Before I asked, I'm read these links:
- https://github.com/apache/pulsar/issues/3302
- Is creating a lot of topics with pulsar is a good scenario?
But I'm not sure about the responses. My use case: We use SSE technology (Server Sent Event) protocol to send event from backend to client browser side to have a reactive behaviour. If the client lost the connection due to network failure, I want the browser code can get all events published since the last message id when the connection is restored. The idea: have one topic by user, and when the browser call the get method, I use the Reader API to browse all msg since this message id. My problem is the scalability of the solution: what happend if I reach 10.000 users, 100.000 ... connected to the website ?
Regards
