Stackery
BETA SIGNUP

Stacks on Stacks

Stacks on Stacks is a serverless technology blog by Stackery.
Databases, Serverless, cloud infrastructure, AWS Lambda, AWS DynamoDB

Stackery Support For NoSQL Tables

By Chase Douglas

One piece of technology that goes hand-in-hand with serverless tech is NoSQL databases. They tend to be more granularly scalable, as their scaling mechanism is some form of "just throw more shards into it." And with recent improvements, services like AWS DynamoDB even have auto-scaling support. Read on ..
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 ..
Databases, best practices, Serverless, security, cloud infrastructure

Using Virtual Networks To Secure Your Resources

By Chase Douglas

In this post, I'm going to highlight one of Stackery's more interesting nodes. The Virtual Network node provides a powerful mechanism for securely deploying resources inside a private network. 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 ..
Serverless, Amazon Alexa, AWS Lambda

Serverless Amazon Alexa Skills

By Marketing

After doing the standard “Hello World” serverless program, I didn’t know where to go next. What would be a simple but interesting project? It was pointed out to me that I could build an Amazon Alexa Skill using serverless. Since I had recently acquired a new Amazon Echo, this seemed like an exciting project to get started on. Read on ..
Process Improvements, best practices, Serverless

What's your serverless maturity level?

By Marketing

In talking with hundreds of early-adopting companies in the serverless space, we've seen a clear pattern emerge in how companies embrace serverless architectures. Whether you're just beginning to evaluate a FaaS (Function-as-a-Service) architecture, or have already transitioned large portions of your application to AWS Lambda (or related FaaS offerings), it can be helpful to get a sense of where your organization lines up on the serverless maturity scale. Read on ..
Serverless, Python

Python Support

By Chase Douglas

I'm excited to announce support for Python in Stackery! Python is our third supported language, along with Node.js and .NET. Read on ..
Serverless

AWS Lambda: Sync or Async?

By Marketing

When you execute your code within AWS Lambda, the functions can either be invoked synchronously or asynchronously. While each is useful and needed for different situations, they also come along with interesting side effects in the serverless space.   Read on ..
Process Improvements, best practices, Serverless

The Serverless Learning Curve

By Marketing

Like all new technologies, there's a lot of hype around FaaS-style "serverless" architectures. You may have heard of the many benefits of serverless: faster time to market, lower infrastructure costs, and impressive scalability. While all true (and enormously advantageous), it's important to identify some of the challenges of this new infrastructure approach. 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 ..
// linkedin pixel