spec VS JSON-Schema Faker

AsyncAPI: Interested in how to define your WebSocket APIs? One of the most advanced realtime specifications is the AsyncAPI specification, which comes with various generators for code and documentation, as well as renderers for the specifications.

Our journey with FastStream started when we needed to integrate our machine learning models into a customer's Apache Kafka environment. To streamline this process, we created FastKafka using AIOKafka, AsyncAPI, and asyncio. It was our first step in making message queue management easier.

Automatic Docs: Stay ahead with automatic AsyncAPI documentation

FastStream supports in-memory testing, AsyncAPI schema generation and more... If you are interested, please support our project by giving a GH start and joining our discord server.

However, in order for the system to work effectively, there must be a common understanding between the components regarding events and their data structures. This is where AsyncAPI comes in; it helps define a contract that describes how the components communicate and behave effectively.

You can also take a look at https://www.asyncapi.com/ (a spec for asynchronous APIs). It's useful for this use case, that is, building a well structured websocket interface with pub/sub.

Sure! Next step I am working on AsyncAPI scheme generation by your application code. It's also includes a project generation from scheme, scheme web view (lika the Swagger for OpanAPI), etc. It will a much difficult than just another broker implementation...

Onboarding - Enable developers to quickly learn how to consume the exposed APIs. For example, offer OpenAPI or AsyncAPI documentation and provide a portal and sandbox.

There’s also json-schema-faker which is pretty cool.

https://github.com/json-schema-faker/json-schema-faker

I built a CSV generator which I then use as a test data source for a dsv library on that principle and another API generator based on schema. Something that might be additionally helpful is json-schema-faker, as you can probably convert you primary record (DB schema) to json-schema then just generate tons of data.

I only know https://github.com/json-schema-faker/json-schema-faker for JS, not Java though.

Hell, i was using this one earlier today; just kills me that people think this is acceptable.

The payload object contains a reference to a JSON Schema object that describes the properties of the event. This allows the consumer to know exactly how to define the event when publishing or how to write code that consumes a subscribed event. There are even tools online that generate examples from JSON Schema (and vice versa).

The class-validator / class-transform looks really nice for formatting/validation but there is also joi. suretype is attractive since theoretically typeconv could generate jsonSchema for json-schema-faker and Open API docs.

I've been using Fake your JSON-Schemas! (json-schema-faker.js.org), but it does not consider if-then-else rules in its generation process.