AWS Event Bridge

  • An Event Bus that helps in integrating with different applications.
    • Applications can be AWS services, System, applications or software as a service application.
  • Suitable for event driven architectures.
  • Fully managed
  • Pay with what you use model.
  • Formally called as cloud watch events.
    • Cloud watch events did not support custom apps as well as SAS applications outside AWS.
  • With Event Bridge we can create event driven architecture.
    • If someone terminates instances in our autoscaling group. We can log this action in cloud watch.
    • We need to automatically deploy our code using code pipelines at 11 PM every day.
    • If a user deactivates his account from our application, we may want a feedback from him. We can trigger an email using SNS or SES or may even schedule a call with him.
  • High-level diagram of an Event Bridge operation.


  • A single rule can have at max five targets.
  • Important terms in event Bridge
    • Event
      • And event indicates a change in an environment
    • Rules
      • A rule matches incoming events and routes them to targets for processing.
    • Targets
      • Target application of your rule. A target processes events.
    • Event bus
      • An event bus receives events. When you create a rule, you associate it with a specific event Bus, and the rule is matched only to events received by that event bus.
      • An event bus acts as a parent to rule.
  • Helps to simplify product software architecture
    • Moving from monolithic to micro service architecture.
    • Reduces the cost of decoupling the services together.
      • Change in upstream service may impact downstream services and vice versa.
    • Addresses the issue of availability with synchronous API’s
      • Services may go slow or there may even be an outage in essential services.
    • Events are central to event Bridge, events are observable, not directed.
      • API’s use directed commands.
      • Events are observed and based on that actions are taken.
    • Event Bus provides an endpoint, where event, producer and send events
    • The router manages directing and fitting those events to appropriate downstream consumers.
      • Consumers can get the events they care about while producers remain decoupled.
    • Amazon event bridge is a server-less event, bus service for SAAS and AWS services.
      • Fully managed, pay as you go.
      • Native integration with SAAS providers.
      • 90+ AWS services as sources.
      • 17 AWS services as targets.
      • $ per million events put into the bus.
      • No additional cost for delivery.
    • Key benefits of Amazon Event Bridge
      • Decoupling
        • Helps to maintain and ensure applications remain decoupled.
      • Simplified event routing
        • Event routing in simple path what is well but our handling can be difficult to Orchestrate.
        • An event Bus can help manage Evors across multiple workflows. This helps in services to remain simple and focus on listing and creating respective events.
      • Improved availability
        • Event, which can help to improve availability. Synchronous API’s are made vulnerable to failures. Asynchronous API’s provide more resilience and right architecture design can improve availability.
      • Third party integration
        • Instead of using polling or web hooks. You can ingest data seamlessly, and in near real-time using events. Event Bridge offers SAS integrations where providers treat data as events.

Comments

Post a Comment

Popular posts from this blog

High Level Diagrams(HLD's)

Image
High Level Diagram for Building a Serverless application using Step Functions, API Gateway, Lambda, and S3 in AWS HLD for Building and Troubleshooting a Serverless Web
Read more

Infrastructure Setup using Cloud Formation Templates

Services Required to create CICD Code Build Build code and deploy image in jfrog Code Pipeline Has (Continuous Integration Continuous Deployment)CICD flow Cloud Formation To deploy and create infrastructure we use yml files. S3 Store our data packages and yml files which are used by CFT. ECS To deploy our application on fargate servers We can also create our manual EC2 instances from pipeline. Secrets Manager Manages all the secrets. ELB/ALB Elastic/Application Load Balancer To map context paths of different services GitHub Stores our code Jfrog Used to store all the docker images Dockerfile Used to create a customised docker image Scanning for Vulnerabilities free code Sonarcube Checkmarx Twistlock Cloudwatch Used to store logs We create log group for each of instances Lambda Functions Used for serverless technologies. Creating a new Environment Create the YML images of the different resources required in the environment. The CFT templates are stored in S3 or can be uploaded from syst...
Read more

AWS Summaries

Database Summary  RDS(OLTP) SQL My SQL Post Gre SQL Oracle Aurora Maria DB Dynamo DB(No SQL) Redshift OLAP Elastic cache Memcached Redis RDS runs on virtual machines We cannot log into this operating systems however Patching of our RDS Operating system and DB is Amazons responsibility. RDS is not server-less. Aurora surverless is seven less which is an exception. Dynamo DB is server-less. There are two types of backups for RDS Automated backups Database snapshots Read replicas Can be multi availability zones. Use to increase performance Must have backups turned on. Can be in different regions. Can be MySQL,PostgreSQL,Maria DB, Oracle, Aurora, SQL Server is not supported. Can be promoted to master, this will break read replica. Multi availability zone Used for DRG only and not performance. You can force a fail over from one availability zone to another by re-booting the RDS instance. Encryption at Rest Is supported for My SQL, Oracle, SQL server, Postgre SQL, Maria DB and Aurora. En...
Read more