Google appenginemigrationcasestudy

Migrating an Enterprise Application toGoogle App Engine – Journey NotesNarinder Kumar & Vikas Hazrati11/11/2010

Agenda Starting Context and Goals Evaluation Criterias Migration Journey  Problems and Solutions Current State Conclusions 2

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

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

Possible Solutions Cloud Approach Java Web Start We decided to take SaaS route 5

Cloud Alternatives 6

Evaluation Criteria - 1 Technology Prespective  Support of different Frameworks  Ease of Development & Deployment  User Community

Evaluation Criteria - 2 Business Perspective  Cost  Maintenance Overhead  Time To Market  Vendor Lock-In  Data Security & SLAs

Evaluation Criteria - 3 Future Trends  Feature Offering Pipeline  Collaboration and combined offering with potential partners

Preferred Solution 10

Why GAE ? 11

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

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

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

JPA is not the same JPA 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

Framework Support 19

Framework Support 20

Multi-Tenancy 21

Multi-Tenancy 22

Memcache 23

Memcache 24

Memcache 25

Memcache 26

Lock-In 27

Avoiding Lock-In 28

Cold Start Problem 29

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

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

SaaS is here to stay and grow 34

www.inphina.comhttp://thoughts.inphina.com

http://thoughts.inphina.com	302
http://www.inphina.com	154
http://vikashazrati.wordpress.com	21
http://turningcloud.wordpress.com	4
http://knoldus.wordpress.com	2
http://blog.knoldus.com	2
http://localhost:8080	1
http://paper.li	1
http://hghltd.yandex.net	1

Google appenginemigrationcasestudy

by Inphina Technologies on Dec 29, 2010

Accessibility

Categories

Tags

Upload Details

Usage Rights

9 Embeds 488

Statistics

Google appenginemigrationcasestudy — Presentation Transcript