Amazon EventBridge is a serverless event bus that makes it easy to connect applications together using data from applications, integrated Software-as-a-Service (SaaS) applications, and AWS services.   EventBridge delivers a stream of real-time data from event sources, and routes that data to targets like AWS Lambda.  EventBridge makes it easy to build event-driven applications because it takes care of event ingestion and delivery, security, authorization, and error handling for you.


The Amazon EventBridge Schema Registry (EBSR) stores event structure - or schema - in a shared central location and maps those schemas to code for Java, Python, and Typescript so it’s easy to use events as objects in code. It is possible to connect to and interact with the schema registry from the AWS Management Console, or REST APIs.  The EBSR stores a collection of easy-to-find event schemas and enables to download code bindings for those schemas in IDEs to represent the event as a strongly-typed object in code. Schema from the event bus can also be automatically added to the registry through the schema discovery feature.


The EventBridge Schema Registry stores schemas in OpenAPI 3.0.0 format.  OpenAPI is a formal specification surrounded by a large ecosystem of tools, which includes everything from front-end user interfaces, low-level code libraries and commercial API management solutions.


To perform the design of an EBSR schemas using OpenAPI 3 with Hackolade, you must first download the EventBridge plugin.  This plugin is strictly compliant with version 3.0.0 of the OpenAPI specification and is based on the Hackolade plugin for OpenAPI but independent of it so it can closely match the AWS requirements for the EBSR schema.


Hackolade was specially adapted to support the design of EventBridge schemas, including all the necessary AWS metadata for the schema.  


The application closely follows the terminology of the specification.  The visual tool puts the focus on what really matters in an API: the schema of the information being exchanged between systems.  At the same time, it provides assistance to modelers and does not require perfect mastery of the OpenAPI 3 syntax.  It generates validated files that are syntactically correct and compatible with the specification thereby greatly improving productivity and quality. The software also allows retrieval (reverse-engineering) of existing schemas in the Amazon EventBridge Schema Registry, as well publishing (forward-engineering) of new schemas (or new versions of a schema).


The diagram below results from the reverse-engineering of AWS event aws.glue@GlueDataCatalogTableStateChange



Structure

The EBSR for any AWS account in a region is made of:

  • an AWS event schema registry
  • one or more custom schema registries

Each EBSR schema corresponds to a single Hackolade model file.  While the structure of the event schema is maintained in the Components tab, the schema metadata is visible in the Schema properties tab.



Data Types

The OpenAPI specification used by EBSR describes primitives (or scalar) data types which can have an optional property modifier, format, plus a file primitive type.  Complex types such as arrays and sub-objects, plus combinations thereof, are also allowed.


       


Event metadata

A number of properties describing the registry and each schema can be reverse-engineered and maintained in the model:

 


Components

Component objects hold a set of reusable objects that can be used across multiple endpoints in the same API: schema, parameter, request body, response, example, header, security scheme, link, or callback. All objects defined within the components object will have no effect on the API unless they are explicitly referenced from properties outside the components object by using a $ref reference in any path item.


As you expose more resources and operations against your API, your API may repeat a lot of existing parameters or response descriptions in many different paths and operations.  By creating reusable component objects, you avoid time-consuming rewriting as well as the risk of inconsistencies.


Data types can be objects, but also primitives and arrays. This object is based on the JSON Schema Specification Wright Draft 00 (a.k.a. Draft-05) and uses a predefined subset of it. On top of this subset, there are extensions provided by this specification to allow for more complete documentation.



Consult this page or more information on how to use definitions.  For OpenAPI, you should limit yourself to Hackolade model definitions.


Forward-Engineering

The files describing the RESTful API in accordance with the OpenAPI specification OAS are represented as JSON objects and conform to the JSON standards.  Hackolade generates OpenAPI documentation in JSON format or YAML format.  The schema exposes two types of fields. Fixed fields, which have a declared name, and patterned fields, which declare a regex pattern for the field name. Patterned fields can have multiple occurrences as long as each has a unique name.  The OpenAPI representation of the API is made of a single file. However, parts of the definitions can be split into separate files, at the discretion of the user. This is applicable for $ref fields in the specification as follows from the JSON Schema definitions.




Reverse-Engineering

This function lets you take a schema from either the AWS even schema registry, or any custom schema registry file in JSON or YAML format and generate Hackolade components.  Then, you may enrich the model with comments, generate standard Hackolade documentation, and make the schema evolve to apply to the EventBridge Schema Registry through the AWS Command Line Interface.