Deconstructing the monolith. Migrating complex systems simply and efficiently

1. © AND Digital 2018© AND Digital 2018
Deconstructing the monolith - migrating complex
systems simply and efficiently
October 2019

2. - Hybris - what is it?
- Hybris Layers
- Existing Hybris Architecture
- Pain Points before moving to
AWS
- How it was moved and how it
looked like in AWS
- Progressively Replatform
Agenda

3. Hybris prior to moving and pain points

4. “
“Hybris is an ecommerce platform which allows its
consumers to sell in both B2B and B2C markets effectively.
Hybris core is an ecommerce platform, but it has several
stand out features which build on this which allow you to
develop a full omni-channel solution.

5. Deconstructing the monolith - migrating complex systems
simply and efficientlyHybris Layers
APPLICATION LAYER
APACHE LAYER
SEARCH LAYER
DATABASE LAYER
URL redirects,static pages
& mod_jk loadbalancer
Hybris Product, Bespoke
Code, Impex Data, shared
media file mounts
Apache Solr -
Master/Worker Setup
Oracle RAC, Oracle DB
Primary Use

6. Deconstructing the monolith - migrating complex systems
simply and efficientlyExisting Hybris Architecture

7. Deconstructing the monolith - migrating complex systems
simply and efficiently
- Manual Deployments took 5-6
hours to complete - take a server
out of the load balancer, upgrade,
test and add back in.
- Manual Platforms - all configured
different which means problems are
seen further up the release cycle
- Provisioning of a new platform
took 8 weeks as hardware needs to
be added to increase capacity
- Rolling back - took less time but
database changes meant you might
be stuck
- Quality of code is generally low
due testing done later in the SDLC
cycle
- Accessing logs is via the logs on
the servers which means people
needed access
- Scaling and Self Healing means
manual installation
- Licence, People, Platform Costs -
generally very high
- Capability Low within the teams to
be able to move to AWS
- Interfaces a large amount to move
PAIN POINTS BEFORE MOVING TO AWS

8. How it was moved?

9. Moving by using AWS Foundational Services
1) Can it be automated, choose the right tools?
2) Look at what each tier does and see if it can be
moved to an AWS Service or another service,
remove layers not required?
3) Do the least amount of re-architecting, but use
AWS what its best for autoscaling, self-healing,
high availability?

10. Hybris
Automating via infrastructure as Code Tools
Scalability
without the
worry
Bootstrap,
self heal
Automate
deployments,
pipelines,
Custom AMI,
reduce
Deployment
times
Code
Repositories
Build
Environment
through code
What does this give you:
- All platforms built consistently
- Code deployment automated
- Blue/Green deployments
- All configuration stored in code
- Self Healing and auto scaling
- Ability to turn off platforms when
not in use
- Time to build a new platform
significantly reduced

11. Deconstructing the monolith - migrating complex systems
simply and efficientlyApache Layer replaced with:
APACHE LAYER
Used for URL redirects, static
pages and mod_jk
loadbalancer
Elastic Load Balancer
redirects/static pages
served at edge

12. Deconstructing the monolith - migrating complex systems
simply and efficientlyApplication Layer moved to:
Hybris Product, Bespoke
Code, Impex Data, shared
media file mounts
APPLICATION LAYER
EC2 Instances
Deploy Bespoke Code

13. Deconstructing the monolith - migrating complex systems
simply and efficientlySearch Layer moved to:
Apache Solr - Master/Slave
Setup
SEARCH LAYER

14. Deconstructing the monolith - migrating complex systems
simply and efficientlyDatabase Layer moved to:
Oracle RAC
DATABASE LAYER

15. AWS Hybris Architecture

16. Changing how you deploy Hybris in this way brings you a number of benefits
What does this achieve?
© AND Digital 2018
Faster, Safer Deployments - using bespoke AMI’s which has product code
preinstalled, means less time to bring up a server. Through the use of
blue/green deployments we can spin up a newer version of Hybris at the side,
test, then make live.
Automatic Scaling - through the use of certain metrics to automatically force
a server to spin up and put into the load balancer once ready.
Self Healing - If an instance fails, it will terminate the node, then autoscaling
with bring up a new one.
Reduce environment costs - Ability to turn off lower environments, scale down
instances. No longer need to buy hardware.
Keep it clean - spin up environments clean or deploy onto clean servers.
Consistent Platforms - from Dev to Production, all platforms should mirror
each other.

17. Progressively Replatform

18. Gradually Replacing the monolith with new services
Bespoke services platform being built with API’s to gradually replace the Hybris Backend Services

19. © AND Digital 2018
Q A