HomeTracking change and innovation in the enterprise software development community
Company: Terracotta

One of the most prevalent application architectures today is that of a stateless application that maps object data into the database to be stored in relational format, and Hibernate is the most popular way to perform this object-relational mapping. Applications are designed this way for two reasons. First, scalability at the database server is a known and tunable quantity. Second, availability of the database is much closer to “five nines” than that of the application server. Despite these reasons, the burden that shared Java state places on the database and on the application developer is very high. While Hibernate lessens the developer’s workload in having to interface to a database, Terracotta lessens Hibernate’s need to depend on the database for availability and scalability in the first place. The marriage of Terracotta and Hibernate simplifies application development and greatly improves application performance. This lowers total cost of application ownership by an order of magnitude in some cases.
This paper's goal is to provide a view into the integration of Hibernate and Terracotta. More important, the paper will delve into the performance improvements and the “how to” steps associated with the integration of the two technologies. Last, we will examine a real world use case and the ROI (both time and systems costs saved) associated with adding Terracotta to an otherwise stateless database application.
You are viewing a mobilized version of this site...
View original page here