Sausalito: An Applica/on Server for RESTful Services in the Cloud. Ma;hias Brantner & Donald Kossmann 28msec Inc. h;p://sausalito.28msec.

Transcription

1 Sausalito: An Applica/on Server for RESTful Services in the Cloud Ma;hias Brantner & Donald Kossmann 28msec Inc. h;p://sausalito.28msec.com/

2 Conclusion Integrate DBMS, Applica3on Server, and Web Server take historic opportunity to simplify system s stack why database as a service if you can have pladorm aas? it works and it works well in the cloud hfp://sausalito.28msec.com Some consequences database disappears, no admin/config (to the be;er and worse) consistency handled at the applica/on server [SIGMOD08, CIDR09] need a programming model that works on all /ers e.g. XQuery,.NET/PLINQ, Ruby (without RAILS!), etc. Java+SQL or PHP+SQL will probably not make it

3 Requirements for DM on the Web Cost ($$$) get cheaper every year; leverage new technology pay as you go along; no investment upfront provision for average case and not peak Scalability response /me independent of number of clients No administra/on outsource patches, backups, fault tolerance 100 percent read + write availability no client is ever blocked under no circumstances Consistency: op-miza-on goal; not constraint

4 What is Cloud Compu/ng? Commodi/za/on of Compu/ng CPU, storage, and network (not yet databases and applica/ons!) Goal 1: Reduc/on of Cost principle: fine grained ren/ng of resources pay as you go (cost grow linearly) Goal 2: Simplifica/on of Management poten/ally infinite/imbreakable compu/ng resources poten/ally no administra/on

5 Cost ($$$) Requirements Revisited get cheaper every year; leverage new technology pay as you go along; no investment upfront Scalability response /me independent of number of clients No administra/on outsource patches, backups, fault tolerance 100 percent read + write availability no client is ever blocked under no circumstances Consistency: op-miza-on goal; not constraint

6 Databases and the Cloud Cloud Compu/ng a great star/ng point Unfortunately, only a frac/on of the stack Customization, Training,... Application Application Server DBMS Hardware

7 Databases and the Cloud Cloud Compu/ng a great star/ng point Unfortunately, only a frac/on of the stack Customization, Training,... Application? Application Server DBMS Hardware

8 Two Camps of Thought for DBMS Install standard DBMS in the Cloud take a tradi/onal DBMS (e.g., Oracle, MySQL,...) install it on an EC2 instance use S3 or EBS as a persistent store Rethink the whole system architecture do NOT use a tradi/onal DBMS create new breed of applica/on server (with DB) run applica/on server on n EC2 instances use S3 + distributed consistency protocols

9 Two Camps of Thought: Camp 1 Install standard DBMS in the Cloud take a tradi/onal DBMS (e.g., Oracle, MySQL,...) install it on an EC2 instance use S3 or EBS as a persistent store Advantages tradi/onal databases are available proven to work well; many tools people trained and confident with them

10 Two Camps of Thought: Camp 1 Install standard DBMS in the Cloud take a tradi/onal DBMS (e.g., Oracle, MySQL,...) install it on an EC2 instance use S3 or EBS as a persistent store Disadvantages tradi/onal DBMS solve the wrong problem anyway focus on throughput and consistency SAP and Oracle misuse the DBMS already today tradi/onal DBMS make the wrong assump/ons e.g., DBMS op/mizers fail on virtualized hardware e.g., DBMS bulkloading tools collapse on S3 Das Kind mit dem Bade ausschü;en!

11 Camp 1: Requirements Revisited Cost ($$$) incompa/ble business models: low vs. high margin expensive hardware and admins needed Scalability tradi/onal DBMS do not scale to 1000s machines No administra/on despite progress, s/ll a dream for trad. DBMS 100 percent read + write availability incompa/ble with ACID paradigm Consistency

12 Camp 1: Requirements Revisited Cost ($$$) incompa/ble business models: low vs. high margin expensive hardware and admins needed Scalability tradi/onal DBMS do not scale to 1000s machines No administra/on despite progress, s/ll a dream for trad. DBMS 100 percent read + write availability incompa/ble with ACID paradigm Consistency

13 Two Camps of Thought: Camp 2 Rethink the whole system architecture do NOT use a tradi/onal DBMS create new breed of applica/on server (with DB) run applica/on server on n EC2 instances use S3 + distributed consistency protocols Advantages and Disadvantages requires new breed of (immature) systems + tools solves the right problem and gets it right leverages organiza/on s investments in SOA

14 Camp 2: Requirements Revisited Cost ($$$) get cheaper every year; leverage new technology pay as you go along; no investment upfront Scalability response /me independent of number of clients No administra/on outsource patches, backups, fault tolerance 100 percent read + write availability no client is ever blocked under no circumstances Consistency: op-miza-on goal; not constraint

15 Looking at the Whole Stack [Berkeley2009] Low level APIs to cloud services (e.g., AWS) S3, SimpleDB: key/value store EC2: deployment of virtual machines ( infinite scalability; hard for programmers) High level (abstract) APIs (e.g., Google, 28msec) deploy whole applica/on / service ( infinite scalability; restric/ons for programmers) Intermediate offerings (e.g., Microson Azure) expose some low level APIs + support abstract (limited scalability; great support for programmers)

16 What is Sausalito? Applica/on Server + Web Server + Database integrated applica/on stack for Web based apps fully SOA enabled all pre configured and lean (no admin) Development Tools XQuery++ Eclipse Plug In complete client side test infrastructure debugger Libraries payment, workflow, HTTP, , JSon, GEO,...

17 Sausalito in the Cloud (connected) Browser Adobe Air Adobe Flex Mobile Games... Client Machines REST (http) Internet Servers of utility provider App. Server App. Server App. Server App2 App3 App2 App3 Cloud Storage (e.g. S3) App2 App3

18 Sausalito in the Cloud (no Server) Client Machines Adobe Browser Adobe Air Mobile Games... Flex App2 REST (http) Internet Servers of utility provider App2 App3 Cloud Storage (e.g. S3) App2 App3

19 Sausalito in the Cloud (offline) Client Machines Adobe Browser Adobe Air Mobile Games... Flex App2 REST (http) Internet Servers of utility provider App2 App3 Cloud Storage (e.g. S3) App2 App3

20 Demo

21 Conclusion: Why Sausalito? Improve flexibility of Web based applica/ons leverage Web based standards: XML, JSON, REST,... flexible data model: sequences of objects XQuery++ programming model (W3C standard) Simplify opera/ons leverage cloud compu/ng technology pay as you go cost: no upfront investment infinite scalability (throughput), 100% availability no administra/on (backups, security patches, DB,...) predictable cost and performance (response /me) Huge cost savings: development + deployment

22 <Thanks/> Because green is the new blue... h;p://sausalito.28msec.com/