|
« Previous • All features • Next » Data Access
Data is king! But choosing from among the sea of data options can be daunting: do you want all the guarantees that a traditional RDBMS provides? Do you need web-scale clustering and horizontal scaling? Do you need data caching? Do you need everything? While the Spring framework can't help you decide on which technology is most appropriate for your application, rest assured that there is no better technology to have at your side than the Spring framework. Spring provides declarative, annotation-driven support for cross-cutting concerns like transactions and caching. Spring also provides convenient template objects that reduce API interactions with most data stores to one-liners. These template objects let you focus on the task at hand and transparently take care of the boilerplate code chores typical of data access technologies like connection acquisition, session creation and concurrency concerns. Spring also provides a unified API that decouples the caching from the choice of persistence technology (compared to other persistence solutions that provide technology-specific support for common caching idioms such as write-through and read-through). Whether you use an object-relational mapping tool like JPA (1 or 2), JDO, or Hibernate; a lightweight straight-SQL framework like iBatis or Spring's JDBC support; or a NoSQL solution like MongoDB, Redis, or Neo4J, Spring's consistent transaction management support and lightweight APIs make short work of building sophisticated, plain-old-Java-object based business services and data access objects.
|
Related Projects
|
|
Data is king! But choosing from among the sea of data options can be daunting: do you want all the guarantees that a traditional RDBMS provides? Do you need web-scale clustering and horizontal scaling? Do you need data caching? Do you need everything? While the Spring framework can't help you decide on which technology is most appropriate for your application, rest assured that there is no better technology to have at your side than the Spring framework. Spring provides declarative, annotation-driven support for cross-cutting concerns like transactions and caching. Spring also provides convenient template objects that reduce API interactions with most data stores to one-liners. These template objects let you focus on the task at hand and transparently take care of the boilerplate code chores typical of data access technologies like connection acquisition, session creation and concurrency concerns. Spring also provides a unified API that decouples the caching from the choice of persistence technology (compared to other persistence solutions that provide technology-specific support for common caching idioms such as write-through and read-through). Whether you use an object-relational mapping tool like JPA (1 or 2), JDO, or Hibernate; a lightweight straight-SQL framework like iBatis or Spring's JDBC support; or a NoSQL solution like MongoDB, Redis, or Neo4J, Spring's consistent transaction management support and lightweight APIs make short work of building sophisticated, plain-old-Java-object based business services and data access objects.
|
