4 ms·
I am just using services with my medium sized application. They are not "micro", but they separate the domains and different concerns pretty well. I have the de
by Aldipower 5y ago
I am just using services with my medium sized application.
They are not "micro", but they separate the domains and different concerns pretty well.
I have the deployment setup more or less like a monolith, but still having separation of concerns with my services. And stateless service runners.. Fair enough I have the state in a single (mirrored) database. But this works perfectly fine for the medium sized app.
Not sure why everything must be black or white.
- unbanned 5y agoService oriented architecture then...
- qxmat 5y agoI've felt SOA is the easiest to grow because it encourages you to swap out concrete implementations as requirements change. For example, IUserService can start off with a "local" UserService implementation that makes direct calls to a database. Once you signup with an IdP this might become UserServiceAzureAD/Okta/Auth0. Unlike microservices, I keep my compile-time guarantees that IUser continues to have the properties I require without any tooling. Given the rhetoric here I worry that I'm the only person who's genuinely swapped out their implementation. The ol' "N-tier is stupid - you're never going to change the database" comment couldn't be more wrong.