Operations | Monitoring | ITSM | DevOps | Cloud

Latest News

Can AWS API Gateway Act as a Load Balancer?

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?

Seven Serverless Champions You Should Start Following Today

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!

Leveraging Lambda Cache for Serverless Cost-Efficiency

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.

Using API Gateway to run Database Queries

The most common integration type for AWS API Gateway is with Lambda functions. The API service can integrate with virtually any other service that accepts HTTP requests, though. This opens up possibilities to use the API Gateway as a proxy to database queries, without any compute layer such as a Lambda function. The direct integration between API and database is perfect when Lambda serves only as an intermediator.

Splunk is Lambda Ready: Announcing a New Partnership with AWS

We are excited to announce that Splunk has partnered with AWS in launching a new AWS Service Ready program – Lambda Ready. This designation recognizes that Splunk provides proven solutions for customers to build, manage and run serverless applications. AWS Lambda Ready designation establishes Splunk as an AWS Partner Network (APN) member that provides validated integrations and proven customer success with a specific focus on observability and monitoring of Lambda Functions.

Lumigo achieves AWS Lambda Ready designation

We’re excited to announce that Lumigo achieved the coveted AWS Lambda Ready designation as a serverless-first observability platform. Over the years we’ve put a lot of effort into building a product that would help the mainstream adoption of serverless technology by providing developers with the tools they need and it’s truly an honor to have AWS recognize those efforts.

Dashbird achieves AWS Lambda Ready designation

Dashbird, centralised observability and incident detection platform for serverless applications. Team Dashbird is proud to announce that we have achieved the AWS Lambda Ready designation, part of the Amazon Web Services (AWS) Service Ready Program. This designation recognizes that Dashbird’s serverless monitoring and debugging platform has demonstrated successful integration with AWS Lambda.

ANNOUNCING - Stackery Achieves AWS Lambda Ready Designation

Today we’re proud to share that Stackery has achieved the AWS Lambda Ready designation for continuous integration and delivery! This differentiates Stackery’s secure serverless delivery platform as fully integrated with AWS Lambda. It also shows our existing and prospective customers that Stackery is a uniquely valuable serverless platform and member of the AWS Partner Network (APN).

MongoDB (and Atlas) vs DynamoDB - 8 Basic Comparisons

Both DynamoDB and MongoDB are NoSQL databases, but the similarities probably end there. In this article, we cover their strengths and weaknesses in 8 basic categories, so that you can decide which one suits best your needs. While the data model behind Mongo is more flexible for storage and retrieval, Dynamo is stronger in terms of scalability, consistent performance under heavy load, and infrastructure abstraction.