Jason C-Williams

Cloud Architect at City

[Jason C-Williams @JCDubs]

I just published 🌍 Handling Cross-Region SSM Parameters in AWS CDK https://t.co/YFmMEPx9rd

[Jason C-Williams @JCDubs]

I'd like to introduce the Janus project 🎉. A new open source project that implements a Serverless authorisation pattern backed by the Cedar policy language and evaluation engine.

Feel free to check out the project. Contributions are more than welcome.
https://t.co/WoN3V1BinH

[Jason C-Williams @JCDubs]

I just published 🔄 You Don’t Need Ordered Events, You Need Smart Events 🧠 https://t.co/bTODrEP29h

[Jason C-Williams @JCDubs]

Attending @AWSNorthConf today.

[Leighton @Leighton]

Learn more about Leighton's culture, and what makes our AWS team tick through the eyes of our most recent recruit, Dan Mackenzie 👇
https://t.co/7Bys67AzPQ

#LifeAtLeighton #AWS

[Leighton @Leighton]

We’re in Manchester for the @AWScomsum

Looking forward to talks on when to use serverless vs containers, demystifying serverless development, and practical tips for building modern cloud applications.

If you're here, come and say hi! 👋

#comsum2025

[AWS North Community Conference @AWSNorthConf]

The closing keynote at AWS North Community Conference will be delivered by none other than @lucamezzalira, Principal Solutions Architect at @awscloud, author of Building Micro-Frontends and creator of the @deararchitects newsletter. 🎉

#AWSNorthCommunityConference #NorthEastTech

[Jason C-Williams @JCDubs]

I just published 🏗️ Building Better CDK Stacks: Organise Resources for Faster ⚡ and Safer 🔒 Cloud Delivery https://t.co/mLdTLqUnq9

[Leighton @Leighton]

Are you attending this year's AWS re:Invent for the first time and are curious of what to expect?

Read @LeeJamesGilmore's blog where he shares his top takeaways from last year’s conference in Las Vegas 👉 https://t.co/W726pJBCTX

#AWSreInvent

[AWS Security Digest @AwsSecDigest]

🛎️ AWS Security Digest 225 is out!

1️⃣ AWS CDK and SaaS Provider Takeover by Ryan Gerstenkorn
2️⃣ AWS Detection Engineering — Architecting Security Logging at Scale in AWS by Muh. Fani Akbar
3️⃣ Build a Real Time Threat Detector with IaC by Rich Mogull

https://t.co/XJywZWDhl1

[Jason C-Williams @JCDubs]

I just published AWS CDK & DynamoDB GSIs ⚡— Beating the One-Index-Per-Update Bottleneck 🚀 https://t.co/QLmQ46aZC9

[Jason C-Williams @JCDubs]

How long does it normally take to get a response from Strava support when creating a zendesk support ticket? I sent an email yesterday but no response yet @StravaSupport

[Jason C-Williams @JCDubs]

New blog: can Claude 3.7 Sonnet build a production-ready, modular CRUD API from scratch using clean code and cloud best practices? 🤖 https://t.co/0r7rpJCUrP

[Jason C-Williams @JCDubs]

@LeeJamesGilmore He might be a hero but he’s not a Serverless hero 😀

[Jason C-Williams @JCDubs]

@dreamorosi This has caught me out all day! Thanks for this :)

[Jason C-Williams @JCDubs]

@LeeJamesGilmore Stop looking at my code! 😀

[Jason C-Williams @JCDubs]

Checkout my latest blog post on handling large event payloads in EDA workloads on AWS. https://t.co/JP1kywFLoV

[David Boyne @boyney123]

Agility with event-driven architecture ⚡️

Event-driven architectures provide agility to engineering teams and organisations. Let’s dive into more details about how and why.

⭐️ Evolutionary Architecture

1. Common saying with event-driven architectures, is that producers do not know about consumers, this allows consumers to be disconnected to producers.

2. Without the coupling of producer and consumer, consumers can come and go easily.

3. As business requirements change, we can add or change consumers without impacting producers or other parts of our architecture.

4. Discoverability is important for consumers to know what they can subscribe to, documentation can help here.

⭐️ GROW ENGINEERING TEAMS

1. Using events to communicate between teams/domains is a popular way for engineering teams to scale.

2. Event-driven architectures allow us to remain decoupled, and evolve and adapt teams to meet business requirements/features.

3. Event-driven architectures couple with domain driven design very well. Define boundaries in your organisation and create teams around that. Understand how Conway’s law can impact this.

⭐️ CONNECTING EXTERNAL SYSTEMS

1. Event-driven architectures are not just about the events we raise internally within our business or organisation, but events we can also consume and share with others.

2. Modern applications integrate with external systems all the time, consume events from other applications and process them internally (webhooks common pattern)

3. Expose events to other consumers outside your domain/business, can also provide value.

4. Bi-directional events are powerful, reacting to real-time events, processing them and passing them back to the business that produced them.

⭐️ IMPACT ISOLATION

1. Producers are often disconnected from the consumers, if consumers fail then impact is isolated.

2. Event-driven architectures can give availability as components/services are isolated and use events to communicate.

3. When consumers fail you have options to deal with this. Having idempotent consumers help, without them you may run into strange side effects.

⭐️ PUBLISHING FUTURE EVENTS

1. Some producers may publish events into the architecture even if no downstream consumers are listening to them.

2. If you know your event is valuable to the organisation, you may want to publish it and have the option to listen in the future.

3. If you use this pattern, maybe consider the costs in doing this, does your broker charge for events published?

Read more with extra resources 👇
https://t.co/KNtCPXhVIu

[Peter Finch @PeterFinchGolf]

HUGE @shotscope GIVEAWAY!!! 🎁🏌️‍♂️⛳️😍

Win 1️⃣ item of WHATEVER you want from the ShotScope website!!!!

TO ENTER ⬇️

- ❤️ and RETWEET this post
- FOLLOW me and @shotscope

[AWS Security @AWSSecurityInfo]

Transforming transactions: Streamlining #PCI compliance using AWS serverless architecture. Focus on building robust and secure payment solutions without getting lost in the complexities of compliance https://t.co/NnOfq1sIdG