Publish/Consume messages to topic-endpoints using Golang

Hi there,

I don't think you should use topic-endpoint. Topic Endpoint feature is provided for JMS standard compatibility when you're migrating from another vendor to Solace.
(and at the end of a migration, you'd move to queue subscription)

You'd prefer using either "topic subscription" or "queue binding".

• Topic Subscription : use that if you're doing Direct Messaging, ie : no persistence on disk, no acknowledgement at publish or subscribe. It has the highest performances. it's used in the finance industrie to publish stock prices
  • Publish : https://github.com/SolaceSamples/solace-samples-go/blob/main/patterns/direct_publisher.go
  • Subscribe :
    https://github.com/SolaceSamples/solace-samples-go/blob/main/patterns/direct_subscriber.go
• Queue Subscription : Use that if you're doing guaranteed Messaging.
  Both publisher and subscriber messages are acknowledged and messages are store on disk.
  You're likely to want to use this I think.
  • In the queue configuration, you set the subscriptions to topics, to choose which messages are stored on the queue (it can be changed dynamically via REST API, see SEMP)
  • Publish to a topic https://github.com/SolaceSamples/solace-samples-go/blob/main/patterns/guaranteed_publisher.go
  • Subscribe to a queue
    https://github.com/SolaceSamples/solace-samples-go/blob/main/patterns/guaranteed_subscriber.go
• If you need scalability of your microservices and ensure messages are consumed in the order they are produced check @Aaron video on Partitioned Queue :

Check our Developer resources here. :

In particular, have a look to API Tutorial & Codelabs ;)