| |
JavaOne, San Francisco, CA – May 6, 2008
Corporate IT organizations doing development on the .NET platform can now take advantage of the Java Persistence Architecture (JPA) API, the popular Java industry programming standard for persisting data. The newly ported solution offers corporate application developers one consistent set of persistence programming commands for building and deploying applications on both the Java and .NET platforms. This is an interesting technology innovation that offers a solution for meeting the requirements of managing enterprise data not currently available for the .Net platform. It could offer enterprise IT organizations the ability to increase code standardization, expand code reuse and decrease development costs.
The first release of the JPA standard for .NET is an excellent baseline set of data persistence commands and facilities. This should be a welcome addition to the .NET development platform, which has not yet created a formal ORM (Object to Relational) API for persisting enterprise data models. The existing .NET ADO approaches provide developers a method for dealing with only the most simple of requirements. Providing .NET developers access to JPA services would offer them the ability to manage more complex data persistence requirements. As a development platform, .NET under the guidance of Microsoft is widely used by large enterprise IT organizations worldwide. These corporations typically have data management requirements that can be quite complex, therefore, it appears that a solution such as JPA is much needed and would be quite beneficial to these organizations.
The first certified JPA provider to innovate a full port to .NET is Thought Inc.'s CocoBase Object to Relational Mapping (ORM) platform. The CocoBase ORM solution is focused on meeting the complex persistence needs of enterprise application development. It has established itself as the only ORM solution that delivers the full range of enterprise persistence requirements with the depth and flexibility required now available for .NET development as well. CocoBase's JPA performance is noted to be on average 200% to 400% faster than other JPA providers which is critical for managing data in todays' large corporate applications. A unique strength of the technology is its' ability to make available corporate legacy data for modern development. The solution includes in-depth training, comprehensive mentoring as well as on-demand technical support, all of which is expected from a commercial vendor such as Thought Inc.
Thought Inc. has consistently innovated solutions in the Java industry demonstrating their technological leadership. For example, CocoBase was the first 100% Java ORM solution available in early 1997. It is not surprising that they are the vendor to deliver the first port of JPA to .NET. Thought Inc.'s technology success has created a list of impressive fortune 1,000 customers who use CocoBase for their mission-critical applications. Expansion to the .Net platform by a respected vendor such as Thought Inc. is welcome news to IT organizations with enterprise data persistence requirements.
Author: Greg Baker, Director of Sales & Marketing, Thought Inc.
Phone: (415) 836-9199
Email to: greg.baker@thoughtinc.com
LEGAL NOTICES
This document is copyrighted and owned solely by THOUGHT Inc.® 2008. CocoBase® and THOUGHT Inc.® are registered trademarks of THOUGHT Inc.®. PURE POJO™, Dynamic O/R Mapping™, Dynamic Object to Relational Mapping™, Dynamic Universal Querying™ and Dynamic Transparent Persistence™ are pending trademarks of THOUGHT Inc.®. CocoBase® technology is based on US patent #5857197 as well as additional issued and pending patents directed to object navigation, object modeling, querying, caching, etc. All other trademarks are property of their respective company. This publication is provided "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement, to also include any and all technical inaccuracies or typographical errors.
|
|
