История одного кастомного маркетплейса и его эволюция с нуля До энтерпрайз решения Как правильно готовить монолитную архитектуру и почему не стоит использовать микросервисы везде и всегда Как можно балансировать между требованием бизнеса и техническим долгом

1. Alexandr Vronskiy, OpsWay
Evolution of Ecommerce Application

2. ❖ A.k.a “shandyDev” on Twitter,
Skype, Github, etc
❖ Troubleshooter at OpsWay
❖ Docker & DevOps it-evangelist
❖ Love opensource:
➢ zend community
➢ opsway/doctrine-dbal-post
gresql
➢ opsway/zohobooks-api
About me

3. Let’s begin..
Let’s begin...

4. ● NO microservice way: what is this?
● NOT about TDD, BDD, DDD, EDD,
EventSourcing, CQRS, каратэ,
кунг-фу и много страшных слов…
● Without code
Let’s begin about...

5. Let’s begin
actually
about
● Main domains in ecommerce apps
Let’s begin actually
about...

6. Let’s begin
actually
about
● Main domains in ecommerce apps
● Marketplace 3-years evolution
Let’s begin actually
about...

7. Let’s begin
actually
about
● Main domains in ecommerce apps
● Marketplace 3-years evolution
● Build architecture of …
Let’s begin actually
about...

8. Let’s begin
actually
about
● Main domains in ecommerce apps
● Marketplace 3-years evolution
● Build architecture of …
● Monolith!
Let’s begin actually
about...

9. E-commerce
What case

10. Ecommerce world

11. Ecommerce
solutions
● Exists products solution & +
Ecommerce solutions

12. Ecommerce
solutions
● Exists products solution & +
● Custom + ERP, CRM, etc
Ecommerce solutions

13. Ecommerce
solutions
● Exists products solution & +
● Custom + ERP, CRM, etc
● SaaS (Shopify, Bigcommerce, ...)
Ecommerce solutions

14. Ecommerce
solutions
● Exists products solution & +
● Custom + ERP, CRM, etc
● SaaS (Shopify, Bigcommerce, ...)
● MIXED
Ecommerce solutions

15. solutions
Ecommerce solutions

16. FrontSite
(ZF2)
Concept idea: Use SOA
● Magento 1.x
● Custom app
● Akeneo
Magento
(ecommerce engine)
Elasticsearch
Akeneo
(PIM)
Customers
Backend
A long time ago in a
galaxy far far away

17. FrontSite
(ZF2)
● Easy bootstrap
● Fast & scalable storage
● Fulltext search, filters & aggregates built-in
Magento
(ecommerce engine)
Elasticsearch
Akeneo
(PIM)
Customers
Backend
A long time ago in a
galaxy far far away

18. FrontSite
(ZF2)
● Ready to handle shopping cart
● Checkout processing
● Order Management
● Seamless requests from front
Magento
(ecommerce engine)
Elasticsearch
Akeneo
(PIM)
Customers
Backend
A long time ago in a
galaxy far far away

19. FrontSite
(ZF2)
● Akeneo - ready PIM system
● PIM - Product Information Management
● Symfony + MongoDB
● Multichannel import / export connectors
Magento
(ecommerce engine)
Elasticsearch
Akeneo
(PIM)
Customers
Backend
A long time ago in a
galaxy far far away

20. 20
Vulpes lagopus (lat.)

21. FrontSite
(ZF2)
Magento
(ecommerce engine)
Elasticsearch
Akeneo
(PIM)
Customers
Backend
Why it’s fail?
too long
Need
customize
uncomfortable
not work easy

22. FrontSite
(ZF2)
Elasticsearch
Customers
Backend
How fixed?

23. FrontSite
API
(ZF2)
Postgresql
Elasticsearch
Backoffice
(Angular)
Customers
Backend
- Products: ~40M
- PriceLists: ~60M
(from 250+ suppliers)
- Postgresql: ~250Gb
- Elasticsearch: ~100Gb
Next level up!

24. First results
● Try (!not think) ready solutions as MVP

25. First results
● Try (!not think) ready solutions as MVP
● Not use universal combines for unique
business problems

26. First results
● Try (!not think) ready solutions as MVP
● Not use universal combines for unique
business problems
● Custom solution - minimize relations

27. First results
● Try (!not think) ready solutions as MVP
● Not use universal combines for unique
business problems
● Custom solution - minimize relations

28. Monoliths are different
Zend Framework 2
MVC Factories DI
IoC
Services
Configs
Modularity
Apigility
Doctrine
ZfcUser
ScnSocialAuth
...

29. Negative moments
Zend Framework 2
MVC Factories DI
IoC
Services
Configs
Modularity
Apigility
Doctrine
ZfcUser
ScnSocialAuth
...
❖ What about update to
ZF3, PHP7, etc??
❖ Dependency HELL!

31. ● No need duplicate clients behavior
Front site
Mobile App
Admin app
GatewayAPI
User
microservice
Catalog
microservice
Order
microservice
Microservices?

32. ● No need duplicate clients behavior
● Easy upgrade
Front site
Mobile App
Admin app
GatewayAPI
User
microservice
Catalog
microservice
Order
microservice
Microservices?

33. ● No need duplicate clients behavior
● Easy upgrade
● Develop in parallel
Front site
Mobile App
Admin app
GatewayAPI
User
microservice
Catalog
microservice
Order
microservice
Microservices?

34. ● No need duplicate clients behavior
● Easy upgrade
● Develop in parallel
● Scalability
Front site
Mobile App
Admin app
GatewayAPI
User
microservice
Catalog
microservice
Order
microservice
Microservices?

35. Front site
Mobile App
Admin app
GatewayAPI
User
microservice
Catalog
microservice
Order
microservice
Microservices? No!
● Increased size code

36. Front site
Mobile App
Admin app
GatewayAPI
User
microservice
Catalog
microservice
Order
microservice
Microservices? No!
● Increased size code
● Duplicate infrastructure code
Validate::email()
Validate::email()

37. Front site
Mobile App
Admin app
GatewayAPI
User
microservice
Catalog
microservice
Order
microservice
Microservices? No!
● Increased size code
● Duplicate infrastructure code
● Communications?
Validate::email()
Validate::email()

38. How to deal?

39. How to deal?
Can not update XXX XXX don’t support YYY
● Analysis & search
root causes of problems
Solutions:
● Remove XXX - 15h
● Add support YYY - 24h

40. Front module
Mobile App
Admin app
Public API
Private API
User domain
Catalog
domain
Order domain
CLI, Crons
Session
Templating
Infrastructure & so on... Business
● Reduce external dependencies
● No re-use cases
● Many internal interfaces
True monolith “Use DDD Luke!” © Obi-Van

41. Front module
Mobile App
Admin app
Public API
Private API
User domain
Catalog
domain
Order domain
CLI, Crons
Session
Templating
Infrastructure & so on... Business
● Can be anything
● Use business code
● Implement storage/persist/interactive
interfaces
True monolith “Use DDD Luke!” © Obi-Van

42. True monolith “Use DDD Luke!” © Obi-Van
Bootstrap
(or React + PSR7)
Routing
Action
(or Command)
Business Handler: RegisterCustomer
$eventManager->attach($userListeners);
$user = User::newCustomer($data);
$user->releaseEvents($eventManager);
$userRepo->save($user);
return $user->id(); // UserId class
instead of Uuid
UserDoctrineRepository
implements
UserRepositoryInterface
EventManager
implements ...

43. Today & next
● ZF3 + Apigility + Doctrine
● AngularJS v1.6 + ReactNative
● PHP7.2, NodeJS, Redis, Postgresql 10,
Elasticsearch 6
● Amazon AWS, Docker, Rancher, Jenkins,
CircleCI
● Websockets (real-time admin)
● Message queue (instead of cron tasks)

44. What is ecommerce
Five whales:
● PIM

45. What is ecommerce
Five whales:
● PIM
● Order Management

46. What is ecommerce
Five whales:
● PIM
● Order Management
● Inventory & stock

47. What is ecommerce
Five whales:
● PIM
● Order Management
● Inventory & stock
● Fulfilment & Logistics

48. What is ecommerce
Five whales:
● PIM
● Order Management
● Inventory & stock
● Fulfilment & Logistics
● CRM

49. What is ecommerce
Five whales:
● PIM
● Order Management
● Inventory & stock
● Fulfilment & Logistics
● CRM
● ERP / Finance

50. What is ecommerce
Five whales:
● PIM
● Order Management
● Inventory & stock
● Fulfilment & Logistics
● CRM
Others:
● CMS, Import/Export, Notifications
● ERP / Finance

51. ● Ecommerce - this is hard
Final results

52. ● Ecommerce - this is hard
● Monolith - this is not hard (32k LLOC) &
can be fast (4 devs)
Final results

53. ● Ecommerce - this is hard
● Monolith - this is not hard (32k LLOC) &
can be fast (4 devs)
● Firstly - business problem solving
Final results

54. ● Ecommerce - this is hard
● Monolith - this is not hard (32k LLOC) &
can be fast (4 devs)
● Firstly - business problem solving
● Secondly - refactoring
Final results

55. ● Ecommerce - this is hard
● Monolith - this is not hard (32k LLOC) &
can be fast (4 devs)
● Firstly - business problem solving
● Secondly - refactoring
● Include estimates on refactoring
Final results

56. ● Ecommerce - this is hard
● Monolith - this is not hard (32k LLOC) &
can be fast (4 devs)
● Firstly - business problem solving
● Secondly - refactoring
● Include estimates on refactoring
● Ping-Pong with clients
Final results

57. Questions? Yes!
Answers? May be!
Thank you for
attention!