Building a serverless application means you usually trade in old issues for new ones. This is an attempt to create a decision framework and break down arguments for and against using serverless vs. other computing models.

Handling large images has always been a pain in my side since I started writing code. Lately, it has started to have a huge impact on page speed and SEO ranking. If your website has poorly optimized images it won’t score well on Google Lighthouse. If it doesn’t score well, it won’t be on the first page of Google. That sucks.

While working for Dashbird.io I’ve had to pleasure to come in contact with a number of serverless early adopters that included both small companies working on apps or just testing ideas as well as fortune 500 companies with an already established user base. What I’ve found is that a lot the people I speak to think of serverless as a shortcut to developing software but that’s just not the case.

This week at the Microsoft Ignite, we unveiled two new Sumo Logic applications for Microsoft Azure services — Azure SQL Database and Azure Active Directory — and two new native integrations with Azure Monitor and Blob Storage. As a cloud-native company, our goal at Sumo Logic is to give our customers the flexibility to create digital IT and DevOps initiatives that leverage multi-cloud deployments in Amazon Web Services (AWS), Google Cloud Platform (GCP) and Microsoft Azure.

How about starting with an introduction? We will attach links to articles already published that expand on each concept or topic in order to keep our journey as compact as possible.