Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Google appenginemigrationcasestudy

2,125 views

Published on

Published in: Technology
  • Be the first to comment

Google appenginemigrationcasestudy

  1. 1. Migrating an Enterprise Application toGoogle App Engine – Journey NotesNarinder Kumar & Vikas Hazrati11/11/2010
  2. 2. Agenda Starting Context and Goals Evaluation Criterias Migration Journey  Problems and Solutions Current State Conclusions 2
  3. 3. How we started Standalone Web Application for Employee TimeSheet and Invoicing Management Has been in Production since 2007 > 6,00,000 downloads Hugely successful in SMEs 3
  4. 4. Pain Points Enterprises not keen in maintaining the Product in-house Rolling Out New Features / Patches was long, time-consuming and Error prone Had to maintain multiple development versions for supporting specific requirements Limited Reach 4
  5. 5. Possible Solutions Cloud Approach Java Web Start We decided to take SaaS route 5
  6. 6. Cloud Alternatives 6
  7. 7. Evaluation Criteria - 1 Technology Prespective  Support of different Frameworks  Ease of Development & Deployment  User Community
  8. 8. Evaluation Criteria - 2 Business Perspective  Cost  Maintenance Overhead  Time To Market  Vendor Lock-In  Data Security & SLAs
  9. 9. Evaluation Criteria - 3 Future Trends  Feature Offering Pipeline  Collaboration and combined offering with potential partners
  10. 10. Preferred Solution 10
  11. 11. Why GAE ? 11
  12. 12. GAE – Technology Perspective Does not impose new Language / Framework PaaS  Everything is ready for use Lot of widely used frameworks are supported Several useful Services available off the shelf Eclipse Plugin, Good Local Simulation & Testing Support Restrictions Imposed by Platform 12
  13. 13. GAE – Business Perspective PAYG Model, No initial set up cost No set-up and subsequent Maintenance effort Shortest Time-To-Market cycle Clearly defined Data Redemption paths and improving further Recent Introduction of SLAs, should improve further Replication & Failure 13
  14. 14. GAE – Future Trends Prespective Heavy and continued Investment from Google to make GAE an attractive platform for Enterprise scale applications Recent Tie-Up with VMWare to jointly offer solutions Introduction to SLAs Addition of New Services in the portfolio 14
  15. 15. 15
  16. 16. JPA is not the same JPA 17
  17. 17. JPA specific examples entity groups transaction restrictions no m:n query restrictions relationshipEach entity has a path of parent-child relationships from a rootentity to itself 18
  18. 18. Framework Support 19
  19. 19. Framework Support 20
  20. 20. Multi-Tenancy 21
  21. 21. Multi-Tenancy 22
  22. 22. Memcache 23
  23. 23. Memcache 24
  24. 24. Memcache 25
  25. 25. Memcache 26
  26. 26. Lock-In 27
  27. 27. Avoiding Lock-In 28
  28. 28. Cold Start Problem 29
  29. 29. Cold Start Problem 30
  30. 30. Cold Start Problem 31
  31. 31. Where are we today ? Application Successfuly migrated to GAE  Currently running in Public Beta Beta Users are happy and given good feedback Client is happy taking the first step towards SaaS application 32
  32. 32. Conclusions Development effort during migration was not huge Significant Cost Savings  For End Users  For Product Development Company Reduced Time-To-Market Reduced Maintenance Wider Audience 33
  33. 33. SaaS is here to stay and grow 34
  34. 34. www.inphina.comhttp://thoughts.inphina.com

×