Backend developer | Reader | Semi-writer | Golang | Node.js | PostgreSQL | Vim enthusiast
I like to understand how things work under the hood, but not too deep.
I've worked at companies that have a "megamicroservice". It's an API so complex, it is a thousand times more complex because they tried to split it up into a thousand pieces.
Backend developer | Reader | Semi-writer | Golang | Node.js | PostgreSQL | Vim enthusiast
I like to understand how things work under the hood, but not too deep.
I work in a place where we had a monolith, they started to migrate to a microservices architecture, but this went so wrong that now we're thinking about migrating the monolith to a new monolith and just extract minimal functionality from it (something like the Citadel arch I read somewhere)...
Massive facepalm to the wasted time on those microservices...
Microservices are not the future, nor the present... They are another good approach for some use case, not for all.
I've worked at companies that have a "megamicroservice". It's an API so complex, it is a thousand times more complex because they tried to split it up into a thousand pieces.
I work in a place where we had a monolith, they started to migrate to a microservices architecture, but this went so wrong that now we're thinking about migrating the monolith to a new monolith and just extract minimal functionality from it (something like the Citadel arch I read somewhere)...
Massive facepalm to the wasted time on those microservices...
This has happened literally everywhere.