Could you please let me know the usage of this async api... can we create flows in anypoint studio after importing async api like raml or it is just for design
@@muletechnologyacademy-zero5625 Hello I've watched 4 videos available so far in this playlist - and I can not find an answer to @nagappan karthick question... How can we "utilize" the AsyncAPI specification in Mulesoft itself? Or maybe it's just a "documentation asset" we write once in Design Center and than exchange with other parties? I mean: event-messaging platforms for further implementation?
Hi, Currently we can design AsyncAPI in design center and it can be shared via Anypoint Exchange or Developer Portal for discovery. Currently it doesn’t have capabilities where we can generate code automatically like APIKit router.
Can we create this for scheduler based integrations also?
It is mostly for event driven architecture.
Could you please let me know the usage of this async api... can we create flows in anypoint studio after importing async api like raml or it is just for design
Please check complete playlists. You will get answer
@@muletechnologyacademy-zero5625 Hello I've watched 4 videos available so far in this playlist - and I can not find an answer to @nagappan karthick question... How can we "utilize" the AsyncAPI specification in Mulesoft itself? Or maybe it's just a "documentation asset" we write once in Design Center and than exchange with other parties? I mean: event-messaging platforms for further implementation?
Hi, Currently we can design AsyncAPI in design center and it can be shared via Anypoint Exchange or Developer Portal for discovery. Currently it doesn’t have capabilities where we can generate code automatically like APIKit router.
@@muletechnologyacademy-zero5625 Thank you for the prompt answer. All is clear now.