originally posted on stackery.io/reinvent
Andy Jassy’s re:Invent keynote today was chock full of new features and services. I’m here to help break down the most important news related to modern application architecture. If you’ve read my first post about how to consume re:Invent content, you won’t be surprised to see below that I’m pointing out news that tell us a larger story about how to ship applications in 2021 and beyond.
Modern applications use managed services wherever possible. The purest form of managed services for compute is AWS Lambda. Write your code and AWS will bill it for the amount…
As you likely know, AWS re:Invent is free and virtual this year. AWS plans to release thousands of hours of content and make hundreds of announcements over the course of the 3-week event. It’s a lot to take in — even from the comfort of your own home (and sweat pants).
That’s why, the team at Stackery created The Guide to Serverless at re:Invent, meant for anyone interested in serverless development. If you are following the re:Invent Serverless, Architecture, DevOps, or Migration tracks you should also follow us.
We dive deeper to help you understand how the days announcements change…
originally posted on stackery.io/blog
Making the move to serverless architecture? By accelerating app development time, serverless isn’t just a boon for business, it’s also a win for engineering teams.
Gartner explains: “Serverless architectures enable developers to focus on what they should be doing — writing code and optimizing application design — making way for business agility and digital experimentation.”
Serverless architectures free up time. Instead of getting bogged down in infrastructure management, you and your team can focus on building well-architected apps that deliver ongoing value to your customers. Serverless saves money, too — you only pay for the cloud…
And how to use stack.new to create resilient & secure policies
By Chase Douglas, CTO & Co-Founder Stackery and AWS Serverless Hero
One of the most powerful aspects of AWS is their Identity and Access Management (IAM) service. The obvious aspect of its power is that it controls who can do what with all the resources inside your AWS account. But the non-obvious side is how configurable it is. You can encode permissions that are so finely grained that a Lambda Function could, for example, be given just enough permissions to be able to read one attribute from one record…
Goal of balancing safety and speed is used throughout examples, geared toward microservices but perfectly applicable to server-based deployments. pic.twitter.com/sYekQlYv9R
- Ryan Coleman (@ryanycoleman) December 2, 2020
Clare focused mostly on production deployments, though pre-production CI/CD was covered at the end of the talk. In my view, while the systems may be similar, the goals differ.
Before shipping to production, your deployment pipeline should be concerned with:
by Tim Zonca, CEO @ Stackery
Too often serverless is equated with just AWS Lambda.
Yes, it’s true: Amazon Web Services (AWS) helped to pioneer what is commonly referred to as serverless today with AWS Lambda, which was first announced back in 2015.
But in 2020, it’s important for enterprises to understand that the serverless landscape is much bigger with more opportunities.
Serverless is sometimes (narrowly) defined as just being about functions-as-a-service, but that’s a very limited viewpoint. At Stackery we support over 20 different AWS serverless capabilities at this point in time, with Lambda being just one of many.
Local prototyping has become de rigueur for most web stack developers in the last few years. Even complex web backends are generally assumed to be emulatable from a developer’s laptop.
But this assumption breaks down a bit as we explore the AWS platform in general. More specifically, serverless architecture challenges the system of local prototyping.
The guide below covers some of the known issues for local prototyping with serverless applications, general principles for getting started, and some best practices to achieve a stable local development process.
— by Farrah Campbell, Ecosystems Director @ Stackery
Another day of re:Invent is over and it’s all been amazing and overwhelming. And yes, the medals really do spin.
It was a huge honor to be named an AWS Serverless Hero a few weeks ago. As I prepare for more conference talks in the upcoming months, I’m reflecting on what it means to be granted this honor despite having only written my first lines of code earlier this year.
That smart, kind people all over the world not only want to learn more about a product I care about but want…
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. …