Member-only story
Probably you have an idea banging upon your head and are wondering the best way to implement it. Don’t be anxious, don’t hurry! Don’t start writing code right away. If you have a project idea, either to start a company from it or to show it off to employers or recruiters, it needs to be done correctly, and thinking about a scalable architecture is a good way to start. Let’s dig in!
What do we mean by “Architecture”?
Of course, let’s go to the Wikipedia and check the definition:
Software architecture refers to the fundamental structures of a software system and the discipline of creating such structures and systems. Each structure comprises software elements, relations among them, and properties of both elements and relations.
Yes, I know you could’ve done it by yourself, but you didn’t. Let’s break this definition down into pieces, naturally, giving my opinion!
For me, the definition of architecture depends on the scope, on the “zoom” you are seeing the system with. It can mean how to structure the system as a whole, with frontend, backend, and databases; it can mean how to organize microservices communication… But in our case, we’ll zoom in and just look to the frontend scope, which is already enough, trust me.
