What are the design patterns on WebSocket?

Question

Design patterns

There is Ratched, there is phpDaemon, there are a bunch of other servers and not only in php. Their sites are full of tutorials on how to make some kind of chat and maybe something else not very complicated. There are no problems with how to respond to requests (mvc is still working). It starts interesting when the server itself has to send some message, and here no mvc can save.
And I can't find anything about how to correctly build a large application. Google searches have also been fruitless.
I do not quite understand, to be honest, even what to google.
Is there something similar to MVC but for asynchronous communication? Some design patterns/designs/tips.
There are suspicions that you need to dig towards server-side Java applications.
Drag the links to the studio, we will watch and read everything.