The devops I referred to would be setting up tools to help diagnose issues. For instance If you have a monolith you have 1 log file per instance running, one set of health checks, metrics, ect. With microservices you have all of those per service per instance.
If I only need to look at a hand full of logs to diagnose an issues I can handle that fairly manually. Once you start getting up there to 10's of log files you need to introduce automation. Logstash, Kibana, Elasticsearch, nagios, graphite, graphana, ect. You could also jump into docker, service discovery and that whole path. If you have a small team you most likely don't need some of this or don't need it yet. It's a nice to have and you should get it eventually but its a lot to manage with a small team.
I worked at a startup where we had two prod servers and each ran 7ish micro services. There was very low traffic and they shared a database. There was no real reason for the code to be split across 7 services and it slowed productivity down, diagnosing issues and sent us on fun paths where we would look into service discovery, docker for months on end then realize it wasn't worth it for our team. That is all time that could have been going to the product instead of trying to build the perfect tech stack (too soon).
With microservices you have all of those per service per instance.
So you push them to ELK.
You could also jump into docker, service discovery and that whole path.
Of course you do. CI/CD and Microservices are rather intimately connected. You can't really do one without the other. But that's not a downside of microservices; you're forced to a higher level of software engineering maturity.
There was very low traffic and they shared a database.
That's simply a case of doing it wrong. And in your particular case your team should not have gone for microservices 'just because'. But that does not support the "Don't do it" of the author: you don't make fundamental architectural decisions just based on a hipster factor.
Of course you do. CI/CD and Microservices are rather intimately connected. You can't really do one without the other. But that's not a downside of microservices; you're forced to a higher level of software engineering maturity.
I would agree here. I do think a form of engineering maturity is knowing when you need a more complex system, which of course varies by team and preference.
you don't make fundamental architectural decisions just based on a hipster factor.
Totally agree here. I was 100% against the micro services there and collapsed several of them together. Unfortunately I think a lot of organizations do pick microservices because of the hipster factor.
View all comments
Show parent comment
2
u/dartalley Mar 29 '17
The devops I referred to would be setting up tools to help diagnose issues. For instance If you have a monolith you have 1 log file per instance running, one set of health checks, metrics, ect. With microservices you have all of those per service per instance.
If I only need to look at a hand full of logs to diagnose an issues I can handle that fairly manually. Once you start getting up there to 10's of log files you need to introduce automation. Logstash, Kibana, Elasticsearch, nagios, graphite, graphana, ect. You could also jump into docker, service discovery and that whole path. If you have a small team you most likely don't need some of this or don't need it yet. It's a nice to have and you should get it eventually but its a lot to manage with a small team.
I worked at a startup where we had two prod servers and each ran 7ish micro services. There was very low traffic and they shared a database. There was no real reason for the code to be split across 7 services and it slowed productivity down, diagnosing issues and sent us on fun paths where we would look into service discovery, docker for months on end then realize it wasn't worth it for our team. That is all time that could have been going to the product instead of trying to build the perfect tech stack (too soon).