John Gilbert

Author, CTO, Full-Stack Cloud-Native Architect, Serverless-First Advocate

[John Gilbert @johngilbert01]

ICYMI, the 2nd edition of my book is available:

Architecture Patterns for #Serverless Systems: architecting for innovation with event-driven #microservices and micro frontend

New chapters, more examples, various updates and some good ole refactoring

https://t.co/vVvmPGXbCV

[John Gilbert @johngilbert01]

#Serverless: Applying Hexagonal Architecture at Multiple Levels

https://t.co/9Wz446EKQg

[John Gilbert @johngilbert01]

@theburningmonk What really concerns me is that this feature is FIFO only. I never assume that events arrive in order. It’s nice when they do, but never assume… Like when replaying events from an archive when a subscriber may have already consumed some of them…

[John Gilbert @johngilbert01]

@theburningmonk At first glance I assumed this feature was just like EB archives, and it may well be. But the press release seems to conflate replay/archive with resubmit/dlq. I use replay to seed new services or fix those beyond the help of a dlq. Hopefully the press release just poorly worded

[Bilgin Ibryam @bibryam]

Summary: It is a 5x🌟 book on serverless:

▶️Has the right number of patterns, level of details, and levelling-up;
▶️Contains uniques takes and ideas;
▶️Despite it uses mainly AWS services, patterns and the level of details is applicable to other cloud providers;

[Bilgin Ibryam @bibryam]

3) Trilateral API:

Each service can have up to three APIs: one for the events it consumes, another for the events it produces, and one for its synchronous interface. Not all are required.

▶️Reminded me of: Turning Microservices Inside-Out
https://t.co/1KKQacF79B

[Bilgin Ibryam @bibryam]

2) There are three high-level autonomous service patterns that all other services fall under

▶️Backend for Frontend (BFF),
▶️External Service Gateway (ESG)
▶️Control Service

[Bilgin Ibryam @bibryam]

1) Autonomous service - owns all the resources it needs to continue to function even when other services cannot. Its building blocks are: Command, Publish, Consume, Query (CPCQ)

CPCQ - this is the core serverless pattern👇

[Bilgin Ibryam @bibryam]

Book review 🌟Software Architecture Patterns for Serverless Systems🌟 by John Gilbert

TLDR: dissects the #serverless landscape into key patterns and mindset that everyone developing cloud applications must know!

🧠Top 3 ideas from this book are: 🧵👇

[John Gilbert @johngilbert01]

@theburningmonk Cost is a key metric in the #serverless pay-per-sip model. Tuning on cost: teaches us about our services and the cloud services we use; drives creativity; improves performance; and reduces waste. It’s addictive!!! And when it’s not enough, switch, that one piece.

[John Gilbert @johngilbert01]

@theburningmonk I don’t think I would classify where they ended up as a monolith. Relative to where they started, maybe. But everything is relative… #serverless first!!!

[John Gilbert @johngilbert01]

@theburningmonk I’ve had a lot of success with hiring strong react developers and teaching them #serverless BE

[John Gilbert @johngilbert01]

@theburningmonk When our parents put men on the moon it was a challenge to work within a very limited set of resources. Every bit counted. Now that the bytes are ever plentiful, it is our challenge not to waste them. #serverless

[John Gilbert @johngilbert01]

@theburningmonk I totally agree and I think the issues revolve around how we sculpt our services: https://t.co/p3Adgxzxba

[John Gilbert @johngilbert01]

@pomSense Glad the book is helpful!!!
Great question! Good addition for 2nd edition.
Add a subsysX.external prefix to the source.
U can even do this in the egress rule w a transform.
Then u have more control in the rules.

[John Gilbert @johngilbert01]

@theburningmonk @boyney123 @donkersgood @sheenbrisals @heitor_lessa @nickste https://t.co/kRh54T1unG

[John Gilbert @johngilbert01]

High Availability vs. Honest Human Error

We have to take honest human error into account if we truly value high availability

https://t.co/jxWeMkMNbu

#Serverless #CloudNative #AutonomousServices #EventFirst #HighAvailability

[John Gilbert @johngilbert01]

this moneyball movie scene always reminds me of the #Serverless #CloudNative #AutonomousServices journey. it is great inspiration whenever the journey feels like an uphill battle.

https://t.co/cxnRqDpcsZ

[John Gilbert @johngilbert01]

@shesupplypi Great question! Many actors interact with an order. A customer places an order, tracks it and views order history. Various actors perform various fulfillment activities. They can all be independent services with the events as the contracts between them.

[John Gilbert @johngilbert01]

#Serverless: Focusing on Actors and their Activities
Applying the #SingleResponsibility Principle

https://t.co/hFypADvtUr