Skip to content
nathankopp edited this page Dec 15, 2010 · 2 revisions
  • Super-simple to use
    • “Obvious” for Java developers
    • Minimally-invasive (for your entities as well as your services)
    • Support storage of any Java class
    • Automatically handle relationships in a “Java” way
    • Smoothly integrated with common application frameworks
    • Follow the DAO pattern
  • Horizontally scalable and high-performance
    • Compatible with NoSQL storage systems
    • Elegant handling of data structure changes
    • On-the-fly data migration
  • Enterprise features built-in
    • Data versioning
    • Transaction-capable
  • Give the developer choice
    • Choose if you value performance or ACID or something in between
    • Choose from various pluggable storage and indexing components
    • Mix and match components within a single system

Clone this wiki locally