Your SlideShare is downloading. ×
Bringing Legacy Apps to the Cloud
Bringing Legacy Apps to the Cloud
Bringing Legacy Apps to the Cloud
Bringing Legacy Apps to the Cloud
Bringing Legacy Apps to the Cloud
Bringing Legacy Apps to the Cloud
Bringing Legacy Apps to the Cloud
Bringing Legacy Apps to the Cloud
Bringing Legacy Apps to the Cloud
Bringing Legacy Apps to the Cloud
Bringing Legacy Apps to the Cloud
Bringing Legacy Apps to the Cloud
Bringing Legacy Apps to the Cloud
Bringing Legacy Apps to the Cloud
Bringing Legacy Apps to the Cloud
Bringing Legacy Apps to the Cloud
Bringing Legacy Apps to the Cloud
Bringing Legacy Apps to the Cloud
Bringing Legacy Apps to the Cloud
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Bringing Legacy Apps to the Cloud

248

Published on

Getting your new applications into the cloud is a relatively simple procedure. However, enterprises are faced with a large number of existing applications in their current portfolio that may not be …

Getting your new applications into the cloud is a relatively simple procedure. However, enterprises are faced with a large number of existing applications in their current portfolio that may not be quite ready for the new cloud world. Before migrating legacy apps to the cloud, like moving to a new house, enterprises need to assess their current portfolio of apps and determine what they should consolidate, what they should get rid of and what they should keep.

But deciding what to keep is only half of the equation. Enterprises need to understand how some application properties and the development process need to change in order to have a successful migration. Companies can reduce their costs significantly by optimizing their applications development and maintenance. Moving away from the "old way" to the "new way" not only results in saving money, but will also result in saving significant time.

Ho Ming Li, Cloud Solution Architect and Phil Whelan, Technology Evangelist, discuss some of the changes to the development process or application structure/properties that companies need to implement in order to successfully migrate their apps:
- Connecting to databases - service binding
- Frontend/Backend - REST/MQ
- Statefulness vs. Statelessness
- Consistency across Environments
- Dependency Management
- Logging and Monitoring

http://www.activestate.com/webinars/bringing-legacy-apps-cloud

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
248
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
15
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Legacy Apps... to the Cloud Considerations and Practices Phil WhelanTechnology Evangelist Ho Ming Li Cloud Solution Architect May 2014
  • 2. activestate.com/stackato | @activestate | #stackato | activestate.com/blog | Copyright 2014 Moving To The Cloud Legacy applications are not designed to run in the cloud. Cloud-enabled applications are. How do we define "legacy" and "cloud-enabled"? How do we cloud-enable our legacy applications?
  • 3. activestate.com/stackato | @activestate | #stackato | activestate.com/blog | Copyright 2014 Cloud-Enabled Application Attributes Portable Scalable (horizontally) Modular ... Challenges Different infrastructure Scaling issues Dependency management ...
  • 4. activestate.com/stackato | @activestate | #stackato | activestate.com/blog | Copyright 2014 Twelve-Factor App http://12factor.net/ I. Codebase One codebase tracked in revision control, many deploys II. Dependencies Explicitly declare and isolate dependencies III. Config Store config in the environment IV. Backing Services Treat backing services as attached resources V. Build, release, run Strictly separate build and run stages VI. Processes Execute the app as one or more stateless processes VII. Port binding Export services via port binding VIII. Concurrency Scale out via the process model IX. Disposability Maximize robustness with fast startup and graceful shutdown X. Dev/prod parity Keep development, staging, and production as similar as possible XI. Logs Treat logs as event streams XII. Admin processes Run admin/management tasks as one-off processes
  • 5. activestate.com/stackato | @activestate | #stackato | activestate.com/blog | Copyright 2014 Today... • Statefulness vs. Statelessness • Connecting to databases - service binding • Frontend/Backend - REST/MQ • Consistency across environments • Dependency management • Logging and monitoring
  • 6. activestate.com/stackato | @activestate | #stackato | activestate.com/blog | Copyright 2014 From Legacy To The Cloud Your legacy software falls into one of the following categories: 1.It just works! 2.Needs a few tweaks 3.Runs with limitations 4.Not suitable for the cloud
  • 7. activestate.com/stackato | @activestate | #stackato | activestate.com/blog | Copyright 2014 Potential Outcomes Your legacy application in the cloud might be... 1.Running with major limitations 2.Running with minor limitations 3.Fully cloudified real word?
  • 8. activestate.com/stackato | @activestate | #stackato | activestate.com/blog | Copyright 2014 1) Statefulness Vs. Statelessness Examples... •Sessions •In-memory data structures •Local disk storage Cloud-enabled Use shared data stores Half-way there Use sticky sessions
  • 9. activestate.com/stackato | @activestate | #stackato | activestate.com/blog | Copyright 2014 1) Statefulness Vs. Statelessness http://www.github.com/homingli/node-session legacy - session halfway - sticky session cloud - session store http://www.ideachampions.com/weblogs/Public-Speaking.jpg Sessions DEMO
  • 10. activestate.com/stackato | @activestate | #stackato | activestate.com/blog | Copyright 2014 2) Data Service Binding Legacy applications involve manual invention to configure service bindings. PaaS can auto-provision service instances and inject service location and credentials into the application Cloud-enabled Grabs service credentials from environment on start-up Half-way there Using legacy data services and hard-coded credentials will work
  • 11. activestate.com/stackato | @activestate | #stackato | activestate.com/blog | Copyright 2014 3) Frontend/Backend - REST/MQ By breaking up a monolithic application to its components, components can scale on demand individually. Communications: REST common interface, MQ for app internals. Cloud-enabled Components are broken up, communicating via REST/MQ Half-way there Running in cloud environment Existing communications path
  • 12. activestate.com/stackato | @activestate | #stackato | activestate.com/blog | Copyright 2014 3) Frontend/Backend - REST/MQ http://www.github.com/homingli/node-febe REST calls Service bindings http://www.ideachampions.com/weblogs/Public-Speaking.jpg DEMO
  • 13. activestate.com/stackato | @activestate | #stackato | activestate.com/blog | Copyright 2014 4) Consistency Across Environments How close can you get your development environment to production? Stackato provides a consistent environment wherever you run it - development QA, or production Cloud-enabled Use PaaS as part of the development workflow Half-way there Use continuous integration to ensure production compatibility
  • 14. activestate.com/stackato | @activestate | #stackato | activestate.com/blog | Copyright 2014 5) Dependency Management Having Ops independently configure the environment for applications is error prone and does not scale. PaaS applications couple dependencies and application code together. Cloud-enabled Use buildpacks. Use stackato.yml to define system dependencies Half-way there Add Ops scripts to application
  • 15. activestate.com/stackato | @activestate | #stackato | activestate.com/blog | Copyright 2014 6) Logging And Monitoring Managing logs across horizontally scaled applications being difficult PaaS enables streaming all logs to a central repository Cloud-enabled Application logs only written to STDERR/STDOUT Half-way there Configure where logs a written to and have PaaS read them
  • 16. activestate.com/stackato | @activestate | #stackato | activestate.com/blog | Copyright 2014 6) Logging And Monitoring https://github.com/Stackato-Apps/go-env staging logs application logs web console logging http://www.ideachampions.com/weblogs/Public-Speaking.jpg Logging DEMO
  • 17. activestate.com/stackato | @activestate | #stackato | activestate.com/blog | Copyright 2014 Over To You What will it take to get your applications running on the cloud? It doesn't have to be all-or-nothing Stackato provides lots of ways to support legacy applications that are not written with the cloud in mind
  • 18. Questions? Phil Whelan@philwhln philw@activestate.com May 2014 Contact Us: Ho Ming Li @HoReal homingl@activestate.com www.activestate.com/stackato
  • 19. Download Stackato http://www.activestate.com/stackato

×