System design is actually very vast. At a high level, it covers things like software architecture, I mean the advantage between monolithic and microservice architecture and choosing between a NoSQL and SQL database. It covers things like how we will design an application that can handle 10000 concurrent users. And includes things like scalability.
Here are a few essential System design concepts you should know:
*Load Balancing
*Caching
*Data Partitioning
*Indexes
*Proxies
*Redundancy and Replication
*SQL vs. NoSQL
*Distributed Systems
At a low level, it covers Object-Oriented Programming and Design, which talk about designing your classes and their relationships, following good coding practices, and software design principles like SOLID.
Because of this, many candidates struggle to answer system design questions, and if you want to succeed, you must put particular emphasis on this skill.
