Serverless development has been turning heads in the market for quite some time now. But it has yet to be accepted by the majority in the development community. With AWS Lambda, Azure Functions, and IBM’s Open Whisk, the market is poised to take a different route in this field. Most of these organizations are spending a lot of money to make the market accept this new paradigm using serverless computing.

Being a developer is awesome. Writing code, solving problems, and thinking of ingenious solutions for complicated algorithms is what we live for. But, the grass is not always so green on this side of the fence. Sooner or later, you need to get your hands dirty and deploy the app you worked so hard on. Deployments are not always easy. To be blunt, they can be challenging and time-consuming. That’s what we’ll solve in this tutorial.

Azure App Service is a platform-as-a-service (PaaS) offering for deploying applications to the cloud without worrying about infrastructure. App Service’s “serverless” approach removes the need to provision or manage the servers that run your applications, which provides flexibility, scalability, and ease of use. However, App Service also introduces infrastructure-like considerations that can impact performance and costs.

With over 200 products offered by AWS, when designing a solution, such as a micro-services based system using a number of these services at its core, it becomes rather challenging to not only monitor them but on the onset of a problem troubleshooting it and resolving it within the least amount of time becomes a daunting task. Building a monitorable system requires a deep understanding of the failure domain of the critical components, which is a tall order for a fairly complex system.

As the world is increasingly reliant on technology, software developers, cloud architects, and DevOps practitioners bear a responsibility similar to that of the health industry or to airplane pilots, for example. In this reality, cloud monitoring isn’t optional, it’s a matter of being professional. What is optional, however, is what monitoring solution to go for. Obviously, the one that best fits your specific needs but which one is it?

Non-Fungible Tokens, or short NFTs, are all the rage right now. Everyone and their pets are starting an NFT project. Some people got rich from using NFTs; others did not. Some say it’s the savior that will rip the power away from big corporations and give it back to the creators; others say it’s just a giant pyramid scheme.

In a serverless application, AWS Lambda functions are typically invoked by JSON-formatted events from other AWS services—like API Gateway, S3, and DynamoDB—and respond with JSON-formatted payloads. Having visibility into these function request and response payloads can provide context around your function invocations and help you uncover the root causes of Lambda function failures.

Python, used in around 53% of all Lambda functions, is the most popular language for doing Serverless. In this article, you’ll get an overview of the need-to-knows for error handling Python in AWS Lambda.

In recent times cloud computing has played a significant role in various domains. In this blog, we will look at how Serverless360 helps these domains fulfill their business needs. We will explore a global insurance provider’s business need with regional offices in several territories and partners in many countries who need to manage policies and contracts and submit claims from different countries to the customer to reduce the processing overhead and maximize automation opportunities.

Here’s a quick roundup of the newest product features, resources, and events from Lumigo.