Serverless
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
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
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 ..
Process Improvements,
DevOps,
best practices,
Serverless,
cloud infrastructure
Stackery is all about serverless, but when I started working here, I had never even heard of the term before. Since starting, I have been hounded by friends and family to explain what Stackery does, which always leads to questions about serverless that I didn’t know the answer to. Two months into the job, I’ve decided it is time to answer some of those questions for myself and others who might be new to the space. I now present to you the 5 W’s of serverless: Who? What? When? Where? And Why?
Read on ..
.NET,
Azure,
Microsoft
Microsoft is a key partner for us. They are a cloud service provider that we aim to support soon, but they are important far beyond being another infrastructure provider for Stackery. Microsoft has a renewed focus on helping developers build great software, and that dovetails with our mission at Stackery.
Read on ..
Serverless,
.NET
I'm super excited to announce our .NET support! We heard from many .NET shops that want to use serverless tech but were hesitant to do so because of a lack of mature tools to enable them. Now, Stackery fills this void.
Read on ..
Serverless,
cloud infrastructure,
api
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 ..
DevOps,
Serverless,
cloud infrastructure
The biggest usage of serverless technologies today is around event-driven workflows in the backend of a system. Examples include receiving an event from an S3 bucket when a video is uploaded, then using a serverless function to spin up a Docker container to transcode the video. However, serverless technologies can provide even bigger wins in when they are used for API services.
Read on ..
Serverless
Serverless is the hot new technology. Everyone raves about it, and many have seen dramatic benefits from using it. Engineering overhead goes down, costs go down, fun goes up! But what is everyone actually doing with serverless technology? We have been reaching out to the best engineers on the planet who are using serverless tech. Along the way we have learned a ton about where serverless tech works well, but also where there is untapped potential. Let's take a look at what people have told us!
Read on ..
DevOps,
Serverless,
cloud infrastructure
I've been hearing increasing chatter about an (arguably still mythical) trend towards NoOps. From my perspective, NoOps is the idealization that infrastructure can become so abstracted and automated that no dedicated Ops team is required to manage it.
Read on ..