Expect field-tested patterns, pitfalls to avoid, and ready-to-reuse templates that keep 200+ services running in production without losing your mind.

2. Let's get acquainted
➢ Solutions Architect at Silpo (E-commerce)
➢ In IT since 2008 (17 years of experience)
➢ Has experience in various roles (full-stack, backend,
team lead, architect, CTO)
➢ Prints on a 3d printer for PrintArmy

3. ➢ 10+ million orders during this last 3 years
➢ 6+ million unique Guests
Silpo E-commerce in Numbers
➢ IT specialists: 370+
➢ Teams: 35 (26 product teams + 9 service
teams)
➢ Releases: 30K+
➢ Merge requests: 50K+

4. Offline Shops
Silpo E-commerce
and Ecosystem
Today we’ll talk about…
➢ Products: 14+
➢ Service and microservices: 400+
➢ RPS: 4k+
➢ Requests per month: 6B+
➢ Total Data Served per month: 30TB+

5. Courier platform Picking platform
Merchant platform
SuperAPP LOKO SuperWEB
Core services:
PIM, OMS
Payment Gateway
GEO
services

6. PHP in microservices
world

7. Create a few PHP services
● Loose Coupling
● Scalability
● Parallel
Development
● Increased Complexity
● Higher Infrastructure
Costs
● Security Challenges
Pros: Cons:

8. PHP Frameworks hell
● Team have the
ability to choose
the framework
● Only team with
knowledge of specific
framework can efficiently
make changes in service
● Cross teams code review
will not be efficient
● The issue solved in one
service can appear in the
other
Pros: Cons:

9. PHP Frameworks hell

10. Symfony Framework
● One of the most
popular PHP
Frameworks
● Big and active
community
● Single approach
through all teams,
only business logic
is different
● Efficient cross teams
code review
● Performance overhead
(if out of the box)
● Configuration-heavy
● Development Speed
Pros: Cons:

11. Fixing Cons (Configuration-heavy and Development Speed)
Service Pack:
● Provides a set of required public and custom
Symfony bundles and configs with meaningful
default values (Configuration-heavy)
● Creating a new service: just require the Service
Pack via Composer and you’re ready to go
(Development Speed)
● Centralized fixes applied to all services at once
(Development Speed)

12. Service Pack secret (please, don't tell anyone)

13. Client interaction
● Client can get
access to any data
(can save time
during
development)
● Client can get access to
any data (security issue)
● Client knows about
backend architecture
● Refactoring or any
change on the backend
must be supported with
frontend
● Each service can be
accessed from the
outside
Pros: Cons:

14. Client interaction

15. Client interaction: API Gateway
● Single endpoint can
merge data from
different services
● Services are not
accessible from the
outside
● Client doesn’t know
about backend
architecture
● Single point for
monitoring and
alerting
● Can be a bottleneck
● Needs add proxy for
service endpoints
(development
overhead)
Pros: Cons:

16. Service to service sync interaction
● Any service can
get any
information from
other service
● Chaotic service to
service connections
● Very hard to
understand all
dependencies
Pros: Cons:

17. Service to service sync interaction

18. Service to service sync interaction: API Gateway
● Strict service to
service interaction
pattern
● Each service
knows only about
API Gateway
● Single point for
monitoring and
alerting
● Can be a bottleneck
● Needs add proxy for
service endpoints
(development overhead)
Pros: Cons:

19. Service to service async interaction

20. Typical PHP service

21. Typical PHP service structure

22. API web server
Keep in mind:
● One process per container in
k8s pod
● Each OpenSwoole worker has
its own php environment and
keeps the code in memory
● !!! Each worker maintains its
own persistent PHP state
across requests !!!

23. OpenSwooleBundle
Main features:
● Controls OpenSwoole server
(start/stop/reload/status)
● Integrates OpenSwoole request/response
handling with Symfony
● Ensures all state-dependent services
reset their state on each request
● Enables parallel execution of functions via
OpenSwoole coroutines
…
Clear state code example:

24. Swoole vs OpenSwoole

25. Metrics: Prometheus

26. Metrics: Mechanics
● PrometheusMetricsBundle - collects
Symfony metrics
● Custom collector - collects
OpenSwoole metrics
● Prometheus scrapes API service
metrics
● Workers and Cron jobs push metrics
to Pushgateway

27. Metrics: Visualization

28. Metrics: Visualization Examples
Symfony + Kubernetes
OpenSwoole

29. Alerts

30. Alerts: Prometheus Example
Alerts as a code
Prometheus rule

31. Alerts: PagerDuty & Slack Examples
PagerDuty incident
Slack alert

32. Logs

33. Logs: Implementation
● Filebeat Logstash Writes logs
directly to ElasticSearch
● Async write of logs via OpenSwoole
task workers
● Symfony Messenger component
integration with OpenSwoole task
transport
● Doesn’t overwhelm pods with a
huge volume of stdout logs
● Doesn’t affect request/response
latency

34. Errors and tracing

35. Errors and tracing: Sentry
● Async error & trace export via
OpenSwoole task workers
● Custom implementation of Sentry
HttpClientInterface to use OpenSwoole
task workers under the hood
● Doesn’t affect request/response latency
● Track 100% of errors and warnings
● Sample traces for 1% of requests, with
the ability to enforce tracing for specific
request

36. Errors and tracing: Sentry Alert Example
Alerts as a code Sentry alert
Slack alert

37. Errors and tracing: Sentry Tracing Example

38. Autoscaling

39. Autoscaling: First Iteration
Formula for KEDA
triggers:
query: sum(rate(http_requests_total{service="ecom--order-service"}[1m]))
threshold: "20"
How it works:
● Metric from Symfony
● Each pod can handle ~20 RPS safely
● If traffic grows → more pods
● If traffic drops → fewer pods
Traffic increase (RPS)
Pods scaled up to 13

40. Autoscaling: Second Iteration
Formula for KEDA
triggers:
query: ((sum(openswoole_workers_total - openswoole_workers_idle) / sum(openswoole_workers_total)) + 0.5) * kube_deployment_status_replicas_available
threshold: "1"
How it works:
● Metric from OpenSwoole
● Scales pods by worker load: when
workers are near full, add pods

41. Development Gates
● Cross-team code reviews
● Tests are part of the Definition of Done
● Static analyzers: PHPStan, PHPMD, PHPCP, etc.
● SonarQube rules and gates
● Security checks: dependency vulnerabilities, OWASP, SAST, secret detection

43. Our custom Symfony bundles are public now
https://github.com/silpo-tech
● OpenSwooleBundle
● RestBundle
● ExceptionHandlerBundle
● PaginatorBundle
● HealthCheckBundle
● FilterBundle
● … and more on GitHub

44. 300 UAH promo code for SilpoApp https://jobs.dou.ua/companies/silpo/vacancies/
Silpo (E-commerce) vacancies