Serverless can bring opportunities by making DevOps more accessible to folks new to the industry. It can also bring opportunities to folks already in the industry that want to spend more time focusing on adding business value. But many technologists, seasoned or otherwise, hear a lot about serverless but don’t always know how to get started.

In the first article in our new series, Yan Cui highlights the key insights from the Amazon Builders’ Library article, Timeouts, retries and backoff with jitter, by AWS Senior Principal Engineer Marc Brooker.

There are scenarios where we want to de-couple logic across multiple logic apps. Generally, this is a straight forward endeavor, unless the downstream logic app has a long-running process. When this does occur, the client (or publisher) will experience an HTTP timeout if the request takes more than 2 minutes. This scenario is captured within the Azure Logic Apps documentation.

This blog focuses on Dashboard capabilities in Serverless360 and its use cases. Let us take a simple cab booking application scenario to have a better understanding of the Composite Application Dashboard.

Among the many, MANY announcements at re:Invent this year is one that settles a years-long debate or concern amongst people considering using AWS Lambda to build serverless applications: cold starts. AWS Lambda is now 5 years old. For all of that time, there’s been a concern about latency the first time a function is called. Well, fret no more: with Provisioned Concurrency you can pay a tiny fee to know Lambda functions are always available.

When we introduced Secondary Storage two years ago, it was a deliberate compromise between economy and performance. Compared to Honeycomb’s primary NVMe storage attached to dedicated servers, secondary storage let customers keep more data for less money. They could query over longer time ranges, but with a substantial performance penalty; queries which used secondary storage took many times longer to run than those which didn’t.

At re:Invent 2019, Farrah and I gave a talk on our paths into the tech industry, how serverless helped us both build some of our first products, and how serverless represents a new mindset. I’d wanted to share a version of that talk on our blog for those who couldn’t make it, though we hope to give it again in the near future.

API Gateway is a serverless service by AWS to expose cloud services through private or public HTTPs endpoints. It is used by many serverless teams to connect frontend applications to backend systems in a secure, scalable and seamless way. API Gateway integrates with Lambda, DynamoDB, S3 and a variety of other AWS services. The main issue with API Gateway, so far, was its cost. At $3.50 per million requests, it can be more expensive than Lambda itself.

We did a compilation of all announcements from the AWS re:Invent 2019 that are relevant for Serverless teams, broken down by services.

Up until now, DynamoDB has been the only option of a truly serverless database battle-tested for production environments. Especially after launching the on-demand throughput capacity optimization, is a perfect-fit database engine for serverless projects.