4 ms·
While I agree that microservices don't make sense for every use case and definitely not for small companies/platforms, I've done the monolith thing over and ove
by tech_tuna 5y ago
While I agree that microservices don't make sense for every use case and definitely not for small companies/platforms, I've done the monolith thing over and over again and for me, microservices truly are a superior platform model.
Yep, they introduce some new problems and by definition, more moving parts but if you're doing anything halfway complicated or "at scale", this is the only sane way to do it.
Docker was hyped a lot but it's a net win for me and for a good chunk of the industry. SPAs with pure API backends are better too. For me and what I do. I love using software defined infrastructure. I love when things are easy and reliable.
I love microservices.
But I also understand why many people don't and why they're a bad fit for some use cases. In some ways, they're kind of like NoSQL databases. If you're just doing microservices because they sound cool and modern, you're like all the folks who use MongoDB and complain that it doesn't work like Postgres. And then talk endless crap about MongoDB.
You're the problem. Not Mongo. Not Postgres. Not monoliths. Not microservices.
- linkdd 5y agoBetween the monolith and the microservice architecture, there is the SOA (Service Oriented Architecture). At Link Society[0], we're building a SaaS offering for one of our product (Kubirds[1]), the architecture is as follows: - A payment service (with Stripe) - An IAM service (with Kratos[2]) - A Deployment service (which interacts with Kubernetes) - A Dashboard backend service (with Hasura[3]) They are not "micro" at all, but each their own task nonetheless. [0] - https://link-society.com (fr) [1] - https://kubirds.com [2] - https://www.ory.sh/kratos/ [3] - https://hasura.io/