Hey, thanks for the response.
The link I sent Golang specifically had an asterisk which had the Note I sent in the previous email saying that it doesn’t support real-time event listeners. So I assumed that the rest of the languages do.
Yes, it's a server environment where the goal is to have a WebSocket sort of thing where I can listen to the orders placed from the client-side and then process the orders server-side and then broadcast the order update to all clients as the order-book and the last traded price (current market price) should be broadcasted to all clients in real-time.
I didn't understand as to why I will have to reinvent these (connectivity, local caching, offline operations, authentication, et al)? Can you explain? Are you saying that with Admin SDK all these features come right out of the box but if I use REST API then will have to implement all these manually?
Are you aware of the reason why Go Admin SDK doesn't have real-time listener support or when can we expect that?
Also if you are aware of any third-party library that implements those features, that would be a great help.
I am still inclined to use golang for its performance but I am a startup and working alone and don't have a team to reinvent the wheel as you said and kind of using firebase for faster development.
Can you guide me as to what can be the possible solution?
Should I just use Python? (That is actually convenient as I will not have to learn a new language.)
The link I sent in the last mail says "Instead, in Go, updates should be proactively fetched by explicitly invoking read operations."
How does this work? Periodically (say every sec) perform read operations to kind of emulate real-time feature?
But what if there are no updates say for an hour. Then all those read operations go to waste?
Thank you.
Regards.