While I was thinking about requirements for cook book, I came to idea, that I need to define high level application architecture.Requirements and task of the application should be considered when you are choosing architecture for your software. We ha...
safonovdm.hashnode.dev4 min read
It may depend if you have something working already or not. Because you can build data flow before you started development. In some cases there are limitations of engine or framework that dictates you data pipelines. But also really valid point that should be taken in consideration. Thanks.
The question to use or not use microservices often comes down to your team structure. Do you have one small team that does everything? Go with the monolith. Do you have a separate team responsible for authentication layer? Might be time to create a separate auth service so teams don't step on each other's toes and can drive their own delivery cycle.
Denis Koltsov
What can also justify multi-service approach is how your data flows and being processed, like if you have some data pipelines and such.
Or also if you have some potentially expensive processes that can kill the entire monolith — better put them into a separate service to achieve better redundancy.