🎄 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.

Development Best Practices

swami
swami Member Posts: 3 ✭
in General Discussions #1

What are the best practices in solace development except naming queues/topics?
And what are the restrictions, recommendations to be followed?
How failover takes place.
could you please some information related to this?

Tagged:

Comments

  • TomF
    TomF Member, Employee Posts: 412 Solace Employee
    #2

    Hi @swami, the most important best practice is the Topic Taxonomy. This has a huge effect on decoupling, whether publishers have to double publish, security... the list goes on. Have a look at our Topic Taxonomy Best Practices.
    Some other recommendations:

    • Keep your session open - don't open a session, send a message, and close the session
    • Don't use AUTO_ACNOWLEDGE. Call acknowledge explicitly. And only do that once you've completely finished with the message.

    Failover is automatically handled by the broker. All the client sees is a TCP disconnection. There are reconnection timers that need to be adjusted to allow the brokers time to establish a new TCP session, but that's all a developer needs to worry about. The message flow will automatically pick up where it left off.

Categories

This Month's Leaders

This Week's Leaders