Stacks on Stacks

Stacks on Stacks is a serverless technology blog by Stackery.
best practices, Serverless, hapi, cloud infrastructure, api, AWS Lambda

Porting to serverless

By Marketing

Unless you have the luxury of building your application from scratch, chances are you'll face a point where you'll have to decide on a strategy for migrating your application to a serverless/functions-as-a-service (FaaS) architecture. While some considerations, like support for your application's language and runtime version, are fairly straightforward, your overall strategy will probably depend on a number of factors including your application's maturity, architecture, and framework. Read on ..
Serverless, cloud infrastructure, api

Easy Custom Domains For Serverless APIs

By Chase Douglas

Because serverless tech is so new, sometimes we find ourselves waiting for features that ought to have been available from the start. Today, Stackery can check-off another feature that will make it much easier for people to start building serverless Rest Apis. One fundamental aspect of building a Rest Api is Read on ..
DevOps, best practices, Serverless, api

Think Twice Before Decomposing Your Apis For Serverless

By Chase Douglas

Even though  AWS Lambda was first released two and a half years ago, serverless tech is still new. Everyone is still trying to sort out how to build applications with it. Best practices are in their infancy. One technique that has been en vogue is decomposing REST apis down to a one-to-one mapping of endpoints and serverless functions. But is this the best way to build an api service? Read on ..
Serverless, cloud infrastructure, api

Serving Binary Files Using Serverless APIs

By Chase Douglas

One of the challenges of building a serverless API is handling binary data. The main serverless API platforms, like AWS API Gateway, only have ancillary support for binary data. Further, binary data handling is inefficient as the data is encoded using base64 format. Taking into account the message payload limits of AWS Lambda, the maximum size for binary request and response payloads is 4.5 KB. This may be enough for an icon, but not enough for even a small image. Luckily, there's another mechanism for handling binary data: redirects using AWS S3 signed URLs. Read on ..
// linkedin pixel