4 ms·
> grouping a bundle of functions together behind an API gateway, you’ve created a microservice Always beats me why people don't warn the readers about the almo
by Dawny33 9y ago
> grouping a bundle of functions together behind an API gateway, you’ve created a microservice
Always beats me why people don't warn the readers about the almost impossible nature of logging and monitoring such systems :/
- tehramz 9y agoBecause most devs aren’t the ones that will need to worry about how it’s going to be monitored once deployed. Not to mention troubleshooting a billion micro services when something breaks.
- mirko22 9y agoHow do you figure that? Who else should worry about it?
- cle 9y agoHow is it impossible? My team and I have built and maintain quite a large serverless system--logging and monitoring have been the easy parts.
- Dawny33 9y agoWe do monitor too. We made a Master-Worker architecture which scales according to the data traffic. (Talked abt it in Velocity Conf. London this year) One way is we monitor the Ansible tasks which make this happen. Apart from that, there is no way we can do it. + trying to make it happen by using something like a Prometheus+Grafana server would defeat the entire purpose of going serverless
- andre-m 9y agoDo you mind expanding on that? With APIG+Lambda you get CloudWatch integration 'out-of-the-box', and can expand the metrics and logs you send out with a few added lines of config. You can also toggle X-Ray for a detailed view of your call graph. If the default implementation isn't good enough, you can define your own CW events, alarms, and log filtering. I'll grant you that you can't just ssh into a host and tail some logs, but if you're keen you can send your logs to elasticsearch for a better arbitrary search experience.
- Dawny33 9y agoYeah. I was talking about the serverless systems which are distributed in nature, which means a huge master-workers architecture.