AWS re:Invent 2022 - Building Serverlesspresso: Creating event-driven architectures (SVS312)

[@arjenwassink7523]

Awesome presentation. In less than an hour a summary of what I teach students in three months! Makes me🙂

[@awssupport]

We're happy to hear that you liked the presentation, Arjen! 😀 ^AK

[@JamesBeswickD]

Thanks Arjen! That's great to hear!

[@ClaudetteMillette-s8b]

Great presentation. Thanks James.

[@JamesBeswickD]

Thank you!

[@atehrosius]

amazing presentation. 👏🏿👏🏿. 👏🏿

[@confused6526]

Wow... awesome!

[@JamesBeswickD]

Thank you so much!

[@liorzamir]

Like a pro

[@stefanstojanovic7596]

What was the main reason to use IOT Core? If you needed messaging system for microservices to communicate, could you be using SNS/SQS? What was the main reason you went with IOT Core? Thank you.

[@praskatti]

SNS/SQS are not built for websockets from what I understand. They are primarily meant to decouple two systems and fan out.

[@JamesBeswickD]

Hello! SNS can deliver messages to other backend services, HTTP and SMS endpoints. But in our case we need to communicate back to a SPA-style application, so we needed a WebSocket delivery. IoT Core provides a very elegant and cost-effectively way to implement messages over MQTT so that's how it was chosen. HTH!

[@deepav9763]

One question, did you normalize the events for your workflow to consume? What I mean by this question is were the events having a common "event" Json which was then sent to the workflow?

[@JamesBeswickD]

Hi Deepa! No, each service followed its own event format. After building the prototype, we then found it's better to produce event schema, definitions, and naming conventions ahead of time so all services produce similar-looking events.

[@deepav9763]

@@JamesBeswickD Thanks for your response. I think normalizing events helps make sense of data better. I have always struggled with this concept of disparate events, because it is going to be harder to make sense of data with disparate event formats.

[@BlueDhow-uf7kd]

What were the total hours taken to develop?

[@architectelevator]

Classic legacy integration challenge: scalable front-end and limited legacy system capacity :-)

[@serhatuyanmis1493]

Thank you for this wonderful content. James is an amazing choice when it comes to presentations. It is easier to learn once he is the one who explains it. Thanks James!!!! 🩷

[@JamesBeswickD]

Thank you - you are too kind!