5 ms·
Why we don't build "micro monolithics" ? Why microservice I am very specialized, and every service should do just one thing well, think about send an email, lo
by siscia 11y ago
Why we don't build "micro monolithics" ?
Why microservice I am very specialized, and every service should do just one thing well, think about send an email, load the ads or load the comments.
Why we don't build a very shallow service, that does everything for just a very small part of the website ?
In a classic website a micro monolithics (mm) could be something like "/login" or "/post-picture".
The mm will not call any other service but it will be able to do every action by itself.
Simply deploy a (or more) new service for every (busy) end point of your application.
In this way we can share, or isolate, our codebase.
It would be easy to deploy, basically you are simply using a whole server to run one single function at very high frequency.
It can bring a lot of chance for optimization.
Just thinking...
- octo_t 11y agothis is basically how apache/mod_perl works.
- jalfresi 11y agoFastCGI? Always thought that was a technology that was sidelined way too soon
- agumonkey 11y agoI don't know if this was researched by system theorist. A spectrum of scale from micro to mono. When micro communication costs are too high, integrate, rinse, repeat. Makes me think of https://news.ycombinator.com/item?id=9777567 https://news.ycombinator.com/item?id=9777567