Serverless 101: Amazon EventBridge

Подписаться 18 тыс.

Просмотров 13 тыс.

50% 1

This video gives a high-level overview of Amazon EventBridge. Amazon EventBridge is a serverless event bus service that makes it easy to connect your applications with data from a variety of sources. EventBridge delivers a stream of real-time data from your own applications, software-as-a-service (SaaS) applications, and AWS services and routes that data to targets such as AWS Lambda. You can set up routing rules to determine where to send your data to build application architectures that react in real time to all of your data sources. EventBridge enables you to build event-driven architectures that are loosely coupled and distributed.

Опубликовано:

13 сен 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 11

@parrou3 Год назад

Sir, you gave me two lessons , one about AWS eventbridge and the second is about self-acceptance. thanks a lot :)

@joshd1732 Год назад

Now that's how you demystify a topic.

@iflux8821 Год назад

Well presented, sir! You are inspiring!

@neilfpv 9 месяцев назад

WOW! I love how you gave an example of a tightly coupled configuration and how to address it! Thanks a lot buddy! Awesome video! Do you own this channel? I'd like to subscribe.

@stevenjleee Год назад

Well explained video, thanks!

@victormwape8145 Год назад

Thank you🙏🙏🙏

@rammehar5531 10 месяцев назад

Great explained Sir Thank you very much.

@user-sh9ps7zj2q 2 месяца назад

Thanks for the video

@r0075h3ll 5 месяцев назад

Nice explanation.

@pikwiatkowski 11 месяцев назад

That's a great video; it nicely shows what an EventBridge is and how it differs from SQS. Good job! I have one observation. At 3:50, you mention that the payment service should drop a request for subscription creation into the bus. I believe it shouldn't send a request for subscription to be created but should instead send an event indicating that payment has succeeded (something that has already happened). The Subscription service can then listen for these events and create subscriptions. It's a subtle but quite important difference in my opinion. What are your thoughts?