4 ms·
Typically, "monolith" implies services - ie, the "backing services" from a traditional 12-factor monolith: - https://12factor.net/backing-services https://12fa
by strix_varius 4y ago
Typically, "monolith" implies services - ie, the "backing services" from a traditional 12-factor monolith:
- https://12factor.net/backing-services https://12factor.net/backing-services
Monolith vs. Microservices comes about because microservices proponents specifically set it up as an alternative to a traditional monolith + services stack:
- https://www.nginx.com/learn/microservices-architecture/#:~:text=Microservices%20versus%20Monolithic%20Architecture https://www.nginx.com/learn/microservices-architecture/#:~:t...
- gedy 4y ago> Typically, "monolith" implies services - ie, the "backing services" I don't know if that's a common interpretation - in the monolith-loving companies I've worked with it very much meant a single ball of code (e.g. huge Rails app), not separate services.