Roy Gabbay’s Post

📢 I'm thrilled to bring you the next installment in our Kubernetes and Cloud Native Associate journey! This article has been in the works for a while, and I'm excited to share it with you all. 😊 🔍 In this article, "Kubernetes Pods: The Building Blocks of Your Cloud-Native Applications", we'll cover: • What Kubernetes Pods are and why they're so important • The anatomy of a Pod • Single-container vs Multi-container Pods • The lifecycle of a Pod • Best practices for working with Pods You can read the article here: https://lnkd.in/gv6vPdaT I'm eager to hear your thoughts! Did this help clarify the concept of Pods for you? Any questions or topics you'd like to see covered in future articles? Let me know in the comments! 😊🚀

💡 Great post by Yan Cui, highlighting the pros and cons of orchestrating workflows inside AWS Lambda functions vs. using Step Functions 👇

Axiom and Serverless Inc. are the perfect match for limitless observability with Serverless Framework. └ Slashes CloudWatch costs by up to 70% └ One-line integration with Serverless for effortless setup └ Full event visibility across AWS and beyond └ Advanced querying and real-time insights with APL Dominic Chapman, Head of Product, shares how Axiom goes far beyond CloudWatch and effortlessly integrates with Serverless. Learn more → https://axi.sh/serverless

Learn by example! Using an event driven architecture along with serverless components of AWS make a good pairing to solve many use cases. Using these services will ensure you only pay for what you use but also provide the ability to scale up quickly when needed. Here is an interesting example from Joud Awad showing the use of AWS serverless components to build a priority queue architecture. https://lnkd.in/eDufSpYs

A great piece worth a read on Stripe 's observability overhaul. Having dealt with similar scaling pains, their move from SaaS to managed Prometheus/Grafana on AWS really resonates. Interesting how they handled the migration with dual-writing and automated validations (those PromQL translations can be tricky!) Nice to see them prioritizing team education over rushed metrics - that's often where these big platform switches fail. The architecture looks solid for their 300M metric scale. #observability #prometheus #DevOps

Kubernetes 🆚 Serverless? Let's settle the debate once and for all!   Check our latest blog post to break down the core aspects of both. 🛠️ https://lnkd.in/dtfXNKeA

TL;DR Join my session on how I built custom Serverless blueprints to implement observability, monitoring and best practices at scale. In my session, we'll dive deep into the design of impactful serverless blueprints, focusing on key areas such as seamless CI/CD integration, Lambda best practices, observability, testing, and effective project structure. Whether you're new to serverless or looking to refine your skills, this session is designed to provide valuable insights and practical takeaways. Additionally, I'll be introducing the 'AWS Lambda Handler Cookbook,' a resource aimed at enhancing your serverless applications and addressing common challenges. Thanks Shani Kazaz for the opportunity. Space is limited. Register now. https://shorturl.at/bsxy1

Dive into building an event-driven application using AWS AppSync, EventBridge, and Step Functions 🚀 https://lnkd.in/exHTnFyQ Subscribe to the DevOps Bulletin newsletter to receive weekly DevOps tips and tutorials: https://lnkd.in/ggvrK5x2

Orchestrating complex serverless architectures can quickly become a tangled mess. AWS Community Builder, Chloe McAree (https://go.aws/3ISYprE) wrote a stellar blog breaking down the latest in Step Functions to help make things less messy. ➡️ https://go.aws/4a67RE2 For all you serverless enthusiasts out there, this is a must-read. Chloe covers why Step Functions are helpful for orchestrating complex serverless architectures, and then dives into new capabilities like: 1️⃣ Redrive from point of failure - No more restarting entire executions. You can now fix issues and redrive from the failed state. 2️⃣ HTTP State - Make direct HTTP calls to ANY public API from your Step Functions workflow. Goodbye Lambda proxies! 3️⃣ Test API - Thoroughly test individual workflow states without spinning up the whole state machine. 4️⃣ Bedrock Integration - Orchestrate generative AI model invocations and fine-tuning jobs using Step Functions. 5️⃣ App Composer Integration - Design Step Functions workflows directly in your IDE for streamlined development. Huge congratulations to Chloe for this detailed and dev-friendly breakdown! Her clear passion for serverless shines through. #AWSCommunity #StepFunctions #Serverless

Serverless is not dead! Serverless does matter to the industry! The serverless ecosystem is evolving! and Serverless has decades ahead of it! Sheen Brisals https://lnkd.in/gMj7nvqQ