{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Screaming in the Cloud","title":"Episode 24: Serverless Observability via the bill is terrible","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/f8f0990c\"></iframe>","width":"100%","height":180,"duration":2372,"description":"What is serverless? What do people want it to be? Serverless is when you write your software, deploy it to a Cloud vendor that will scale and run it, and you receive a pay-for-use bill. It’s not necessarily a function of a service, but a concept.\nToday, we’re talking to Nitzan Shapira, co-founder and CEO of Epsagon, which brings observability to serverless Cloud applications by using distributed tracing and artificial intelligence (AI) technologies. He is a software engineer with experience in software development, cyber security, reverse engineering, and machine learning.\nSome of the highlights of the show include:\n\nModern renaissance of “functions as a service” compared to past history; is as abstracted as it can be, which means almost no constraints\nIf you write your own software, ship it, and deploy it - it counts as serverless\nSome treat serverless as event-driven architecture where code swings into action\nWhen being strategic to make it more efficient, plan and develop an application with specific and complicated functioning\nEpsagon is a global observer for what the industry is doing and how it is implementing serverless as it evolves\nTrends and use cases include focusing on serverless first instead of the Cloud\nEconomic Argument: Less expensive than running things all the time and offers ability to trace capital flow; but be cautious about unpredictable cost   \nUse bill to determine how much performance and flow time has been spent\nCompanies seem to be trying to support every vendor’s serverless offering; when it comes to serverless, AWS Lambda appears to be used most often\nNot easy to move from one provider to another; on-premise misses the point\nPeople starting with AWS Lambda need familiarity with other services, which can be a reasonable but difficult barrier that’s worth the effort\nManaging serverless applications may have to be done through a third party \nSystemic view of how applications work focuses on overall health of a system, not individual...","thumbnail_url":"https://img.transistorcdn.com/vgV98ushAFvdAFQSQazvt5GYVniCaXSWIjs5eI3r0gQ/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzE0OTQvMTU4Mzg2/OTQ4My1hcnR3b3Jr/LmpwZw.webp","thumbnail_width":300,"thumbnail_height":300}