3 ms·
I'm privately skeptical about starting with microservices-first for new application development. I have seen a lot of literature about starting off with a mono
by Yhippa 9y ago
I'm privately skeptical about starting with microservices-first for new application development. I have seen a lot of literature about starting off with a monolith and then breaking that down as you see fit. This makes more sense to me than introducing a ton of complexity up front.
Or is it better to deal with that complexity up front and then adding new services/functionality will be easy as time goes on?
- trumpeta 9y agoI'd recommend starting with a monolith, but pay extreme attention to properly separating modules and hiding them behind a small, well-defined API. Then it will become easier to separate these modules out as necessary.
- troebr 9y agoWhether you work with a monolith or microservices, decoupling is the key, and the best way to ensure decoupling is using the proper abstractions and APIs.