Thank you, I will see if this the answer I need and get back to you.
Edit: I’m really out on my deep end here, but research so far indicates Spring Boot is also request-driven - in the sense that the server handles several requests and returns a result asynchronously/synchronously. I want a model where the server broadcasts messages at its own accord, and users sometimes sending messages where a response is not needed. This is more akin of the observer pattern. If I need to forcibly adapt Spring Boot to do this as well, I am better off continuing with Tyrus.
If you could outline a bit more specifically how Spring Boot can do this from the get go, I’m all ears.