Bachelor's and Master's in CS from MIT. Previously, worked @ Microsoft & Zynga. Currently Co-Founder of Moesif (moesif.com), the most advanced API analytics platform.
One of the growing challenges with serverless computing is monitoring and debugging all those functions. Logging context is now scattered across even more components than even in a microservice architecture. May of the logs are very vendor specific and is not like looking at standard NGINX or HaProxy logs.
But we are still very excited about growth in this space. Interesting that you wrote a book on this topic. Congrats.
Yes, absolutely. Monitoring and debugging remains a challenge in serverless because for one
you can't ssh into a running lambda. Fortunately, the serverless landscape is maturing: services such as AWS X-Ray, Iopipe, Dashbird, and a few others have emerged to help solve the visibility problem: they help you see inside your lambda functions.
As serverless continues to grow and mature, I expect we'll see more solutions in this space.
Thank you for reading!
Software engineer with over 12 years of experience in programming, machine learning, and reverse engineering. Co-Founder and CEO at Epsagon, tracing and visualizing serverless apps.
I think that leveraging external services and APIs are a KEY THING here - it enables you to focus just on your business logic, and FaaS enables you further to not even manage the server your code is running on.
Regarding monitoring - at Epsagon (epsagon.com), we are focusing on automatic end-to-end monitoring of the ENTIRE architecture, rather than of a single Lambda - which we found out is the main challenge in serverless today. Feel free to contact us and try it out our beta.
This is a good point, but I feel this is a solvable problem. Surely there must be a way to unify the logs of several microservices somewhere? But I feel this needs to be provided by the platform where your code runs. Like a periodic upload of logs to a central data warehouse
Bachelor's and Master's in CS from MIT. Previously, worked @ Microsoft & Zynga. Currently Co-Founder of Moesif (moesif.com), the most advanced API analytics platform.
lol. I'll do my own plug.... Since most serverless and microservices are APIs, if we capture all the data at the API level from all these different sources, and analyze them together can solve this problem. Check out the company that I started. Moesif. (moesif.com)
Work at Docker Inc. Ex Serverless.com. Ruby, Golang, API Aficionado, Serverless, Docker, Mesosphere. Asst. Scoutmaster at BSA Troop 39. Amateur Photographer. Entrepreneur.
There are pros and cons.
One of the growing challenges with serverless computing is monitoring and debugging all those functions. Logging context is now scattered across even more components than even in a microservice architecture. May of the logs are very vendor specific and is not like looking at standard NGINX or HaProxy logs.
But we are still very excited about growth in this space. Interesting that you wrote a book on this topic. Congrats.
Yes, absolutely. Monitoring and debugging remains a challenge in serverless because for one
you can't ssh into a running lambda. Fortunately, the serverless landscape is maturing: services such as AWS X-Ray, Iopipe, Dashbird, and a few others have emerged to help solve the visibility problem: they help you see inside your lambda functions.
As serverless continues to grow and mature, I expect we'll see more solutions in this space.
Thank you for reading!
Great read!
I think that leveraging external services and APIs are a KEY THING here - it enables you to focus just on your business logic, and FaaS enables you further to not even manage the server your code is running on.
Regarding monitoring - at Epsagon (epsagon.com), we are focusing on automatic end-to-end monitoring of the ENTIRE architecture, rather than of a single Lambda - which we found out is the main challenge in serverless today. Feel free to contact us and try it out our beta.
This is a good point, but I feel this is a solvable problem. Surely there must be a way to unify the logs of several microservices somewhere? But I feel this needs to be provided by the platform where your code runs. Like a periodic upload of logs to a central data warehouse
lol. I'll do my own plug.... Since most serverless and microservices are APIs, if we capture all the data at the API level from all these different sources, and analyze them together can solve this problem. Check out the company that I started. Moesif. (moesif.com)
Yes, true, but things are improving. Check out serverless.com/blog/serverless-mon...
Checkout AWS X-Ray. Its improving.
You can redirect the logs to Splunk or an ELK stack from any of the leading FaaS providers.