cloudant and the *aas landscape
Post on 25-Dec-2014
181 Views
Preview:
DESCRIPTION
TRANSCRIPT
Cloudant and the *aaS Landscape
Robin Smith, Cloudant Europe Market Development Manager robin.smith@uk.ibm.com @robinsmith82
2
2
2
2
!
• Introductions !
• Anatomy of the Cloudant Data Layer !
• IaaS, PaaS, DBaaS… EaaS !
• Start small, grow big
26
▪ NoSQL based (CouchDB)
▪ JSON (JavaScript Object Notation) document data store
▪ Clustered in a ring
▪ Designed for highly concurrent access
▪ Data written to 3 DB nodes for resiliency
▪ Any node in cluster can service any request - no single point of failure
▪ Request routed internally to return data
▪ Writes go to disk, if quorum not met data safe and cluster “heals” itself
Load balancer
http(s) request GET /my_db/fred
{ “_id”: “fred”, “age”: 20 }
Anatomy of the Cloudant Data Layer
27
▪ Mobile / web applications with large scale requirements
▪ Scale == data size ( GB -> TB)
▪ Scale == concurrency of users (00’s -> Ms)
▪ Systems / Databases of engagement
▪ NOT Systems / Databases of record
▪ Global data distribution
▪ Intermittently connected devices
Anatomy of the Cloudant Data Layer
2
Anatomy of the Cloudant Data Layer
2
IaaS
2
IaaS
API
2
DBaaS
2
!
!
EaaS == Expertise as a Service !
Highly differentiated from other IaaS and even PaaS provider components
!
The future of the Enterprise Cloud?
EaaS
2
Start Small, Grow Big
£0 - <2 GB, <50k light & <10k heavy http requests / month
2
- >1 TB data? -> Global data distribution? - > 90 concurrent connections? -> SLA (Risk / reward share)? -> DBA on demand? -> Custom, application specific, contracts around latency / availability / concurrency?
23
Thank You!
top related