Build, protect and deploy apps across any platform and mobile device
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate decision processes with a no-code business rules engine
Build mobile apps for iOS, Android and Windows Phone
A complete cloud platform for an app or your entire digital business
Deploy automated machine learning to accurately predict machine failures with technology optimized for Industrial IoT.
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
A few weeks back, I worked feverishly to get an article ready for the November 2005 edition of the Sys-con's Java Developer Journal, or as many people refer to it, the JDJ. Check out your pigeon hole mailbox, or head to JDJ online to read the article.
For this article, I delve into the details of matching your JDBC driver against the many choices in the Object-Relational-Mapping (ORM) mechanisms that are so prevalent in many of today's popular architectures. You can use the figure below as a reference. This is an excellent representation we put together that shows how can assemble an application that uses an ORM mechanism, coupled with a best of class JDBC driver and layer it on top of your relational data source.
While I specifically avoid any wide ranging discussion on the pros and cons of each ORM mechanism, I do opt to peel back some of the layers to look exhaustively at the connectivity layer, something that is all too often under-discussed in many development organizations. The majority of today's ORM mechanisms live on top of relational databases, so it is a reasonable assertion to make that without an effective and informed investment in a connectivity layer from a best of breed JDBC driver, you risk loosing the productivity value-add an ORM mechanism to the disadvantage of your development organization. I am of course interested to hear your opinions and feedback, so comment below and we can continue our conversation there.
View all posts from Jonathan Bruce on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
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 for appropriate markings.