This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
I have a small query regarding JDBC connectivity over WAN. I have scenerio where my application is running say 'San Francisco' and Database server is at another place say 'New York'. When i want to connect to database server on WAN using JDBC, what is the minimum network bandwidth/latency required to successfully connect to database server.Does JDBC have any recommended range of latency?
There's no particular JDBC requirement. JDBC as a standard is independent of the underlying network layer, but most JDBC drivers are built on TCP/IP and merely require reasonably long-lived connections. Dealing with connection interruptions can be a significant design problem for "difficult" networking conditions. It's more a matter of whether your program can deliver acceptable performance, as judged by users.
There are two pieces of performance advice for some-one developing such a "long-haul" application: 1. connection pooling - connect time can be very significant even on a "short haul"; in a test I did recently, not using connection pooling when connecting through a VPN tunnel made a very simple test program perform 800% slower. 2. Statement.setFetchSize() (or Connection.setPrefetchSize() if you're using Oracle) - ResultSet row retrieval can be buffered to significantly improve performance and manage memory usage.
I'm assuming your database port is secured somehow, such as via a VPN tunnel. If it's not, if the port is open to the Internet, it will be found by hackers and attacked; if there's any security errors in the database program, the hackers will get in.