Leveraging NoSQL in the Cloud


Published on

Companies are increasingly taking advantage of using a virtualized or cloud infrastructures for their applications, especially those that require real-time data synchronization between mobile devices and the cloud.

In this webinar you will learn about:

- Cloud provisioning and definitions of terms related to data in the cloud
- The unique data management challenges for cloud-based applications
- How to create a highly available, cloud-friendly data layer that scales “out” (not up)
- How to expand (or shrink) the data layer, and rebalance dynamically as application needs change
- Solutions that simplify the management of applications in the cloud

To view Couchbase webinars on-demand visit http://www.couchbase.com/webinars

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Leveraging NoSQL in the Cloud

  1. 1. Leveraging  NoSQL  in  the  Cloud     Uri  Budnik  (RightScale)   Frank  Weigel  (Couchbase)     1  
  2. 2. 2 #RightScale Pioneered Cloud Management •  World’s cloud management platform •  A shop for managing the entire stack •  Managing cloud deployments globally for •  •  More than launched •  Powering the production cloud deployments •  fully supported cloud providers and counting
  3. 3. 3 #What’s Driving Cloud?•  Four horsemen •  Cut costs •  Improve agility •  Increase scale & reliability •  Leverage best practices•  Highly effective layers of abstraction •  SaaS – cloaked below the browser •  PaaS – cloaked below the code •  IaaS – cloaked below the OS•  Each layer achieves scalability & reliability through uniformity•  True IaaS clouds are API-driven
  4. 4. 4 #So what’s the problem?•  Paying attention to design•  Using cloud != designing for cloud•  Accidental tourist in cloud •  Sign up, launch servers, sit back•  Good cloud design •  Secure •  Reliable •  No lock-in •  Fault-tolerance •  Scalability
  5. 5. 5 #The DIY Trap•  Most clouds are a set of APIs and/or a simple UI to launch servers – is that what you need?•  These are basic building blocks, not a management system•  How should you spend your time? •  Managing multiple users with different levels of access •  Configuration management and app lifecycle management •  Track usage and costs across applications and business units •  All the general purpose things you need to do like: Monitoring, Alarms, Auto-scaling, etc What do you do about IT or development personnel unilaterally opening a cloud account and deploying an environment?
  6. 6. 6 #Why you should care about multi-cloud•  Multi-cloud scenarios •  Within / between public clouds •  Public / private hybrid•  Lock-in dangers •  Data has mass •  Vendor contracts, features & APIs•  High availability and disaster recovery•  What you should do •  Preserve multiple choices for any service •  Keep contracts to length you can predict •  Avoid unique services & APIs •  Anticipate moving – set up small footprints elsewhere •  Pilot a private cloud •  Design for portability: architecture choices matter
  7. 7. 7 # One Cloud – Many Resource Pools London Amsterdam Chicago Beijing Seattle Dublin Oregon Seoul NYC AreaSF Area Tokyo DC Area Fukuoka Dallas Hong Kong Hyderabad Singapore São Paulo Private Clouds Public & Managed Clouds Amazon Web Services Logicworks Datapipe Rackspace IDCF / Yahoo! Japan SoftLayer Korea Telecom Tata KINX UnGeo
  8. 8. 8#
  10. 10. Cloud  Environment  ProperCes   •  ParCal  network  outages   •  Complete  node  failures  happen   •  Limited  node  resources  compared  to  dedicated   datacenter     –  IO  limited   –  CPU  and  RAM   •  Node  resources  must  be  used  both  efficiently  and   flexibly   •  SoluCons  must  be  architected  to  fit  the  Cloud   10  
  11. 11. Typical  Cloud  Architecture  Stack   11  
  12. 12. Scaling  the  ApplicaCon  Layer  is  Easy  •  ApplicaCon  Servers  hold  relevant  state  in  Data  Layer  •  Scale  by  adding  more  applicaCon  servers  •  Load  balancing  Cer  selects  applicaCon  server     12  
  13. 13. Scaling  the  ApplicaCon  Layer  is  Efficient   13  
  14. 14. RDBMS  designed  for  different  use-­‐cases   14  
  15. 15. Data  Layer  Scaling  hard  with  RDBMS  •  Limited  scale  up  in  the  cloud  •  RDBMS  do  not  scale  out  •  Cost  explosion  &  Latency   explosion   15  
  16. 16. NoSQL  Databases  •  New generation of databases, designed to address needs of modern web & cloud focused solutions•  No fixed schema –  No more costly schema updates•  Automatic key sharding•  Low latency optimized•  No multi-operation transaction support 16  
  17. 17. Couchbase  Server  Data  Layer  scales  like  ApplicaCon  Layer  Data  layer  now  scales  with  linear  cost  and  constant  performance.  •  Scale by adding more database servers•  Sharding to correct server based on key 17  
  18. 18. Scaling  with  Couchbase  is  easy!  •  Horizontal scalability of Data Tier•  Linear cost•  Flat response times 18  
  19. 19. Summary  •  Done  right,  moving  to  the  cloud  offers  significant   advantages   –  Cost  reducCon,  beaer  agility,  increased  scalability  &  reliability  •  Managing  and  monitoring  deployments  in  the  cloud   greatly  benefit  from  using  a  cloud  management   plaborm  on  top  of  the  IaaS  APIs.  •  Make  sure  your  data  storage  layer  is  designed  for  the   cloud   –  Horizontally  scalable,  fault-­‐tolerant  &  high  performance   19  
  20. 20. Q&A     @FRANKWEIGEL                                        @URIBUDNIK  FRANK@COUCHBASE.COM          URI@RIGHTSCALE.COM         Explore  a  ready-­‐to-­‐launch  example  applicaCon  stack   hap://www.couchbase.com/fast-­‐track-­‐your-­‐app   20