Last week, I worked on a POC – how can we dynamically set SQL Server Connector configurations within Logic Apps? – that became a real project and a real architect solution. And one of the critical pieces was Azure App Configuration. Azure App Configuration stores configuration data as key-values.

In today’s modern age, the most crucial aspect of communication is expression. Various groups express their thoughts or feelings through their work. For example, painters express themselves through their paintings as well as singers express themselves through the way they sing. Writers might make you feel their thoughts while reading some of the articles or books they knew how to write primarily for their readers so the readers will understand their feelings and thoughts.

The concept of a microservice perfectly fits the structure of a serverless function, which easily enables deployment and runtime isolation for different services. On the storage side, services such as DynamoDB also make it easier to have independent databases for each microservice and scale them independently (when required or desirable). Before we dive into details, please consider whether the benefits of Microservices abundantly outweigh its disadvantages for your particular project and team.

As you probably already know, Step Functions is a serverless Workflow Service provided by Amazon Web Services (AWS). There’s a lot to discuss about this service, and you’ll find plenty of vital information in our AWS Step Functions: The Ultimate Guide as well as in our series of articles that’ll dive deep into various aspects regarding this AWS service.

Managing applications at scale often comes up as one of the biggest concerns for businesses; How can it work smoothly? How do we monitor so many resources? How do we maintain best practices with constantly evolving infrastructure? In this article, we run through the best approach for operational excellence looking at serverless monitoring strategy, serverless alerting strategy, and security and compliance best practices.

I’ve been primarily a Javascript developer for a long time now, it’s been my go-to language for the better part of a decade now, I even wrote a post on how to implement observability in a traditional Node.js application. Now, on top of hacking around in JS, I also love building things for AWS Lambda which is AWS’s option for Functions-as-a-Service.

Today, AWS announced the AWS Lambda Runtime Logs API, a new way to easily send logs from AWS Lambda functions directly to your destination of choice. AWS Lambda Extensions, announced in October, provide the ability to run code in parallel that is independent of your function’s lifecycle. We’ve created an extension that utilizes the Lambda Runtime Logs API to send your logs directly to Honeycomb.

We are excited to partner with AWS to get real-time log data from AWS Lambda through the new AWS Lambda Runtime Log API and AWS Lambda Extensions. AWS Lambda Extensions enable us to more easily integrate into the AWS Lambda execution environment to control and participate in the AWS Lambda lifecycle and the AWS Lambda Logs API enables us to collect function, platform, and extension logs. Through this integration, Sumo Logic and AWS make it possible to reduce operational overhead and improve performance.

AWS released Lambda Extensions just over a month ago, and we explained what they are and why they matter. Today, AWS has announced AWS Lambda Logs API, a way for extensions to subscribe to and process Lambda logs in real-time.

Serverless. It’s likely you’ve already come across this term somewhere, but what exactly does it mean? Well, to start, serverless, or serverless computing, doesn’t really mean there aren’t servers involved, because there are, rather it refers to the fact that the responsibility of having to manage, scale, provision, maintain, etc., those resources now belong to cloud providers, such as AWS Lambda, Google Cloud Platform, Microsoft Azure, and others.