AWS recently launched the Serverless Event Bus, AWS EventBridge. Some have described it as an extension of CloudWatch Events, while others say it is provides the same features as AWS SNS. So, what exactly is EventBridge? And how does it fit into the existing AWS serverless ecosystem?

You’ve no doubt heard that IOpipe has been acquired by New Relic (congratulations to both). As part of the acquisition, New Relic has said it intends to retire the IOpipe platform in the next 30 days. If you’re currently relying on the IOpipe platform to monitor and debug your serverless application you have an important decision to make. One option is to try out New Relic’s serverless monitoring functionality.

It’s been a great couple of months at Stackery. Since coming on as CEO earlier this year, I’ve been impressed with how much our team gets done and their contributions to making the serverless development experience easier and more reliable. I want to take a moment to recognize two of our amazing Stackerinos who were recognized by AWS recently with the AWS Serverless Hero distinction.

If you have anything to do with the world of cloud computing or even programming for that matter, then I’m sure you’ve heard of different terms being tossed around such as “serverless computing” or “containers,” and even “monolithic architectures.” A lot of people who understand such computing methods can have a bad habit of using these terms without leaving any explanation as to what they are.

I often get asked what software tools are ideal for a serverless developer. I like being asked for my tooling preferences as much as the next developer gal, but when you break it down, this particular question is flawed. Serverless is, after all, about using a massive suite of platform tools to let you do minimal management.

In this article we’ll introduce the AWS Cloud Development Kit and explore how it can boost the productivity of your development and infrastructure teams. Infrastructure-as-Code is fast emerging as a de-facto standard for development organizations.

There’s no sure-fire way to tell whether or not serverless tech is going to grow or even be around next year. Every post-apocalyptic movie has thought me that technology is the first thing to go after a catastrophic event happens. And if that happens we’ll have to return to some ancient tech like ** knock on wood ** containers.

In 2008, Netflix was struck by a disaster. A fast-growing global streaming service was well on its way to transform the entertainment industry when the management faced a problem exposed by a data center failure. Even though it was a single issue, it shut the entire service down, depriving the company of millions in profits and effectively ending the shipments of DVDs (they were still a thing in 2008).

ServerlessConf NY this past October was an important milestone for those of us tracking how software is built on cloud services. . We’ve seen the serverless talks evolve from “what is serverless” to “I built a weird thing” to “We built a new business” to “We refactored a legacy app and kickstarted our feature velocity.” We’ll come back to those last two soon, , but I want to highlight some points from one in particular by Tim Wagner.