If you’ve read the blog posts on CloudJourney.io before, you’ve likely read the term “Continuous Verification”. If you haven’t that’s okay too. In this blog series, we’ll look at how the premise of Continuous Verification works in a serverless world, and how we built the components that make up the ACME Serverless Fitness Shop. The first in the series is about the tools and technologies we used.
The article I wrote with Bill Shetti on Tracking Distributed Errors in Serverless Apps is now available on DZone too 🙌 In this article, we demonstrate how to use Sentry.io to better monitor errors in serverless applications and save you some time while debugging your apps running on AWS Lambda.
Microservices give us as developers an incredible amount of freedom. We can choose our language and we can decide where and when to deploy our service. One of the biggest challenges with microservices, though, is figuring out how things go wrong. With microservices, we can build large, distributed applications, but that also means finding what goes wrong is challenging. It’s even harder to trace errors when you use a platform like AWS Lambda.
As a developer, I’ve built apps and wrote code. As a cheesecake connoisseur, I’ve tried many different kinds of cheesecake. After I got to talk to some of the bakers, I realized that building apps and baking cheesecake have a lot in common. It all starts with knowing and trusting your ingredients. Trusting the ingredients you work with and making sure you have a transparent process to get them into your final product is one of the most important things.
Using serverless requires us to change our mindset on how we build apps and requires us to unlearn things we learned building apps in the past. At AWS re:Invent I got a chance to do a VMware Code session and talk about how we took part of our ACME Fitness Shop and transformed it into serverless functions with AWS Lambda.
Serverless is a development model where developers focus on a single unit of work and can deploy to a platform that automatically scales, without developer intervention. That’s awesome, but is it cheaper to run a Serverless platform or does using Kubernetes work better? In this blog, I’m diving into some of the options you have with AWS Fargate and self-hosted Kubernetes. TL;DR Serverless is cheaper!
There are many predictions from market analyst firms on the size of the global serverless architecture market and how fast it will grow. The numbers range from $18B to $21.99B in the next few years with the compound annual growth rate (CAGR) in the double digits. But is serverless only a fancy name for products like AWS Lambda and Azure Functions?
The CTO of a company I have worked for used to say that services should be loosely coupled but tightly integrated. I didn’t realize until a lot later how true that statement is as you’re building out microservices. How those microservices communicate with each other has also changed quite a bit. More often than not, they send messages using asynchronous protocols. As an industry, we decided that this new way of building apps should be called “Event-Driven Architecture (EDA).