How are (architecturally) real-time servers built?

Question

Game development

I have relatively little experience writing backends for all sorts of business applications. There was an idea and desire to write a game. If there are no problems with the client, then the usual way of writing backends does not sound like a word at all. The game requires constant communication between the client and the server and constant updating of data for everyone at the same time. Actually, the question arises, how are real-time backends built architecturally? In particular, preferably in Java or Kotlin. Any help, training materials, courses, articles will do. Thanks in advance.

Answer 1

There are 3 options that allow two-way server-client exchange:
- WebSockets
- Server-Sent Events
- Long Polling
There are libraries that wrap these transports and choose the best one based on their client capabilities. For .Net it's SignalR , for Java and Kotlin I don't know, but you can search by keywords.
And, to a heap, the answer from StackOverflow https://stackoverflow.com/questions/11077857/what-...