One of the biggest issues with socket servers is that traditionally they do not scale. The requirement to have a consistent TCP connection makes things very difficult when you want to scale. If one connection sends a message to Server A, how does that message get to a user on Server B?
The solution is to integrate with some centralized pub/sub system that is external to the socket connection system. Unfortunately, this means that if your socket layer is already heavily based on pub/sub, you will end up duplicating efforts.
On Thursday, I traveled to the TechSmith Corporation in the Lansing, Michigan area to deliver a presentation about .NET Core, Microsoft’s newest open source cross-compatibility framework.
At the presentation, I discussed some of the platform’s features and functionality, such as dependency injection, logging, user roles/identities, and use cases.
The idea is that you pass the class/function/attribute through a function and the result becomes the class/function/attribute.
As an example, if you make a @final decorator and have the code…