Click here to close now.


Release Management Authors: Jnan Dash, Liz McMillan, Lori MacVittie, Gilad Parann-Nissany, Carmen Gonzalez

Related Topics: Java IoT

Java IoT: Article

Making the Impossible Easy: Failover for Any Application

Using JDBC Database Connectivity Drivers to Support Your Application Failover Strategy

JDBC at Cloud Expo

If your systems require constant accessibility, you know that application failover is an essential function for automatically and transparently redirecting requests to an alternate server in the case of a failure or downtime. Several options exist for ensuring high availability for your mission-critical applications. Those options may be hardware- or software-based, and may also vary considerably in terms of project or enterprise scope and in terms of cost and complexity. Chances are you're relying on one or more such options. But are you aware that the database driver software you use can make application failover much easier and cost-effective to implement, configure, and manage application failover?

High availability solutions are typically complicated and expensive to code. With an application relying on an Oracle data source platform, for example, the Transparent Application Failover (TAF) is what Oracle offers as a high availability strategy. This is certainly a robust solution; however, it must operate in conjunction with Oracle's Real Application Cluster (RAC) high availability environment. An existing application using a non-RAC replication solution cannot use TAF. Implementing Oracle's RAC environment is expensive, and to get an application to support TAF you'll be faced with writing a great deal of complicated, Oracle-specific code.

As an alternative option, you could implement, configure, and manage your application failover entirely through the JDBC software driver used to access the Oracle database. Drivers exist on the market that provide sophisticated failover capabilities such as replaying Select queries in progress and re-creating lost connections and sessions. This approach obviously offers advantages over a proprietary failover approach requiring database-specific application code and offering limited database-related flexibility going forward. But is a driver-based solution really up to the job?

Putting It to the Test
To demonstrate how you might implement a JDBC driver-based application failover, I prepared a use case example of the technology using a small Java application and a high-performance commercially available JDBC driver connecting to an Oracle database. In this demo, a company is writing a web application to browse through a number of golf courses. The country clubs that the company is working for expect a seamless experience for their users (i.e., the application is low tolerance). The data is replicated on two different servers and users get to browse through the course catalog (a page per course), and each page displays course information from the database. The developer wants to ensure that the application doesn't experience any errors or hiccups while a user is browsing the catalog. They want to ensure that, should the database connection to the primary server fail while fetching Course 5, users get Course 6 - rather than an error - when they hit the next button.

Having set up my primary database and replicating the data on my alternate database, I was ready to test failover. Since physically pulling the cable on or actually crashing the server running the primary database would have provoked undesirable responses from my co-workers, I employed a freely available packet analyzer (sniffer) utility called Snoop. It's designed to gather data about the wire-level traffic between the driver and server; however, it can also be used to simulate a database failure. Simply starting a Snoop program sitting between the application and primary sever and then killing the window running Snoop effectively terminates the connection by destroying the active socket. I set the snoop utility to listen to port 1521 on my local machine, connecting to my primary server (see Figure 1).

Next I set my connection URL such that the primary connection would go through the Snoop listener on my local machine, so that closing the Snoop window effectively simulates a connection failure. Listing 1 shows what my URL looked like. (Listings 1 - 4 can be downloaded here.)

Note that the primary server is to my local machine (nc-jdavis), which goes through Snoop to nc-lnx08 (in the Snoop window). In the URL, I added my failover options to indicate that nc-linux02 is the alternate server and I want the option for failoverMode. Setting failoverMode=select indicates to the driver that I want to failover seamlessly while going through the data - in other words, I'm telling it: "Make it look like I never got disconnected." In addition, I set a small performance option, failoverPreConnect, that causes the driver to connect to both the primary and alternate server during the first connect. This saves my application from incurring the cost of connecting during the failover process. It isn't much, but at runtime every bit counts. Let's take a look at the code that displays the results:

while ({
for (int i=1; i <= numCols ; i++) {
System.out.print("'" + results.getString(i) + "'\t");

You'll notice immediately that this looks like a standard loop iterating through the results and printing them to the screen. How do I know that I've failed over successfully? Easy - I check the warnings object, which will indicate when the failover occurs (see Listing 2).

Why not show something that indicates the failover? Because I don't want to have to change my code to add failover on the client side; I want it to work with my middleware out of the box (that is, with no changes necessary to client code). In addition, if the application were being developed using a packaged application framework (think Hibernate or Cognos), then you cannot change application code, which makes using this failover mechanism easy to incorporate in any application architecture.

Now I run the application. Notice that the output is formatted for easy reading. In Listing 3 you can see the successful connection information for the server as well as the rows of golf course information.

You can see that I've successfully connected to the primary server and fetched all the data. So the application works. But this is not the purpose of the demo: I want to see it fail. I set a breakpoint (or code in a pause such as on the line in my application containing the System.out.println() statement, then debugged the application and, when I hit the breakpoint, continued through it for the first six rows. The Snoop window showed my connection (see Figure 2).

Next, I simply closed the window, effectively terminating my socket connection with the database and hanging it there. Continuing again, I see that row seven has nevertheless printed out. The driver caught the "connection failed" exception, connected to the alternate database (nc-lnx02), replayed the connection parameters, refetched, validated the data, and positioned on the correct row. The only indicator that anything happened is in the warnings object, indicating a successful failover. This can be logged to the application logs, or used as a trigger to send an e-mail to the systems administrator for action. Listing 4 shows the output when the failover happened.

The Right Database Connectivity Middleware Is Key
Putting the logic of failover in an application is tedious and expensive. As the sample provided here demonstrates, letting the middleware handle the failover and repositioning logic can be a better strategy in terms of saving development time and costs and focusing on satisfying the needs of your users. However, this recommendation comes with a caveat: not all database connectivity drivers have this capability or, having it, can deliver it with sufficient robustness to serve as a viable failover strategy.

Database drivers provided by the database vendor, for instance - and often used by systems architects as the default choice - provide limited if any application failover support. In such cases failover typically involves dependencies on proprietary high availability environments such as Oracle RAC, Microsoft Cluster Server (MSCS), or DB2 High Availability Disaster Recovery (HADR). Where failover support is provided, it is only in drivers that are based on client-side libraries. For Java that means Type 2 architecture - which, in turn, means inferior runtime performance and increased deployment and maintenance costs.

If you're considering the simplicity and flexibility of application failover provided by data connectivity middleware, look for high-quality drivers that provide the following important benefits:

  • No reliance on expensive and hard-to-implement server dependencies.
  • Failover managed entirely by the driver, simplifying application code.
  • Flexible and configurable failover options for various enterprise requirements.
  • Standards-based approach, to provide consistency regardless of environment.
  • Client load balancing, which works with failover to help distribute new connections so that no one server is overwhelmed with connection requests.

Making sure that application failover can handle connection failures in a standard way is key to ensuring the stability and uptime required by your customers. The database connectivity driver you implement should be an important part of your failover strategy. Some of them offer simple, cost-effective, yet sophisticated failover support to relational data sources, managed by the database driver versus adding costs in the application programs or implementing costly failover options provided by the database vendors. Obviously this is an offer you can't - or at least shouldn't - refuse to consider.

More Stories By Jesse Davis

Jesse Davis is the Senior Engineering Manager for Progress DataDirect Connect product line, and has more than 12 years experience developing database middleware, including JDBC and ODBC drivers, ADO.NET providers, and data services. Jesse is responsible for DataDirect’s Connect product development initiatives and forward looking research.

Comments (1) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

Most Recent Comments
MoonRainbow 11/19/09 07:39:00 PM EST

Unfortunately your solutions doesn't say anything about the genesis of data. How is the data gets propagated between primary and backup? Any failover solution must take this into account, because if you don't implement it correctly, your databases might not be accessible for quite a while after one crash. Opening simultaneous connections to both databases at start-up is also not a highly scalable approach, because you quickly use network and database resources that way.

@ThingsExpo Stories
Most of the IoT Gateway scenarios involve collecting data from machines/processing and pushing data upstream to cloud for further analytics. The gateway hardware varies from Raspberry Pi to Industrial PCs. The document states the process of allowing deploying polyglot data pipelining software with the clear notion of supporting immutability. In his session at @ThingsExpo, Shashank Jain, a development architect for SAP Labs, discussed the objective, which is to automate the IoT deployment process from development to production scenarios using Docker containers.
Countless business models have spawned from the IaaS industry – resell Web hosting, blogs, public cloud, and on and on. With the overwhelming amount of tools available to us, it's sometimes easy to overlook that many of them are just new skins of resources we've had for a long time. In his general session at 17th Cloud Expo, Harold Hannon, Sr. Software Architect at SoftLayer, an IBM Company, broke down what we have to work with, discussed the benefits and pitfalls and how we can best use them to design hosted applications.
We all know that data growth is exploding and storage budgets are shrinking. Instead of showing you charts on about how much data there is, in his General Session at 17th Cloud Expo, Scott Cleland, Senior Director of Product Marketing at HGST, showed how to capture all of your data in one place. After you have your data under control, you can then analyze it in one place, saving time and resources.
The Internet of Things (IoT) is growing rapidly by extending current technologies, products and networks. By 2020, Cisco estimates there will be 50 billion connected devices. Gartner has forecast revenues of over $300 billion, just to IoT suppliers. Now is the time to figure out how you’ll make money – not just create innovative products. With hundreds of new products and companies jumping into the IoT fray every month, there’s no shortage of innovation. Despite this, McKinsey/VisionMobile data shows "less than 10 percent of IoT developers are making enough to support a reasonably sized team....
Just over a week ago I received a long and loud sustained applause for a presentation I delivered at this year’s Cloud Expo in Santa Clara. I was extremely pleased with the turnout and had some very good conversations with many of the attendees. Over the next few days I had many more meaningful conversations and was not only happy with the results but also learned a few new things. Here is everything I learned in those three days distilled into three short points.
DevOps is about increasing efficiency, but nothing is more inefficient than building the same application twice. However, this is a routine occurrence with enterprise applications that need both a rich desktop web interface and strong mobile support. With recent technological advances from Isomorphic Software and others, rich desktop and tuned mobile experiences can now be created with a single codebase – without compromising functionality, performance or usability. In his session at DevOps Summit, Charles Kendrick, CTO and Chief Architect at Isomorphic Software, demonstrated examples of com...
As organizations realize the scope of the Internet of Things, gaining key insights from Big Data, through the use of advanced analytics, becomes crucial. However, IoT also creates the need for petabyte scale storage of data from millions of devices. A new type of Storage is required which seamlessly integrates robust data analytics with massive scale. These storage systems will act as “smart systems” provide in-place analytics that speed discovery and enable businesses to quickly derive meaningful and actionable insights. In his session at @ThingsExpo, Paul Turner, Chief Marketing Officer at...
In his keynote at @ThingsExpo, Chris Matthieu, Director of IoT Engineering at Citrix and co-founder and CTO of Octoblu, focused on building an IoT platform and company. He provided a behind-the-scenes look at Octoblu’s platform, business, and pivots along the way (including the Citrix acquisition of Octoblu).
In his General Session at 17th Cloud Expo, Bruce Swann, Senior Product Marketing Manager for Adobe Campaign, explored the key ingredients of cross-channel marketing in a digital world. Learn how the Adobe Marketing Cloud can help marketers embrace opportunities for personalized, relevant and real-time customer engagement across offline (direct mail, point of sale, call center) and digital (email, website, SMS, mobile apps, social networks, connected objects).
The Internet of Everything is re-shaping technology trends–moving away from “request/response” architecture to an “always-on” Streaming Web where data is in constant motion and secure, reliable communication is an absolute necessity. As more and more THINGS go online, the challenges that developers will need to address will only increase exponentially. In his session at @ThingsExpo, Todd Greene, Founder & CEO of PubNub, exploreed the current state of IoT connectivity and review key trends and technology requirements that will drive the Internet of Things from hype to reality.
Two weeks ago (November 3-5), I attended the Cloud Expo Silicon Valley as a speaker, where I presented on the security and privacy due diligence requirements for cloud solutions. Cloud security is a topical issue for every CIO, CISO, and technology buyer. Decision-makers are always looking for insights on how to mitigate the security risks of implementing and using cloud solutions. Based on the presentation topics covered at the conference, as well as the general discussions heard between sessions, I wanted to share some of my observations on emerging trends. As cyber security serves as a fou...
With all the incredible momentum behind the Internet of Things (IoT) industry, it is easy to forget that not a single CEO wakes up and wonders if “my IoT is broken.” What they wonder is if they are making the right decisions to do all they can to increase revenue, decrease costs, and improve customer experience – effectively the same challenges they have always had in growing their business. The exciting thing about the IoT industry is now these decisions can be better, faster, and smarter. Now all corporate assets – people, objects, and spaces – can share information about themselves and thei...
The cloud. Like a comic book superhero, there seems to be no problem it can’t fix or cost it can’t slash. Yet making the transition is not always easy and production environments are still largely on premise. Taking some practical and sensible steps to reduce risk can also help provide a basis for a successful cloud transition. A plethora of surveys from the likes of IDG and Gartner show that more than 70 percent of enterprises have deployed at least one or more cloud application or workload. Yet a closer inspection at the data reveals less than half of these cloud projects involve production...
Discussions of cloud computing have evolved in recent years from a focus on specific types of cloud, to a world of hybrid cloud, and to a world dominated by the APIs that make today's multi-cloud environments and hybrid clouds possible. In this Power Panel at 17th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the importance of customers being able to use the specific technologies they need, through environments and ecosystems that expose their APIs to make true change and transformation possible.
Too often with compelling new technologies market participants become overly enamored with that attractiveness of the technology and neglect underlying business drivers. This tendency, what some call the “newest shiny object syndrome” is understandable given that virtually all of us are heavily engaged in technology. But it is also mistaken. Without concrete business cases driving its deployment, IoT, like many other technologies before it, will fade into obscurity.
Microservices are a very exciting architectural approach that many organizations are looking to as a way to accelerate innovation. Microservices promise to allow teams to move away from monolithic "ball of mud" systems, but the reality is that, in the vast majority of organizations, different projects and technologies will continue to be developed at different speeds. How to handle the dependencies between these disparate systems with different iteration cycles? Consider the "canoncial problem" in this scenario: microservice A (releases daily) depends on a couple of additions to backend B (re...
Container technology is shaping the future of DevOps and it’s also changing the way organizations think about application development. With the rise of mobile applications in the enterprise, businesses are abandoning year-long development cycles and embracing technologies that enable rapid development and continuous deployment of apps. In his session at DevOps Summit, Kurt Collins, Developer Evangelist at, examined how Docker has evolved into a highly effective tool for application delivery by allowing increasingly popular Mobile Backend-as-a-Service (mBaaS) platforms to quickly crea...
The Internet of Things is clearly many things: data collection and analytics, wearables, Smart Grids and Smart Cities, the Industrial Internet, and more. Cool platforms like Arduino, Raspberry Pi, Intel's Galileo and Edison, and a diverse world of sensors are making the IoT a great toy box for developers in all these areas. In this Power Panel at @ThingsExpo, moderated by Conference Chair Roger Strukhoff, panelists discussed what things are the most important, which will have the most profound effect on the world, and what should we expect to see over the next couple of years.
Growth hacking is common for startups to make unheard-of progress in building their business. Career Hacks can help Geek Girls and those who support them (yes, that's you too, Dad!) to excel in this typically male-dominated world. Get ready to learn the facts: Is there a bias against women in the tech / developer communities? Why are women 50% of the workforce, but hold only 24% of the STEM or IT positions? Some beginnings of what to do about it! In her Day 2 Keynote at 17th Cloud Expo, Sandy Carter, IBM General Manager Cloud Ecosystem and Developers, and a Social Business Evangelist, wil...
PubNub has announced the release of BLOCKS, a set of customizable microservices that give developers a simple way to add code and deploy features for realtime apps.PubNub BLOCKS executes business logic directly on the data streaming through PubNub’s network without splitting it off to an intermediary server controlled by the customer. This revolutionary approach streamlines app development, reduces endpoint-to-endpoint latency, and allows apps to better leverage the enormous scalability of PubNub’s Data Stream Network.