# eventbridge Published articles for eventbridge. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Micro Service Events (AWS EventBridge vs. SNS) DevFeed: [Micro Service Events (AWS EventBridge vs. SNS)]() Original publisher: [Read original article]() Author: Kristian Müller Published: 2022-09-16T12:06:51Z Content type: comparison Language: en Sources: [Homegate Engineering Blog - Medium]() Topics: [event driven](), [Messaging](), [Amazon Web Services](), [Amazon Simple Queue Service (SQS)](), [Publish-subscribe pattern](), [Architecture & Design](), [AWS Lambda](), [Amazon API Gateway](), [DynamoDB](), [Amazon S3](), [TypeScript]() Tags: [api](), [api-gateway](), [architecture](), [aws](), [aws-eventbridge](), [aws-sns](), [data](), [data-processing](), [database](), [dynamodb](), [event](), [event-driven](), [eventbridge](), [eventbus](), [events](), [gateway](), [lambda](), [messaging](), [microservice-architecture](), [s3](), [sns](), [sqs](), [typescript]() ### AI overview This article examines Homegate's event-driven microservice architecture on AWS and compares Amazon SNS with EventBridge as messaging infrastructure. It describes how services use SNS, SQS, Lambda, API Gateway, DynamoDB, and S3, and explains that EventBridge has a different focus, so replacing SNS is not necessarily the right question. ### Source excerpt During the last few years, we've been busy rebuilding the Homegate platform in an event driven, micro service architecture based on AWS. One of the most important buildings blocks, or shall we rather say the mortar that connects the building blocks, is the way our services send events to each other. While Amazon offers its notification service SNS since more than 12 years; in 2019 it started a newcomer in the messaging bus field by introducing EventBridge. This was very interesting to us as we're using SNS a lot. Bus on a Bridge (Photo by "Blue Elf" on Wikimedia Commons) As EventBridge was introduced and gained traction we asked ourselves what advantaged we would gain by switching our SNS based service glue to EventBridge. Maybe this turned out to be the wrong question for us. Let's look at our system to see why. Micro Services Connected by SNS Homegate is connecting dozens of services via SNS right now. Those services range from single purpose Lambda functions written in TypeScript to database heavy services using Aurora or DynamoDB and Step Functions sending events to other services. Some of the services are also interfacing external APIs such as Salesforce or SendGrid. Here our Lambda functions can call APIs when needed. On the other hand, we have web services to be called as APIs by other systems and end users. This is mostly achieved via API Gateway. A typical service connects to the system by subscribing to events needed to fulfill its purpose. Those inbound SNS events are then ingested via SQS allowing for orderly data processing and DLQs to handle errors. Outgoing results are pushed back to the system in form of events to a SNS topics. As Marko Savic has pointed out, we're also utilizing S3 to store and replay those events if needed. Basic AWS Lambda function connected via SNS If we would replace the SNS topic by streams on the EventBridge we would initially gain the same functionality by utilizing SQS as well. However, EventBridge has a different focus. Let ## Should we consider migrate to Amazon EventBridge from Amazon SNS + SQS ? DevFeed: [Should we consider migrate to Amazon EventBridge from Amazon SNS + SQS ?]() Original publisher: [Read original article]() Author: Guillaume Lannebere Published: 2022-02-01T14:45:47Z Content type: article Language: en Sources: [betclic-tech - Medium]() Topics: [Amazon EventBridge](), [Amazon Simple Queue Service (SQS)](), [event driven](), [Architecture & Design](), [Microservice](), [Amazon Web Services](), [Monitoring](), [Latency]() Tags: [amazon-eventbridge](), [architecture](), [aws](), [event-driven](), [eventbridge](), [latency](), [microservices](), [monitoring](), [net](), [sns](), [sqs]() ### AI overview The article examines Betclic's event-driven architecture requirements and its early-2019 decision to combine Amazon SNS with Amazon SQS. It presents the decision in the context of unpredictable traffic, multiple consumers, event replay, monitoring, schema management, language interoperability, analytics, autoscaling, low latency, high availability, AWS integration, and cost. ### Source excerpt Should we consider migrating to Amazon EventBridge from Amazon SNS + SQS? In early 2019, Betclic was in a corner, and we decided to migrate to microservices approach and migrate to the cloud. The first step of this change was the implementation of an Event Driven Architecture (EDA). Betclic presentation Before speaking of architecture and EDA, it's essential to know what Betclic is doing to understand our choice quickly. Betclic is a French online gambling company. Betclic operates in Sports betting, horse race betting, and online poker. The specificity of gambling is that we don't have predictive traffic. We have high traffic peaks during significant events and weekends. We can see an example of traffic on a soccer event: Example of trafficEDA wishlist When beginning 2019, we did a workshop to identify the key features of our ideal EDA; we would like something: allowing multiple reads: the same message can be read by various services with error recovery: in case of error, we would like to replay events easy to monitor: particularly with Datadog, our centralized monitoring solution with schema registry language-agnostic: we use 3 main languages .net, Kotlin, and Typescript (for Lambda), and the chosen solution must work with all languages with analytics capabilities: we would like to integrate all our events of EDA in our data lake fully managed with auto scaling: essential feature for us; we have unpredictable traffic with big spikes at the end of matches, so we need to have an EDA to be able to absorb our spikes with low latency and high availability: also an essential feature, we would like our EDA to serve critical use cases for our final users, so we want something the most real-time and the most available possible well-integrated with AWS services: EDA is one of our first bricks in the cloud, but we want something to help us to migrate to AWS easy to use: we want all the time something easy to use :) but here it's particularly true because EDA is a centralized ## EventBridge Schema Registry -- what it is and why it matters for Serverless applications DevFeed: [EventBridge Schema Registry -- what it is and why it matters for Serverless applications]() Original publisher: [Read original article]() Author: Alex DeBrie Published: 2019-12-02T00:00:00Z Content type: article Language: en Sources: [Serverless Blog]() Topics: [Serverless](), [Structured-data]() Tags: [applications](), [aws](), [aws-lambda](), [cloud-computing](), [eventbridge](), [faas](), [function-as-a-service](), [infrastructure-as-code](), [news](), [registry](), [schema](), [serverless](), [serverless-architecture](), [serverless-framework]() ### AI overview The article explains that the EventBridge Schema Registry documents event schemas and improves their discoverability within the event domain, with a focus on Serverless applications. ### Source excerpt The EventBridge Schema Registry helps document your event schemas and add discoverability to the event domain. See why it's useful here. ## EventBridge Use Cases and Examples DevFeed: [EventBridge Use Cases and Examples]() Original publisher: [Read original article]() Author: Philipp Müns Published: 2019-07-30T00:00:00Z Content type: tutorial Language: en Sources: [Serverless Blog]() Topics: [Amazon Web Services](), [event driven](), [serverless framework]() Tags: [aws](), [aws-lambda](), [cloud-computing](), [engineering](), [event-driven](), [eventbridge](), [examples](), [faas](), [function-as-a-service](), [how-to](), [infrastructure-as-code](), [serverless](), [serverless-architecture](), [serverless-framework](), [use-cases]() ### AI overview This tutorial introduces AWS EventBridge and shows developers how to use it with Serverless Framework to build event-driven applications. ### Source excerpt AWS recently announced the EventBridge offering which helps developers build universal, reliable and fully event-driven applications. Come see how to use it with Serverless Framework