Hello @DavidAlsh! Thanks for checking this one out and leaving a comment. I'd definitely recommend cargo-lambda. Removes all the pain away! Using zig is optional and only if you need cross compilation AFAIK
To be fair the only AWS related content is to use JSON to better utilise eventbridge and its broker. All other information is key to event-driven arch regardless of cloud provider.
Blameless culture in incident analysis 00:07 Blameless approach to learning from mistakes 05:26 Organizations are responsible for ensuring employees have accurate information and are not overworked. 10:37 Creating a blameless culture requires psychological safety and open-minded staff. 15:19 Personal health is more important than business success 20:03 Blameless culture is better than finding a culprit 24:39 Improving software delivery through smaller tasks and better organization 29:10 Creating a blameless workplace culture leads to improvement and growth. 33:56
0:00 Tao 4:12 Rule #1: Use JSON everywhere 7:43 Rule #2: Use standard event envelope 9:05 Rule #3: Use unique event ID 10:27 Rule #4: Use schemas and contracts 12:24 Rule #5: Maintain backward compatibility 15:22 Rule #6: Maintain a schema registry 16:26 Rule #7: Use an event broker 18:46 Rule #8: Use event supporting APIs 21:00 Rule #9: Evolve your events 22:38 Rule #10: Use the storage-first pattern 25:24 Rule #11: Trace your events 28:28 Conclusion
Great and fluent presentation. It would have been interesting to also mention the option of duplicating some data in different microservices in an eventual consistent way, rather than adding it to the event payload.
Great presentation. One thing I was a bit confused by. With an event driven architecture using a broker (like EventBridge) how can GraphQL play in that? I can see GraphQL as the more external client, but don't see how it would be used in an event broker style interconnect.
Fantastic as usual, Luc!!! Well prepared and delivered, this is a straight 10/10 score on presentation skills. To technical communities, please be aware that there exists an industry standard to describe a common and transport-independent set of event properties (especially metadata, such as id for idempotency, object references, ordering/sequencing semantics) called CloudEvents. If you're starting fresh (unlike Luc), consider adopting CloudEvents to save yourself time with designing common event schemas, SDKs, validation, and all the intricacies of transporting events over different (heterogeneous) channels.
Superb as always, Luc! If you had 15-20m extra, it’d be great to have a before/after for some of these topics - it’d help new practitioners understand what sort of tooling or stage they need to be before getting there
Arni, Good description 😉 Surprised no other comments. Questions: 1. What other game host options does AWS have? You mentioned FleetIQ is being trialed for other AWS projects. 2. Is FleetIQ now generally available? For what purposes? 3. Can Gamelift host available Steam/ Epic games besides those in development ? 4. How about for Parsec/ Steam Remote Play P2P multiplayer? 5. Links to pricing for Gamelift and FleetIQ? 6. Link for list of AWS edge locations. Are these any useful for reducing latency for any kind of gaming? Cheers ! 🤑
