Strangler application
- 2. Who am I ? • Develop enterprise applications • Currently at Perceptive Informatics
- 3. Agenda • Strangler Application – What ? – How ? – Why ? • Questions – Interruptions solicited !
- 4. What is a Strangler Application ?
- 5. What is a strangler application ? • Build grounds up • Integrated with legacy application • Phase out. Phase in
- 6. This is what we had
- 7. Where we wanted to be
- 8. Dependencies
- 12. Eventually…
- 13. How ?
- 15. Events
- 16. Events contd.
- 17. Data model
- 18. UI
- 19. Closing thoughts
- 20. Conclusion… • What worked ? • What didn’t ? • What makes an application easy to Strangulate ?
- 21. References • http://www.delicious.com/rajivnarula/Stran glerApplication
Editor's Notes
- #3: At perceptive, I have been involved in a refactoring project. And that is what I will be talking about tonight
- #4: Strangler application is a refactoring strategy. The basic idea is that you create a brand new application- grounds up. This application will gradually replace the existing application. I will explain more on what Strangler application is How we are using it in Perceptive- And finally some closing thoughts on how we have found this strategy in practice so far
- #7: The tan oval circles represent portions of the application which need to be refactored The reasons could be because of anything Incorrect dependencies Old technologies Poor performing code
- #8: A brand new shiny application !
- #11: So this is what a Strangler application looks like You start from grounds up However, you don’t wait till the whole application is done before you can start using it You keep on retiring services\\components from your existing application and move them to the new strangler application And slowly the application on the left will get strangulated by the application on the right
- #15: Opening statement
- #21: What worked: Easier to build than to re-factor Benefits delivered immediately What didn’t Two apps to maintain. Where to begin ?