I want to implement a solution of sending transactions over a open socket connection to the back end system. The current architecture of the application uses open socket connection - send transaction - close transaction. This architecture helps achieve a lot of concurrent transactions.
Changing the architecture, where transactions will be sent over an open socket connection (for the server life), what would be the approach that I can take without impacting performance.
Shilpa: This architecture helps achieve a lot of concurrent transactions.
It depends more on the server implementation and not really on you as a client. Anyways that was just an FYI!
Shilpa: Changing the architecture, where transactions will be sent over an open socket connection (for the server life), what would be the approach that I can take without impacting performance.
As far as i understand, you want to pool the socket connection instead of opening and closing per transaction.(better call it request, not to get confused with application level transaction) Is my understanding correct? If yes, then try to google on "connection pool", you will get a lot of results like this that will help you understand the concept. Although most of the articles you will find will be related to JDBC but you can apply the concept for any type of connections.
0
