How Microcks Can Speed-Up Your AsyncAPI Adoption - Part 1

Laurent Broudoux

ยท3 min read
Post cover image

August 11th 2020 was the official announcement of Microcks 1.0.0 release and our first Microcks General Availability (GA) version to fully manage event-driven API through the support of AsyncAPI specification. This first post explains why we decided to start this project and provides more insights.

For those who don't know Microcks yet: it is the ultimate Open source Kubernetes Native tool for Mocking and Testing all your APIs. With Microcks, you can turn your API contract, collection or SOAP UI projects into live mocks in a few seconds. For further information, please read "Why Microcks ?".

We are following the AsyncAPI specification initiative since day one and I clearly remember how the first announcement back in 2017 resonated within our team ! We shared the same principles: Open source and community driven... and last but not least, 100% aligned with our vision that open specifications standards like OpenAPI is the ultimate way to move forward and perpetuate our mantra: unlock developers potential in an unpredictable and strongly innovative environment!

Since then, we have been in touch with our mutual communities and strategic users to see if we all embrace the idea of adding AsyncAPI testing and mocking support within Microcks. Microcks community was very enthusiastic by the idea and problem this integration can solve. We have helped some users on their AsyncAPI use cases to grab valuable feedback on how to manage Microcks event-driven API integration. We learned a lot from different vertical industries, including tricky IoT & Edge computing or fintech implementations.

Our communities clearly validate that it makes sense to have the same tool managing all their API whatever the type, open contract definition or design tool used. This is why, today Microcks supports open standards for contract definitions and mainstream open collaborative tools:

microcks-supported-standards

It took us a year to make, which explains why Microcks 1.0.0 release is already GA and the first tool on this topic ๐Ÿ˜‰

asyncapi-tool-tweet

This is a major step forward as we are convinced that the transition to cloud-native applications will strongly embrace event-based and reactive architecture. Thus the need to speed-up and govern event-based API like any other services mocking using Microcks will be crucial and a key success factor for any modern and agile software developments.

Microcks 1.0.0 provides a solid platform for simulating event-based API using message broker technologies like Apache Kafka even before the publishing component has been developed. And once developed, it is then capable to validate that all the publisher sent events will be compliant with the defined specification, automatically from a CI/CD pipeline.

To demonstrate our commitment/vision and to improve AsyncAPI specifications on our favorite topic: testing & mocking, we have launched an upstream feature request in order to provide a formal type for message examples.

call-to-action

Please have a look at this proposal #329 and share your opinion. At the moment, it is a part of AsyncAPI 2.1 milestone.

In the next article, we will focus on Microcks + AsyncAPI use cases. Stay tuned.

And if you can't wait for text explanataions, do not hesitate having a look at the AsyncAPI SIG Meeting #34 recording for full illustrations of the capabilities. ๐Ÿ˜‰

Subscribe to our newsletter to receive news about AsyncAPI.

We respect your inbox. No spam, promise โœŒ๏ธ

Made with :love: by the AsyncAPI Initiative.