🎄 Happy Holidays! 🥳

Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.

Happy Holidays!

Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.

Open API or Solace Native API? How to choose and how to get started

TomF
TomF Member, Employee Posts: 412 Solace Employee
edited July 2020 in Blogs & Tutorials #1

One of the first things you need to do when defining your event driven architecture is which API(s) to use in your client applications. Fortunately, Solace had loads! But there's a further choice: open APIs like JMS or MQTT or the Solace native APIs?
Open APIs give you freedom, flexibility and interoperability, at the expense of a restricted feature set, as I discuss in this blog post. In the accompanying codelab I get you started using the native APIs to get you going.

https://solace.com/blog/solace-messaging-apis-event-mesh-features-performance/

Comments

  • marc
    marc Member, Administrator, Moderator, Employee Posts: 963 admin

    Awesome, thanks for sharing @TomF! It's definitely a pleasant surprise to see this blog :)