EventBridge Atlas

EventBridge Atlas

  • Docs
  • GitHub

โ€บIntroduction

Introduction

  • Motivation
  • How it works

Getting Started

  • Installation
  • Setup
  • Populating your Metadata
  • Running with slate
  • Running with asyncapi
  • Running with docuowl
  • Running with flow (node diagram)

Customising

  • Adding metadata to schema

Parsers

  • What are parsers?
  • Slate Parser
  • Asyncapi Parser
  • Docuowl Parser
  • Flow Parser

Releases

  • v1.1.0
  • v1.0.0
  • v0.4
  • v0.3
  • v0.2
  • v0.1

Other Projects

  • awsicons.dev
  • mockit

Contributing

  • Contributing
Edit

Motivation

Event-Driven Architectures allow us to scale, be agile and keep our architecture decoupled. Ultimately I believe they help us work more efficiently.

When starting off with Event-Driven Architectures we spend time discovering our core business events, writing code to match them and maintain versions going forward.

Over a period of time more events are added to our domain, requirements change, and our architecture scales.

It can become difficult to know and understand what events are flowing within our domain.

I'm a huge fan of AWS EventBridge and I wrote this tool to help engineers gain and keep an understanding of events that flow through their domain.


I believe event discovery should be organic and be accessible to everybody.
EventBridge Atlas was built to solve this problem.

๐Ÿ‘‹ Let's Connect ๐Ÿ‘‹

If you are interested in connecting or reaching out you can find me on Twitter.

If you have any ideas or feedback I would love to hear them.


Last updated on 7/23/2021 by John Mitchell
How it works โ†’
Status ChecksStar eventbridge-atlas