0.0.1 • Published 1 year ago

cdk-schema-watcher v0.0.1

Weekly downloads
-
License
MIT
Repository
github
Last release
1 year ago

MIT License PRs Welcome

All Contributors

Watch on GitHub Star on GitHub

Read the Docs | Edit the Docs | View Example

Core Features

  • 🔎 Consumers sign up to any changes to events
  • 🔔 Get notified anywhere you want
  • 📊 Plugin architecture
  • ⭐ Setup in minutes

All powered by CDK

Why use SchemaWatcher?

SchemaWatcher is a CDK construct that can help you scale your event-driven architecture by allowing event consumers to subscribe to schema changes.

Amazon EventBridge is a serverless event bus that lets you receive, filter, transform, route, and deliver events, you can write custom event producers and listen to them downstream with custom rules and consumers.

Amazon EventBridge also offers a Schema Registry. EventBridge provides schemas for all events that are generated by AWS services and when you turn on schema discovery it will automatically detect and provide schemas for your custom events (OpenAPI and JSON Schemas).

When producers make changes to events or raise new events onto your EventBridge bus, EventBridge will automatically picks up these changes (with schema discovery turned on), and either make new schemas or update schemas for you.

Consumers can use these schemas to validate events, understand what is in the payload of events or even document their event-driven architecture using tools like EventCatalog.

As time goes on your event-driven architectures will grow, keeping on top of producer and consumer relationships can be hard, we are often told that “producers should not know about consumers”. Technically there is an element of truth to this, but you will often find this leads to some problems…

So, what if we could notify consumers of incoming breaking changes in our schema’s? Notifying consumers could help us manage our event-driven architectures and scale them as our organisations scale.

SchemaWatcher was designed to help developers manage their event-driven architecture. Notifying consumers of any changes to event structures can help catch issues before you see them in production.

Read more on the website

Getting Started

You should be able to get setup within minutes if you head over to our documentation to get started 👇

➡️ Get Started

Or run this command to install the cdk construct

npm i cdk-schema-watcher

Example using SchemaWatcher CDK construct with the Slack Plugin

Configure the construct with the Slack Plugin.

import { SchemaWatcher } from 'cdk-schema-watcher';
import { SlackNotifier } from 'cdk-schema-watcher/plugins';

new SchemaWatcher(this, 'MyTeam', {
  type: 'All',
  sources: ['myapp.users', 'myapp.orders'],
  plugins: [
    new SlackNotifier({
      API_KEY: process.env.SLACK_API_KEY,
      CHANNEL_ID: process.env.SLACK_CHANNEL_ID,
    }),
  ],
});

Example outputs

New version of schema found. alt

New event found alt

Contributing

If you have any questions, features or issues please raise any issue or pull requests you like. We will try my best to get back to you.

License

MIT.