Child pages
  • Data Persistence
Skip to end of metadata
Go to start of metadata

Apstrata providers a NoSQL database service with a "document" (or "object") basic entity paradigm. Our database service provides more natural abstractions for storing business objects than the classical relational model.

If one were to store this business object in a Relational database one would need to create multiple tables, using 3rd normal form schema and add the triggers and stored procedures to implement the business process and security rules. As shown below, this is a non-trivial exercise:

In contrast, the Apstrata database uses a document metaphor to store the business object. All of the fields, rules and security are defined and stored together, as shown below:

The Apstrata database supports the complexity and richness of the business object natively and greatly simplifies the development, maintenance and enhancement of business application data. 

Apstrata doesn't create an artificial limit between meta-data and digital assets, furthermore the store provides an automatice versionning of document changes. Our full text search service automatically indexes meta-data and digital asset contents (MS-Office or PDF files).


Apstrata Database Features

  • Document based storage model
  • Ability to create arbitrary number of Stores (document collections) per account
  • Rich Media support: Binary file types are stored into the database documents with the meta-data (such as images, videos and Office or PDF documents)
  • Typed data fields: String, Numeric, Date, Text
  • Transaction Support: ACID transactions, multiple simultaneous operations succeed or fail together
  • Rich Query ability: Flexible Filter Statements, Result Set Sorting, Basic Aggregates and Count
  • Full Text Search over all document meta-data fields and rich media object types such as Office and PDF documents
  • ACLs: field level security on read, write, delete operations by user or group of users
  • Schema definition, applying ACLs based on a schema, assigning documents to schemas, validating data based on schema
  • Saved Queries
  • Version control

For specific details on how to persist data, please check the SaveDocument API.

  • No labels