A well organized monolithic application is better for most startups and probably 99% of businesses. If I hear a dev say “but Netflix uses microservices” one more time 🤣 Netflix is Netflix, we aren’t Netflix.

@jwage Monolithic applications can be well organised? I thought we just called them large / big applications.

@jwage When do you recommend microservices?

@jwage Just ask what a microservice is. But the time they’re done agreeing on a definition, your product will have been on the market for 6 months.

@jwage We chose to build each base component as a standalone and put it in its own library in angular. No more hunting for components. They all live in their own library and if you need to import a component you can bypass modules and import it directly to the component.

@jwage Did someone say microservices? youtu.be/y8OnoxKotPQ

@jwage I would like to add: "microservices written in golang" :)

@jwage In my opinion, you must start on monolithic env, to know your domain and on second step go to ddd strategy.

@jwage The problem with bigger monolith applications, even well organized ones is, you cannot upgrade only parts of it(library/framework/language) so chances are much bigger you stay with tooling that you start to hate and you can't do anything about it.

@jwage Bold of you to assume the monolithic app will be organized 😅 But besides that, I think it's true for most cases, as long as everyone is aware that things can change quickly and people can adapt quickly to the market changes.

@jwage A well organized application can become microservice one iteratively without pain. So build nicely - evolve easy.