In the fast-moving and demanding world of software development, it is critical for organizations to utilize solutions that help streamline server setup in a scalable and affordable manner. Serverless computing solutions were developed in response to these requirements.

From the development and operations side, launching a new software application can be quite challenging. Deciding which tools to use, how to organize the task pipeline, managing collaboration among team members, monitoring performance and potential issues after launch, etc. It’s not easy to get it done right. Dashbird recently went through all of this. Behind the scenes, our amazing development team worked really hard to overcome all challenges and deliver the best value to our users.

Custom Handler is a feature in Azure Functions which lets you bring your own command, script, or executable, and hook it up to Azure Functions Triggers and Bindings. Custom Handler implements a lightweight Web Server. In other words, you can write your own APIs, in any language i.e. it need not be a language supported by Azure functions. You can just hook up your Azure function host with your custom API and let your function act as a proxy.

Lumigo’s Auto-Tracing allows you to implement distributed tracing on your Lambda functions with 3-clicks and no manual code changes. If you’ve already decided to move to a serverless infrastructure, you probably understand the importance of monitoring your AWS Lambdas and what it might entail. For the few out there that are still wondering what monitoring AWS Lambda means, I’ll break it down for you in a couple of steps.

AWS Lambda is the leading serverless computing solution and is one of AWS’ most successful products, to date. Its popularity is in large part because of the way it makes development easier and faster. Lambda completely abstracts away the maintenance of underlying infrastructure including compute, storage, memory, and networking. Developers simply upload their code in the form of Lambda functions and the service fully handles the execution of these functions.

A few weeks ago, Stackery had the pleasure of participating in a webinar with leaders from AWS and MasterStream ERP, a telecom-quoting company that has quite the architectural modernization story to tell due to their adoption of serverless with Stackery. Our very own Farrah Campbell (Ecosystems Director) sat down for a fireside chat with Santiago Cardenas (Sr.

We’ve recently updated one of the most powerful features in Lumigo: Explore, and I wanted to tell you a bit more about it and what it can do for you. Explore is a quick and easy way to find events you are interested in your Lambda invocations. Without a feature such as Explore, you would have to sift through thousands of invocations to find what you are looking for, wasting a lot of time.

TL;DR: yes, API Gateway can replace what a Load Balancer would usually provide, with a simpler interface and many more features on top of it. The downside is that it doesn’t come cheap. Load balancers have been one of the most common ways to expose a backend API to the public or even to an internal/private audience. API Gateways seem to provide the same functionality: map and connect HTTP requests to a backend service. So, are they the same or are there any differences?

There are so many early serverless adopters and pioneers who many of us in the community know well: AWS heroes, in-demand speakers, and celebrated community organizers with thousands of followers, popular Twitch channels, and full speaking dockets. It’s a fantastic idea to follow these folks because they are known for a reason.We cover them regularly at Stackery!

Cost-efficiency is one of the main pillars of the Serverless Well-Architected framework. Read-intensive applications can save money and improve efficiency by using cache systems. AWS Lambda’s internal memory could be used as a caching mechanism. A Lambda container remains alive after an invocation is served, even if it stays idle for some time. Whatever was loaded in the container’s memory will remain there for the next invocations.