Create and deliver personalized experiences across digital properties at scale
Build engaging websites with intuitive web content management
Leverage a complete UI toolbox for web, mobile and desktop development
Build, protect and deploy apps across any platform and mobile device
Build mobile apps for iOS, Android and Windows Phone
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate UI, load and performance testing for web, desktop and mobile
Optimize data integration with high-performance connectivity
Automate decision processes with a no-code business rules engine
Globally scale websites with innovative content management and infrastructure approaches
Content-focused web and mobile solution for empowering marketers
Faster, tailored mobile experiences for any device and data source
UX and app modernization to powerfully navigate today's digital landscape
Fuel agility with ever-ready applications, built in the cloud
In my last post, I highlighted the reasons why you still need to think about your JDBC driver when using Hibernate. Here, we’ll dive further into the area of codeless configuration, specifically high availability.
Continuing with the Hibernate analogy, most people use Hibernate because they want to focus in on database-level coding without getting into the nitty-gritty, driver-level code. But using some advanced functionality with the vendor drivers doesn’t work with Hibernate out of the box, ruining the abstraction that Hibernate and other frameworks are trying to provide. So, we end up with a perception that if you’re using Hibernate, there’s no way to take advantage of high availability without making changes to the underlying code. Right?
Well, only partially right. If you’re using a free driver from one of the major database vendors like Oracle, you won’t be able to take advantage of high availability without getting into the code as they use non-standard error messages to indicate different states of failover which Hibernate can’t handle.
Don’t despair! We’ve solved the problem at Progress|DataDirect by offering drivers that failover in a JDBC standard way, giving you back the power of your ORM so your developers can focus on writing applications faster. Not only can you still take advantage of high availability while using Hibernate, but you can also write applications that translate across databases, so you can change that backend as often as you like with no worries that the functionality will need to change with it.
Choosing between high availability and high functionality is no longer an issue. Progress|DataDirect’s high availability approach is enabled to support SQL Server, DB2, Oracle, Sybase, MySQL, and Informix. By implementing the failover logic at the driver level, we make sure that our customers don’t have to pay for additional functionality in the server when the drivers can take care of it themselves. Furthermore, if your app is already written, you can drop in a Progress|DataDirect driver, turn it on, and certify that key failover functionality still works.
To borrow a phrase from Staples, “That was easy!”
As Senior Director of Research & Development, Jesse is responsible for the daily operations, product development initiatives and forward looking research for Progress DataDirect. Jesse has spent nearly 20 years creating enterprise data products and has served as an expert on several industry standards including JDBC, J2EE, DRDA and OData. Jesse holds a bachelor of science degree in Computer Engineering from North Carolina State university.
Copyright © 2017, Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.