Blugento Romania (ZentoShop.com) process of building a Magento Software-as-a-Serivce product and the journey to running it ona state-of-the art Kubernetes cluster inside AWS.
1 of 33
Download to read offline
More Related Content
Journey to a multi-tenant e commerce solution in the cloud with Kubernetes - AWS Loft Bucharest
2. Journey to a multi-tenant
eCommerce solution in the
cloud with Kubernetes
3. Vlad Stnescu
CTO & Founder @ Blugento
Former CEO & Founder @ MindMagnet
@VladStanescu
Adrian Balcan
DevOps @ Blugento
10 yrs experience in DevOps
@Adrian_Balcan
5. Monolith PHP application
Relies on local storage
Not built for cloud
WHAT WE DO / Application
6. Deploy with one command
Upgrade with one command
Run application in isolated environment
GOAL PRODUCT MARKET FIT
THE STONE AGE / Requirements
8. THE STONE AGE / Deployment
Individual git repos for each module
Deploy with Git Pull
Core modules on create, optional modules added manually
Manual update of modules
9. THE STONE AGE / The Problem
Does it work
Isolated
Resilient
Scalable
Affordable
Maintainable
Manageable
Monitoring
YES
YES
NO
NO
NOT with scale
NOT really
Somewhat
NOT really
11. NEW SETUP / Requirements Checklist
No single point of failure
Namespace isolation
Cost efficient (low load => low cost)
Centralized management
PaaS MySQL
PaaS Filesystem
PaaS DNS
14. 1.0
AWS Architecture - KOPS
Advantages
Best option to deploy Kubernetes on AWS
Infrastructure as code
Ease of deployment
Ease of management
Flexibility of Kubernetes version
Challenges
Self-management of Masters
ETCD know-how
17. 1.0
Whats Great
No single point of failure
Stable & Scalable
Centralised Management
ToDo
Monitoring
Issues & Problems
ElastiCache instability/latency due to multi-db
EFS mount problems
Networking
Manual SSL certificate management
20. 2.0
Whats Great
More Stable & Scalable
Monitoring
ToDo
Enhance monitoring
Improve Logging performance
Issues & Problems
Autoscaler
Networking
Heavy linux distribution and scaling (minor)
23. MONITORING
Access Logs (with time)
Pods
CPU
Memory
IO
Nodes/Cluster
CPU
Memory
IO
Networking
MySQL Queries
Admin audit trail
24. 3.0
Whats Great
More Stable & Scalable
Great Monitoring and Logging
CentOS distribution
Issues & Problems
Multi-account EFS
25. THE FUTURE
Blugento 2.0 Application
Upgrade from Magento 1 to Magento 2
Implement frontend in PWA
Microservice oriented approach
Serverless components
No more local storage
32. CONCLUSIONS
New technologies are painful
but worth it
Use PaaS wherever possible
Infrastructure as code
Monitoring is key
Automate everything
Pay attention to Limits & Costs
o EFS/EBS IOPS & Burst Balance
o Network traffic costs
o Aurora IOs
o CloudWatch costs
o EFS, S3 count limit (soft and hard)
33. Thank you!
Vlad Stnescu
CTO & Founder @ Blugento
Former CEO & Founder @ MindMagnet
@VladStanescu
Adrian Balcan
DevOps @ Blugento
10 yrs experience in DevOps
@Adrian_Balcan