1 / 22

Scalable Transactions in the Cloud

CloudSave. CloudTran. Scalable Transactions in the Cloud. Matthew Fowler, NT/e. ?. And the answer is platform for mainstream Java developers to use IMDG for scalable, commercial applications without worry and minimal hassle for commercial advantage It's a lump of middleware

miron
Télécharger la présentation

Scalable Transactions in the Cloud

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CloudSave CloudTran Scalable Transactions in the Cloud Matthew Fowler, NT/e 1

  2. ? • And the answer is • platform for mainstream Java developers • to use IMDG • for scalable, commercial applications • without worry and minimal hassle • for commercial advantage • It's a lump of middleware • built on, adding value to GigaSpaces 2

  3. 2001 • WebLogic/J2EE specialisation • One week training course • 4-point architecture for dummies • Messed-up architecture • revenue down • Automating server-side applications • J2EE/EJB • Spring/Hibernate 3

  4. 3-5...5-10...10-20...1,000,000 • Tracy's story: the path of successful apps • Database • Caching • In-memory Data Grid • The 50,000 club • Application scale drivers • Mobile phone growth, iPhone Apps • Micropayments • e-commerce continued growth 4

  5. Get an edge with performance “Latency really matters ... 100ms of latency costs 1% in sales.” Amazon “An extra 0.5 seconds in search page generation time dropped traffic by 20%.” Google Please wait ..................... “... almost half of visitors will abandon a site if they perceive a page or feature takes longer than 2 seconds to load. ” GetElastic 5

  6. 6.5m, x10yrs, $400bn/yr • Mainstream Java developers • 6.5m • most have 5-10 years experience • 50 million man-years experience • Plain old application development market • $400bn/year • Can they build an IMDG application? • How can IMDG go mainstream? 6

  7. Explaining it to your Mom / Boss IMDG - SOR Persistent Storage 7

  8. Explaining it to a techie • System of Record in IMDG. Keep DB for • warehouse apps/BI • sleeping at night. • Catching the money: • ACID transactions • throughput, scalability, bullet-proof reliability • distributed, data + messaging • ORM - Object references, not foreign keys.Easy to program. Entity groups for performance. 8

  9. In-Memory Data Bases - Are You Crazy? • What's it worth: • Loss of sales, traffic - 5% vulnerable, saved by speed of IMDG • For $100m/year co: • $5m/year revenue for good behaviour • Customer/order/product data - 2million * 16Kb • 8 servers in grid for 32GB live data • 8 servers isn't a lot • Worth doing the numbers! 9

  10. Distributed Transactions Fear and loathing ... Low Reliability Complicated Programming of Unknowing Unintended Consequences 10

  11. , 1, 2, 3, ...  • Other alternatives • forget transactions, forget databases • Dan's the Man • GoogleApps on V2 last we heard 11

  12. Distributed Cloud Transactions • Grid connected • Helland's get out clause • System of Record is in the grid • No voting - 1PC not 2PC • Commit to backed-up memory • Leverage the GigaSpaces platform • SBA/Entity Groups, Transactions, SQL Queries, Backups Redefining the problem How is it possible? 12

  13. 200/ ... 2,000 ... 20,000/second 13

  14. Transactions you can count on 14

  15. Transactions you can count on 15

  16. Herding Cats - Java Style • How to distribute data • How to find it • How to resolve references • IMDG versus user view: FK ↔ OO • Atomicity on failure • Timeouts • Scalability • Consistency and isolation 16

  17. The 'T' Word • GigaSpaces Local Transactions • GigaSpaces Distributed Transactions • Mirror service • see Cat-Herding 101 17

  18. How CloudTran ORM works Partitioning (entity groups) Client Gridsearch OL Service Order Commit Data Data TxB Commit Commit Confirm Confirm Tx Messaging 18 Datasources

  19. 300 .. 700 .. 900 .. 2,100 • Performance of transaction buffer • Tiny Transactions per second 19

  20. In-Cloud Federated Applications Virgin Airways LastMinute.com IMDG IMDG CloudTran -FederatedTransaction Buffer 20

  21. Scalable transactions in the cloud? • platform for mainstream Java developers • to use IMDG • for scalable, commercial applications • without worry and minimal hassle • for commercial advantage • GigaSpaces CloudTran 21

  22. End 22

More Related