For me #TheServerlessBook is the culmination of all the mistakes, lessons and realisations from the past 5 years of working on enterprise-grade AWS serverless software.
It is the book I wish I’d had on my desk in 2019 when I was leading my first serverless engineering team
Big day today: #TheServerlessBook is out! ✨
📗 Ebook available now https://t.co/Ct94QLUCCg
📘 + On the @OReillyMedia platform - DM me for 30-day trial code! https://t.co/AwRLDftPsI
📙 Paperbacks should start shipping in 4 weeks - preorder to get it first https://t.co/bjCGp5c6bq
@AWSbrett Nice! That looks sensible Brett. And what do the stack files look like, do you define all resources inside the constructor or some other approach?
@MicheleBertoli@Meta@EnodeHQ Congrats Michele! Sounds like a super cool project. I remember you saying this is the area you wanted to work in one day, so very happy to hear it’s now a reality! 🙌
@gunnarmorling The danger here is becoming too precious about production systems. This leads to fragility and a fear of change. Of course the default should be VCS but there is always a time/place for more direct changes. As long as they are done with the same level of scrutiny, care, control
@balajmarius Thanks Marius, your support means a lot!! What a dream team we had (with Xin and BiggaMasta) - never shipped so much code in my life! 🚀
Let me know what you think of the book!
@sheenbrisals returns for Ep. 62!🚀
Sheen shares his journey from software engineer to #AWS Hero to published author. Learn what inspired his book, how the community helped, & MORE on this exciting episode!
🎧 Spotify: https://t.co/VumSiHUgPl
📺Youtube: https://t.co/tw29SEqYom
Still one of the most compelling and interesting serverless use cases, Luc talking us thru PostNL’s cloud journey @ServerlessCWL. Christmas is just another day for this guy! Spikes, what spikes?
A few MUST read books about architecture:
👉 Learning Systems Thinking
👉 Head First Software Architecture
👉 Serverless Development on AWS
👉 Learning Domain-Driven Design
👉 Building Event-Driven Microservices
��� Designing Distributed Systems.
Any other for my bookshelve?
@coltmcnealy What would message transforms in the broker look like Colt? Could this include blending data across msgs into a single consumed msg? And by Workflow API do you mean something like a workflow engine/durable execution?
Such a good point! Also helps to view all those early decisions through the one-way/two-way door lens. Some you can reverse out of as you learn more and evolve the system, some you are stuck with forever. Try to delay one-way decisions for as long as possible
We build knowledge over time, but most of our system decisions are made at the start.
That’s why we need to build systems that can evolve over time.
well said @boyney123 👏