Operations | Monitoring | ITSM | DevOps | Cloud

Towards the end of 2016, it all started with developing a simple platform to manage Microsoft Azure Service Bus namespaces. The then classic Azure portal had limited capabilities to manage Azure Messaging resources like Service Bus Queues and Topics. Paolo Salvatori developed and managed a community tool called Service Bus Explorer. We identified that there are some challenges or limitations in managing and monitoring Azure Messaging resources using the above two.

Serverless computing is one of the fastest-growing areas in software development, along with hybrid clouds and using multi-cloud strategies. The global serverless architecture market is expected to grow at a CAGR of 16.2% in 2021 through 2026. It will reach $10.29 billion from $4.2 billion in 2020, according to MarketWatch. The serverless approach promises to help developers beat the cons of self-managed and even virtual server infrastructure. But is serverless right for you?

Let’s start with what you should monitor in Lambda functions. In general, there are two areas – user experience and the cost of the system. User experience usually comes down to availability, latency, and feature set of a service, while the cost of operating a service is important to ensure the profitability of the business.

Stackery can be used to create a new CloudFormation template or to quickly visualize an existing one. Code is automatically generated as you simply drag-and-drop resources on a graphical grid. The experience is much more intuitive than previous generation tools like AWS CloudFormation Designer. Stackery visualizes resources the way a human would perceive them, grouping related resources together.

As your infrastructure grows, getting a handle on all your AWS resources can be overwhelming. While that’s probably an understatement, help could be right around the corner. We’ll cover a few CloudFormation visualizer tools that can help, but let’s level set first. AWS CloudFormation is an established Infrastructure-as-Code solution that allows you to define, provision, organize, manage and update your AWS resources from a text-file template.

If you’re worried that switching to serverless infrastructure is too expensive for your business, you’re not alone. Total spending on cloud services will top $284 billion by 2024. The good news is there are many ways to track and lower your serverless operation costs without slowing down your business. Lambda and how can it help your business? Find out more by reading these Lambda frequently asked questions.

Today, we’ll cover some of the ways you might find quite useful in your everyday work. We’ll go through some of the logging best practices in AWS Lambda, and we will explain how and why these ways will simplify your AWS Lambda logging. For more information about similar topics, be sure to visit our blog. Let’s start with the basics (and if you have the basics covered, feel free to skip ahead): How does logging work with AWS Lambda?

The promise of running a business on the cloud is that — in theory, at least — you should be able to scale your infrastructure up and down with your customer utilization. This should lead, again in theory, to less maintenance and more opportunity for innovation.