๐Ÿ’ก

This post was written 3 years ago, it may be out of date, my opinion might have changed, and/or the writing may be embarrassingly bad. Read with caution.

Reactive Systems on AWS

Fall/2021 โ€“ 2 min read

AWS has a huge library of fantastic resources. This post highlights the recently released whitepaper about building reactive systems on AWS.

AWS has a huge library of fantastic resources. This post highlights the recently released whitepaper about building reactive systems on AWS.

โ€œReactive Systems on AWSโ€, helps line up The Reactive Manifesto and various AWS concepts and services.

I call out a few more details in the Twitter thread belowโ€ฆ

Tweet 1/8 ๐Ÿ‘‡ Next tweet

highlighting another @awscloud white paper leading up to @awsreinvent

this time, let's look at Reactive Systems on AWS. available as a PDF at https://d1.awsstatic.com/whitepapers/reactive-systems-on-aws.pdf

๐Ÿงตโ˜๏ธ #cloud #devops

Tweet 2/8 ๐Ÿ‘‡ Next tweet ๐Ÿ‘† Start

this thread is available unwound at https://t.co/mpdUK5FbIV

yesterday's thread at https://markn.ca/2021/practicing-continuous-integration-and-continuous-delivery-on-aws/

๐Ÿงตโ˜๏ธ #cloud #devops

Tweet 3/8 ๐Ÿ‘‡ Next tweet ๐Ÿ‘† Start

this white paper is all about how to adapt the elements in The Reactive Manifesto, https://www.reactivemanifesto.org/, to an @awscloud environment

these systems are "more flexible, loosely-coupled and scalable"

๐Ÿงตโ˜๏ธ #cloud #devops

Tweet 4/8 ๐Ÿ‘‡ Next tweet ๐Ÿ‘† Start

the manifesto lays out four key areas for reactive systems:

1. responsive 2. resilient 3. elastic 4. message driven

the white paper follows this structure and adds observability & tracing

๐Ÿงตโ˜๏ธ #cloud #devops

Tweet 5/8 ๐Ÿ‘‡ Next tweet ๐Ÿ‘† Start

I'll say this right now, tracing is absolutely critical to the success of any loosely coupled system. trying to figure out which events/messages related to which issue is a nightmare if you haven't planned ahead

that ๐Ÿง  is echoed more politely in the paper

๐Ÿงตโ˜๏ธ #cloud #devops

Tweet 6/8 ๐Ÿ‘‡ Next tweet ๐Ÿ‘† Start

the paper walks through example use cases (like #adtech) that you should abstract as much as possible.

you might not be serving ads but your problem set might look similar

there's also blocking & synchronicity. these are great topics to dive deeper into

๐Ÿงตโ˜๏ธ #cloud #devops

Tweet 7/8 ๐Ÿ‘‡ Next tweet ๐Ÿ‘† Start

the tail of the paper lines up some key @awscloud services & features with the reactive elements.

this is ok, but honestly, I would prefer a more neutral take or links out to projects that show specifics.

the middle ground doesn't hold much value here

๐Ÿงตโ˜๏ธ #cloud #devops

Tweet 8/8 ๐Ÿ‘‡ Next tweet ๐Ÿ‘† Start

all-in-all this is an interesting paper that highlights a great cloud-native approach to system design.

it's deep enough to give you an idea of the advantages but you'll need more if you're going to actually build a reactive system on @awscloud

/๐Ÿงตโ˜๏ธ #cloud #devops