Breaking Up with Your Solution: Migrating Your Ecommerce to a Microservices Platform
•Download as PPTX, PDF•
1 like•193 views
Skava’s senior director of product marketing, Jon Feldman, hosted a presentation at NRF Big Show 2019 discussing how slow development cycles, costly integration, and scale limitations are signs it’s time to break up with your existing commerce platform. Learn practical strategies and the benefits of moving off your legacy solution to a modern microservices platform. Stop throwing money at maintenance and focus on delivering tailored customer journeys!
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Breaking Up with Your Solution: Migrating Your Ecommerce to a Microservices Platform
Similar to Breaking Up with Your Solution: Migrating Your Ecommerce to a Microservices Platform (20)
More from Skava
More from Skava (8)
Recently uploaded
Recently uploaded (20)
Breaking Up with Your Solution: Migrating Your Ecommerce to a Microservices Platform
- 1. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. Breaking Up with Your Solution: Migrating Your Ecommerce to a Microservices Platform
- 2. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED.
- 3. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. • Understanding of Microservices in Commerce • How legacy commerce systems introduce friction • Terror Free Migration Session Takeaways
- 4. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. 4 93% of CXOs believe that digital will disrupt their business - Forrester
- 5. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. 5 87% of companies believe digital transformation is a competitive opportunity - Forrester
- 6. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. 6 By 2020, CEOs expect 41% of revenue to be driven by digital - Gartner
- 7. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. 7 What you want
- 8. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. 8 What you get
- 9. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. 9 What’s the problem?
- 10. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. 10 "Ideas are easy. Implementation is hard.” —Guy Kawasaki
- 11. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. 11 What was your platform built to do? When was it architected?
- 12. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. Stop me if you've heard this one before 12 • Development is slow, costly or risky • QA takes forever • You’re pushing the limits of what your platform can deliver • Integrations are costly or inefficient • You have new business requirements • Your TCO is out of control
- 13. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. Then things get real 13
- 14. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. Then things get real 14
- 15. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. 15 Maybe it’s not so hot
- 16. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. What can a modern platform do for you? 16
- 17. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. The Microservices Architecture 17
- 18. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. 18 Experiment with anything
- 19. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. 19 Bring features to market quickly
- 20. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. Partitioned Risk 20
- 21. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. 21 Technical resiliency to survive operational problems
- 22. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. And many more… 22 • Proven open source technologies • Easier to find resources • Integrates with anything • Scales atomically • In use now
- 23. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. How do I get there? 23
- 24. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. 24 A Constellation of Unpopular Options Replatform Gut it out Ignore it for another yearOutsource Hope for the best
- 25. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. The Big Bang Deployment
- 26. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. 26 The Alternative: The Strangler Pattern (Don’t throw it out)
- 27. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. 27 Keep the stuff that works Build new features in a modern framework Migrate at a pace that makes sense to your business No Big Bang!
- 28. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. Move at the pace of your business 28
- 29. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. Move at the pace of your business 29
- 30. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. Move at the pace of your business 30
- 31. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. You don’t need to stand still 31
- 32. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. Microservices Framework Architecture ORCHESTRATION DEVOPS MONITORING SERVICE DISCOVERY RESILIENCE MESSAGING DATA STORE MICROSERVICES DATA PROCESSING DISTRIBUTED CACHING CONFIGURATION MANAGEMET CONTAINER MANAGEMENT CONTENT MANAGEMENT
- 33. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. Search User Catalog Promotions 3rd Party Microservices Cart and Checkout OMS and CSR Inventory Loyalty BYO Custom Microservices Recommendations Wish List and Registry Skava supports an evolving architecture Skava Commerce API Orchestration Layer ERP Entitlement CRM Legacy Inventory WMS/3PLs Integration Layer 1 Customize
- 34. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. Search Catalog Promotions 3rd Party Microservices Cart and Checkout OMS and CSR Inventory Loyalty BYO Custom Microservices Recommendations Skava Commerce API Orchestration Layer ERP Entitlement CRM Legacy Inventory WMS/3PLs Integration Layer 1 Customize 2 Remove User Skava supports an evolving architecture
- 35. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. Search User Catalog Promotions 3rd Party Microservices Cart and Checkout OMS and CSR Inventory Loyalty BYO Custom Microservices Recommendations Wish List and Registry Skava Commerce API Orchestration Layer ERP Entitlement CRM Legacy Inventory WMS/3PLs Integration Layer 1 Customize 2 Remove 3 Add Pricing Skava supports an evolving architecture
- 36. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. Skava Commerce UNLEASH E-COMMERCE OUT OF THE BOX BUILD YOUR OWN PLATFORMTM ENHANCE YOUR EXISTING DIGITAL EXPERIENCES Everything you need to launch a cutting edge e-commerce solution out of the box. Use as a foundation to build your own digital future. Choose the microservices and digital applications you need.
- 37. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. Questions? Thank You
- 38. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED.
- 39. CONFIDENTIAL AND PROPRIETARY. ALL RIGHTS RESERVED. Stop me if you’ve heard this story 39 • Development is slow, costly or risky • QA takes forever • You’re pushing the limits of what your platform can deliver • Integrations are costly or inefficient • You have new business requirements • Your TCO is out of control
Editor's Notes
- Hello everyone and thank you Jon Feldman, Senior Director of Product Marketing We’re going to talk about digital commerce, getting more done, common friction, how microservices are an unlock to shipping more features.
- Thank you for attending! NRF wants to be sure that you know that these are Skava’s ideas, and not theirs Legal required slide
- Microservice advantage in commerce 2. Common friction points of legacy systems 3. How to migrate without terror So lets talk about digital commerce!!
- 93% of C level executives think that digital will disrupt their business That the impact of online is impacting virtually everyone And that its a big change
- And 87% felt that this presented a competitive opportunity
- Brick and mortar retailers who have online stores feel that 41% of their revenue will shift online by 2020. 2020 is next year! Online is clearly happening.
- Everyone wants to hit their goals We understand what needs to be done We are all smart We have vision
- Instead you get a train wreck Missed targets A big mess People standing around trying to understand what happened Did not execute Pensacola Florida
- What is keeping us from doing the things that we want? Why are upstarts able to move so fast? Why aren't my business requirements getting done?
- Guy Kawasaki: IDEAS are easy IMPLEMENTATION is hard And with your legacy commerce solution, its likely even harder Lets look at what happened
- Behold, STATE OF THE ART in 1999. Back in the day, THEY WERE ALL SEXY. Behold these FAST CARS. Look at that Scirocco - would have killed for that in college Pretty nice RED NUMBER UP FRONT
- Common issues: DEV is SLOW QA is a BOTTLENECK BUSINESS REQUIREMENTS are HARD to do in your CURRENT PLATFORM TCO is crazy HIGH You CAN’T DO what you want to with your CURRENT TECHNOLOGY INTEGRATIONS are super HARD
- Then you get an email like this Business not getting the features it wants Annoyed about spending on maintenance Wants better use of the money Why are you screwing us?
- Then you get an email like this Business not getting the features it wants Annoyed about spending on maintenance Wants better use of the money Why are you screwing us?
- 1999 Ford Probe at Copart, valued at $2,290, located in Baltimore. Rollover with biohazard & chemical dammage https://www.copart.com/lot/53373928
- NEW ARCHITECTURS have emerged over the last 10 years Designed to ADDRESS COMMON FRICTION points of legacy monolithic commerce systems
- OK, so lets talk architecture. Monolithic architectures, like Oracle Commerce, Websphere and Hybris put everything into one giant application. Totally a great idea at the time Was super fast Allowed scalability Fast processing Microservices, meanwhile are a collection of little apps Each with its own database and process Advances in networking and computing make this technology feasible – wasn’t in the past One failure doesn’t sink the ship You can change the parts easily without turning the whole thing off
- Legacy systems often punish experimentation - QA - ONE THING BREAKS and takes the whole ship with it - COMPLICATED CODE - FRONT AND BACK END are intertwined - Need to KEEP THE PLANE FLYING at all times In contrast microservices - COMPARTMENTALIZE the changes - If one thing breaks, NOT EVERYTHING BREAKS - And if its truly busted, you can FIX FORWARD and roll out the specific service and restart it, while remaining transactional
- New microservices platforms speed up development NO REGRESSION QA before launch LAUNCH ANY TIME – not in giant bundles LESS DEPENDANCIES MORE RESILLIANCE LESS RISK FAST TO FAIL
- COMPARTMENTALIZE RISK - Microservices let you keep the risk of changes or experimentation limited to the place you are experimenting with ITS OK TO FAIL - Breaking things isn’t a catastrophe DEPLOY IN MINUTES - Deployments can be minutes instead of hours You don’t need to bust caches, bring in your development team, the whole deal. Its faster SUPPORTS AGILE DEVELOPMENT
- Graceful failure Not everything assumes everything else will always be there
- Modern architectures leverage PROVEN OPEN SOURCE TECHNOLOGIES at all levels of the code Makes it easier to find people – you aren’t looking for an obscure technology engineer, but instead using COMMON TECHNOLOGIES Modern architecture means INTEGRATIONS ARE EASIER – everything is modern SCALE JUST THE MICROSERVICE you care about – you don’t need to lift all the boats, just the one that is sinking This is all proven, it really works!
- So all that sounds rad. I think its worth exploring a new platform But how do I get there? Isn’t this scary??
- Its totally scary Replatform Gut it out Ignore it Hope for the best Give up and outsource
- And like, every rip and replacement I’ve heard of went terribly No one wants another big bang To much revenue on the line Paying 2x licenses
- Hope! You don’t have to throw it away You can slowly deprecate it. Or strangle it. Depends on how friendly you are with your legacy system.
- The strangler pattern lets you Keep the things that work the way you want Build new stuff – the new requirements – on the new system while protecting the old one Migrations don’t stall out the business – you don’t have to focus on developing features for the OLD and the NEW systems at the same time No big bang! SO HOW??
- Also, it kills the big bang. Start by taking a small part of your existing app, and hand its functionality to a microservice Typically we see PIM or Personalization as a first step Then, as time goes on, you add more and more microservices, which replace the existing stuff Over time, you get a fully migrated system, but your customers and users won’t know it Protect what works, move at your pace
- Also, it kills the big bang. Start by taking a small part of your existing app, and hand its functionality to a microservice Typically we see PIM or Personalization as a first step Then, as time goes on, you add more and more microservices, which replace the existing stuff Over time, you get a fully migrated system, but your customers and users won’t know it Protect what works, move at your pace
- Also, it kills the big bang. Start by taking a small part of your existing app, and hand its functionality to a microservice Typically we see PIM or Personalization as a first step Then, as time goes on, you add more and more microservices, which replace the existing stuff Over time, you get a fully migrated system, but your customers and users won’t know it Protect what works, move at your pace
- Plus, during the migration, you can develop new functionality for the new system and put it into production immediately No development in two places at the same time
- Ok, let’s talk about infrastructure. This is the framework, the home that your microservices live in and the plumbing that connects them. And building it out can be one of the biggest and most time-consuming challenges for a team moving to microservices. We’ve done the legwork for you so you won’t have to start from scratch building your orchestration and messaging layers and all the other pieces you need... and you won’t have to battle through the learning curve that comes with each of them. For you technical folks in the room, our framework uses best-of-breed, open source technologies you see listed here. And Skava’s microservices come with the business tools to accelerate your time to market and make your solutions easy to use day to day without IT involvement.
- And that raises a key point -- digital commerce is constantly evolving. That last thing you want to do is swap out one legacy platform for another. Skava Commerce is modular, which means you can use the individual pieces of the platform and customize and extend them independently.
- Unlike monoliths where you have to keep the entire application running, with Skava you have ultimate flexibility to swap components in and out – you’re not forced to upgrade and maintain the entire solution as a single unit.
- And you can also bring your own microservices and plug them into the framework. You can use our ready-to-use infrastructure to build your own custom microservices or use the technologies and frameworks of your choice. They’ll work in our environment.
- As you probably know, Skava Commerce is architected from the ground up as an end-to-end platform of microservices. You can choose to implement the entire suite, or, thanks to the modularity of our platform you can pick and choose from our set of pre-built microservices and use only what you need. And you can do this either as part of a full-on Build-Your-Own-Platform initiative or as part of a process of enhancing your existing platform piece by piece. MULTI TENNANT SINGLE CODE BASE
- Common issues: DEV is SLOW QA is a BOTTLENECK BUSINESS REQUIREMENTS are HARD to do in your CURRENT PLATFORM TCO is crazy HIGH You CAN’T DO what you want to with your CURRENT TECHNOLOGY INTEGRATIONS are super HARD