Making the move to serverless architecture? By accelerating app development time, serverless isn’t just a boon for business, it’s also a win for engineering teams. Gartner explains: “Serverless architectures enable developers to focus on what they should be doing — writing code and optimizing application design — making way for business agility and digital experimentation.”

In this three-part blog postseason, we will describe the different development tools that are available or the different development approaches that we can use to create how Logic Apps. And for each approach/tool, we will describe: First of all, and rephrase Microsoft description: Azure Logic Apps is a cloud service that automates the execution of your business processes or workflows (sequence of tasks that produce a specific outcome).

AWS offers the ability to login to a web UI dashboard. In this dashboard, you can add, edit, and deploy various cloud resources. When I was first getting started with AWS, this is where I began for two reasons: My very first full-time job as a Software Engineer was on a small enough team that all of our infrastructure was setup using the AWS console in a single AWS account.

Microservices architecture is getting adopted extensively in the world of distributed applications. There are various options and frameworks available to implement the Micro Services, e.g., Azure Service Fabric, Azure Kubernetes Services, Azure Functions, etc. The hottest trend these days seems to be serverless. The promise of consumption-based pricing, where you only pay for what you use and nothing more, is enticing.

Alright, we talked the “serverless is awesome” talk but now it’s about time to walk the walk. In the light of us launching our brand new website, we thought it would be fun to show you how to create a serverless website from scratch. In the next 15 minutes, we’ll take you through the entire process of creating your first website running on serverless and you better believe it’s going to be awesome.

Have you noticed recently that your AWS Lambda invocation requests are getting throttled? If so, your Lambda functions are probably not running as designed. Let’s examine the possible causes and solutions to poor Lambda performance.

Any application built today is expected to be highly responsive, highly available, and required to adapt to enormous changes in real-time at peak business hours, store ever-increasing volumes of data, and make that stored data available for users a fraction of seconds. To achieve such low latency and high availability, you need to deploy these applications’ Instances in data centers that are close to their users.

Serverless computing simplifies IT operations by delegating infrastructure setup, configuration, provisioning, and management to a cloud vendor.

There is a growing ecosystem of vendors that are helping AWS customers gain better observability into their serverless applications. All of them have been facing the same struggle: how to collect telemetry data about AWS Lambda functions in a way that’s both performant and cost-efficient. To address this need, Amazon is announcing today the release of AWS Lambda Extensions.

We are excited to announce a new integration to help developers add partner solutions to their serverless applications. AWS recently released Lambda Extensions to allow Lambda to augment the Function invocation lifecycle. Extensions from AWS, AWS Lambda Ready partners, and open source projects are useful for a wide range of use cases. For example, Extensions simplify a development workflow by automatically instrumenting Lambda functions or deploying operational tools without needing code changes.