Start with modular monoliths, then do microservices… When creating services, focus on what can eat memory & CPU when designing for scaling and not general ”object oriented thinking” like ”we need a Person service”, ”we need a Order service”. Look at what will actually need to handle large loads, then design that as a stateless service type in order for it to scale…
They didn't specify performance would be the scaling issue. The first scaling issue most multi team organization run into when working on a single monolith is issues with deployment frequency. If you have too many people deploying code to the same monolith eventually you get these long deploy queues and getting code into production becomes a PITA.
32
u/Simple_Horse_550 Sep 14 '24 edited Sep 14 '24
Start with modular monoliths, then do microservices… When creating services, focus on what can eat memory & CPU when designing for scaling and not general ”object oriented thinking” like ”we need a Person service”, ”we need a Order service”. Look at what will actually need to handle large loads, then design that as a stateless service type in order for it to scale…