Relative Content

Tag Archive for client-server

Is this architecture feasible? Maintaining two tcp sockets open from the server to two clients in order to relay events between the two

Basically I need to keep track of two clients and need pass messages between the two. I am thinking of creating a tcp connection between the clients and the server and using the server to manage this connection between the two and relay messages as needed. I need to know if my architecture is realistic in the sense that it needs to be able to scale to hold thousands of these relays.

Is this architecture feasible? Maintaining two tcp sockets open from the server to two clients in order to relay events between the two

Basically I need to keep track of two clients and need pass messages between the two. I am thinking of creating a tcp connection between the clients and the server and using the server to manage this connection between the two and relay messages as needed. I need to know if my architecture is realistic in the sense that it needs to be able to scale to hold thousands of these relays.

Is this architecture feasible? Maintaining two tcp sockets open from the server to two clients in order to relay events between the two

Basically I need to keep track of two clients and need pass messages between the two. I am thinking of creating a tcp connection between the clients and the server and using the server to manage this connection between the two and relay messages as needed. I need to know if my architecture is realistic in the sense that it needs to be able to scale to hold thousands of these relays.

Is this architecture feasible? Maintaining two tcp sockets open from the server to two clients in order to relay events between the two

Basically I need to keep track of two clients and need pass messages between the two. I am thinking of creating a tcp connection between the clients and the server and using the server to manage this connection between the two and relay messages as needed. I need to know if my architecture is realistic in the sense that it needs to be able to scale to hold thousands of these relays.

Is this architecture feasible? Maintaining two tcp sockets open from the server to two clients in order to relay events between the two

Basically I need to keep track of two clients and need pass messages between the two. I am thinking of creating a tcp connection between the clients and the server and using the server to manage this connection between the two and relay messages as needed. I need to know if my architecture is realistic in the sense that it needs to be able to scale to hold thousands of these relays.

have we come full circle with microservices, back to very old school approaches?

In terms of software architecture and design, how do microservices “stack up” (pun intended) against middleware? I’m coming from Java, and it seems like as you move away from straight REST as an API, and abstract away different layers and connection parameters, at least in Java, you’ve almost come full circle back to some very old school ideas. We’ve come back to virtualization…wheras the JVM is already virtual.

have we come full circle with microservices, back to very old school approaches?

In terms of software architecture and design, how do microservices “stack up” (pun intended) against middleware? I’m coming from Java, and it seems like as you move away from straight REST as an API, and abstract away different layers and connection parameters, at least in Java, you’ve almost come full circle back to some very old school ideas. We’ve come back to virtualization…wheras the JVM is already virtual.

have we come full circle with microservices, back to very old school approaches?

In terms of software architecture and design, how do microservices “stack up” (pun intended) against middleware? I’m coming from Java, and it seems like as you move away from straight REST as an API, and abstract away different layers and connection parameters, at least in Java, you’ve almost come full circle back to some very old school ideas. We’ve come back to virtualization…wheras the JVM is already virtual.