Much of the writing I’ve done in this space over the past few years has been geared towards microservices and scalable architectures based on innovations in cloud providers’ technologies. But sometimes the way that we talk about microservices architectures implies that they are the only good solution and monoliths are bad. Are they?
What we have to say, what you want us to hear.
That’s how our blog works. It’s interactive. Let’s learn together.
Serverless has been a buzzing topic in the cloud community for quite some time now, and with good reason: serverless is great for managing cloud costs and utilization, deploying quickly, and scaling on-demand. While I’ve touched on some serverless elements before, today we’re going to talk about the backbone of serverless computing: Function as a Service or FaaS.
It’s back to school season, and for me that meant helping my eldest daughter move into her first apartment with roommates and … cable internet. Few industries garner as much universal hatred as residential Internet service providers (ISPs). The previous residents, in their well-earned distrust of the local provider, told her that it would be much cheaper to purchase her own modem and router than to lease. And so, she bought reasonably-priced (translation: the cheapest) models from Amazon.
Whether you’re working with a single-instance application or a complex deployment of dozens of orchestrated microservices, it is important to know that the code is working the way it should, and how people and outside systems are interacting with it. I’ve written before about instrumentation of applications and even showed a toy example using amazon X-Ray, but I thought I should devote some space to observability and why it is important.