Operations | Monitoring | ITSM | DevOps | Cloud

As developers, we all seek to build web applications that can scale seamlessly, adapt to changing needs and do so without incurring excessive costs. One way to achieve this is by migrating web applications to AWS Lambda, which can provide scalability, flexibility, and cost savings. To make this process even easier, AWS provides the Lambda web adapter, a simple and efficient tool that enables you to migrate your web apps quickly.

The AWS CDK lets users build as Infrastructure as Code (IaC) reliable, scalable, and cost-effective applications in their cloud environments. With the AWS CDK, developers can use various supported programming languages to create constructs (reusable cloud components) and compose them together into stacks and applications.

In this blog, I will speak about “How to throw exceptions inside Logic Apps using default capabilities”. Let’s get started!

Lambda has a size limit of 6MB on request and response payloads for synchronous invocations. This affects API functions and how much data you are able to send and receive from a Lambda-backed API endpoint. I have previously written about several workarounds on the request payload limit. But sometimes you also need to return a payload bigger than 6MB. For example, PDF or image files.

AWS Lambda Function URLs make it even easier to create AWS Lambda functions that can be accessed and triggered by using HTTP/S requests, which is key for building serverless applications that are connected to and invoked from the web. Now you can generate a URL in one click that points to a specified Lambda function. Then, any HTTP/S request that a Function URL receives will trigger the Lambda function it’s assigned to.

Today I will speak about another useful Best practice, Tips, and Tricks that you must consider while designing your business processes (Logic Apps): How to embed HTML images into your email using Logic App Designer.

A distributed system is a system whose components are located on different networked computers, which communicate and coordinate their actions by passing messages to one another. The components interact in a decentralized manner and work together to achieve a common goal. Working with distributed systems is challenging, because failure often spreads between components and debugging across multiple components is difficult and time-consuming.

Want to build websites and apps in a way that’s both easier and cheaper? Well, it’s possible even for major organizations and international companies. In this article, let’s take a look at how serverless architecture and computing is changing the game for software developers. We’ll start at the very beginning and walk through how serverless works, how we got this far, and the pros & cons of this approach.

When your organization has started to adopt Azure, the continuously increasing number of Azure resources throughout all your Development, Test, and Production subscriptions make it hard to keep on top of the health of all those resources. So, it is important to have proactive Azure resource monitoring to know when something unexpected happens.