Difference between revisions of "MagnetoDB"
m (→What is MagnetoDB?) |
m (→Overall architecture) |
||
Line 28: | Line 28: | ||
== Overall architecture == | == Overall architecture == | ||
− | It is | + | The shape of the architecture based on Cassandra storage is below. It is the classic 2 layer web application, where each layer is horizontally scalable. |
+ | Requests are routed by load balancer to web application layer, and processed there. | ||
+ | |||
[[File:magnetodb_architecture.png|800px|frameless|center]] | [[File:magnetodb_architecture.png|800px|frameless|center]] | ||
+ | |||
+ | [[File:magnetodb_components_by_layers.png|800px|frameless|center]] | ||
== API == | == API == |
Revision as of 22:58, 29 October 2013
Contents
Status
Scope
Document describes the idea and technical concept of DB service for OpenStack like Amazon DynamoDB. There is no implementation yet.
What is MagnetoDB?
MagnetoDB is Amazon DynamoDB API implementation for OpenStack world.
What is DynamoDB?
DynamoDB is a fast, fully managed NoSQL database service that makes it simple and cost-effective to store and retrieve any amount of data, and serve any level of request traffic. With DynamoDB, you can offload the administrative burden of operating and scaling a highly available distributed database cluster
DynamoDB tables do not have fixed schemas, and each item may have a different number of attributes. Multiple data types add richness to the data model. Local secondary indexes add flexibility to the queries you can perform, without impacting performance. [1]
Why it is needed?
In order to provide hight level database service with DynamoDB API interface for OpenStack users.
Just simply create the table and start working with your data. No vm provisioning, database software setup, configuration, patching, monitoring and other administrative routine.
Integration with Trove?
Initially suggested as blueprint for Trove it was rejected as not following the programm mission.
MagnetoDB is not one more database, which can be provisioned and managed by Trove. It is one more OpenStack service with own API, keystone based authentication, quota management.
However, the underlaying database will be provisioned and managed by Trove, in order to reuse existing Openstack components and avoid duplication of functionality.
Overall architecture
The shape of the architecture based on Cassandra storage is below. It is the classic 2 layer web application, where each layer is horizontally scalable. Requests are routed by load balancer to web application layer, and processed there.
API
The API consists of the following methods
- BatchGetItem
- BatchWriteItem
- CreateTable
- DeleteItem
- DeleteTable
- DescribeTable
- GetItem
- ListTables
- PutItem
- Query
- Scan
- UpdateItem
- UpdateTable
Implementation
Pluggability
The most suitable data source is Cassandra. But it is better to make datasource plugguble and give the framework for implementation of interface for any other underlying storage.
OpenStack component reusage
Purpose | OS component |
---|---|
Provisioning of web tire | Heat, Mistral (Convection) |
Load balancer | LBaaS, Neutron |
Autoscaling of web tier | Heat autoscaling, Ceilometer |
Data Source provisioning and management | Trove |
Monitoring | Ceilometer |
Authentication | Keystone |
Autoscaling
- Web autoscaling is suggested to implement with HEAT autoscaling group resource
- Datasource scalability based on future Trove autoscaling