Hi all I am wondering if Netty could be a good candidate to build a middleware... I am new to Netty and asynchronous programming in general, so asking to experts ;)
I have 2 legacy applications, a webapp in java (soap-ws) and a legacy server (old-server) written in assembly which only speaks in TCP/IP. There are ~100 instances of soap-ws instances running and (i think) only one instance of the old-server (mainframe). The schema is as follow: soap-ws (spring) ---->[HTTP] middleware (netty?) ---->[TCP/IP] old-server (assembly) The soap-ws is blocking and also the old-server. Does it make sense to use Netty in the middle (which acts both as a server and a client)? My understanding is that I could use a blocking http client from soap-ws (the request thread will wait a response and I am fine with that) to call the asynchronous middleware. Then the middleware will call the old-server in an asynchronous way, then the response will come from the old-server and will be transmitted to the blocking soap-ws client. Another point, the old-server should probably manage the pressure from the asynchronous middleware (queue?). So could Netty be a could candidate (its scalability looks promising)? Or should I stay with synchronous technologies (Tomcat/Spring) all the way long? Thanks for your lights --nick -- You received this message because you are subscribed to the Google Groups "Netty discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/netty/7c69a1ac-2424-4e45-8756-d5c3c0b66398%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
