Serverless Event Gateway Pattern

<h1>Introduction</h1> There are many times when developing our serverless solutions when we need to interact with existing legacy systems or 3rd party services within our wider domain; and they are unable to publish and consume events from your central <a href="https://docs.aws.amazon.com/eventbridge/index.html" rel="noopener ugc nofollow" target="_blank">Amazon EventBridge</a> bus directly due to technology or framework limitations. <pre> This could be simply that they can't utilise the aws-sdk or iam in code, but can perform REST API requests.</pre> <img alt="" src="https://miro.medium.com/v2/resize:fit:700/1*OwuOl6UMIakjz7GUu-3zEA.png" style="height:151px; width:700px" /> This quick article discusses using the ‘Event Gateway Pattern’ alongside Amazon EventBridge and <a href="https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-api-destinations.html" rel="noopener ugc nofollow" target="_blank">Amazon EventBridge API Destinations</a> to allow this flow between systems both ways i.e. consuming and publishing based on domain events. <a href="https://blog.serverlessadvocate.com/serverless-event-gateway-pattern-7578b59730fe">Visit Now</a>