3 ms·

First - always think whether monolith would solve your problems. Second - would mixed architecture solve my problems ? Third - would microservices solve my pr

by pojzon 8y ago

First - always think whether monolith would solve your problems. Second - would mixed architecture solve my problems ? Third - would microservices solve my problem better? Not every company has to be a Netflix or Zalando or Google... I think we finally at the point when people should stop jumping on buzzwords and do the hard work of going through pros and cons of every solution.

icebraining 8y ago
The advantage of jumping on the buzzwords is that have you many others with you. I had to build a SaaS platform for hosting a business webapp, with the particularity that every client had their own separate codebase and database (no multitenancy). It was a simple django-like stateless app in front of Postgres and we had a low availability SLA (99.5%) so I thought it was simple, just deploy each app to one of a pool of servers, with a single Nginx and Postgres instances on each server, then point the client's (sub)domain to it. In the end, it worked fine, but since I couldn't find anyone doing the same, it meant I had to write a whole bunch of custom tooling for deployment, management, monitoring, backups, etc. Were I starting now and decided on Kubernetes, the solution would be more complex and less efficient, but it would mean we would have one-click deployment and pretty dashboards and such in a couple of days instead of many weeks. And if we had to bring someone in, they wouldn't have to learn my custom system. Buzzwords are a kind of poor-man's standards, they provide some sort of common ground among many people.
- collyw 8y ago
  You are still going to need to customize kubernetes deployments.
- pojzon 8y ago
  So instead you chose to still have to customize deployments and network setup. Alot more complex security config to do things seemingly "fast". Is that company a start up ? If not it will cost them alot later on..

by pojzon 8y ago

icebraining 8y ago

The advantage of jumping on the buzzwords is that have you many others with you. I had to build a SaaS platform for hosting a business webapp, with the particularity that every client had their own separate codebase and database (no multitenancy). It was a simple django-like stateless app in front of Postgres and we had a low availability SLA (99.5%) so I thought it was simple, just deploy each app to one of a pool of servers, with a single Nginx and Postgres instances on each server, then point the client's (sub)domain to it. In the end, it worked fine, but since I couldn't find anyone doing the same, it meant I had to write a whole bunch of custom tooling for deployment, management, monitoring, backups, etc. Were I starting now and decided on Kubernetes, the solution would be more complex and less efficient, but it would mean we would have one-click deployment and pretty dashboards and such in a couple of days instead of many weeks. And if we had to bring someone in, they wouldn't have to learn my custom system. Buzzwords are a kind of poor-man's standards, they provide some sort of common ground among many people.

collyw 8y ago
You are still going to need to customize kubernetes deployments.
pojzon 8y ago
So instead you chose to still have to customize deployments and network setup. Alot more complex security config to do things seemingly "fast". Is that company a start up ? If not it will cost them alot later on..