3 ms·
The article's author description points to a startup company with a handful of devs, so it's quite likely that they indeed wouldn't gain much from microservices
by blauditore 10y ago
The article's author description points to a startup company with a handful of devs, so it's quite likely that they indeed wouldn't gain much from microservices.
But large companies with large code bases are a whole different story, and what works well for the former might be unfeasible for the latter.
- mikeryan 10y agoSo as a small company or startup the upside of microservices is the architecture lends itself well to the use of third party services. Using Auth0 for user auth is awesome for not having to right a ton of user management boilerplate. Content ful for CMS capabilities gives you a content management system and UI. Firebase for DB and push services, Amazon SNS for notifications. A lot of early prototyping and startup tasks can be done gluing together third party services while you focus on core product offering. You can always pull back services as you outgrow these. I think this use case is one of the huge reasons microservice architectures have been so popular.
- bmh100 10y agoThe author addresses building internal software as monolith vs. microservices, not the use of others' services as part of one's monolith/microservice.
- StabbyCutyou 10y agoThis is more of the intended audience (earlier startups or smaller groups of devs), but I could have done a better job spelling that out.