(this might be off-scope - but nothing ventured, nothing gained) We've been exploring using Swagger/OAS as the lingua franca for documenting services and APIs. At the same time, we're increasingly moving towards serverless architectures where the entry points to our functions and services aren't always REST APIs, but could be messages on Kinesis/PubSub (the most common edge case). I'd love to fit those into our API specs - as we do consider both "I consume this message" or "I will emit this message" to be part of the components contract.
Curious how others have solved this... conventions in Swagger? Combined with other definition tools as some kind of aggregate? Jason -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
