The Web Through a Backend Engineer's Eyes
What comes next: code, data, systems, infrastructure, and automation
Slide contents
1. The Web Through a Backend Engineer's Eyes
What comes next: code, data, systems, infrastructure, and automation
2. Alexander Polomodov
Engineering manager in Tinkoff.ru acquisition
Public, unauthenticated part of tinkoff.ru
Release-free content management
Automation for acquisition channels
Personalization and A/B tests
3. The web is an evolution of systems
4. 01. Code Organization
From spaghetti to explicit architectural boundaries
5. Evolution starts as a fight for clear boundaries
6. 02. Data Storage
Every new class of problems brings a new class of storage
7. Storage is chosen for the product model
8. 03. System Design
From monoliths to services and serverless
9. Web architecture becomes distributed
10. 04. Infrastructure
Infrastructure stops being a separate workshop
11. The runtime moves to managed platforms
12. 05. Process Automation
The delivery pipeline becomes part of the product
13. Automation shifts focus from deploys to resilience
14. The web is a platform, not a page
Backend engineers live in distributed web systems
Code on platforms — CaaS, PaaS, serverless: the normal way to run backend
Data as a service — DBaaS lowers ops cost, raises the cost of design mistakes
Reliability in the pipeline — CI/CD and chaos engineering as daily practice
15. The web becomes systems engineering
Code boundaries matter as much as the framework
Storage is chosen for the product model
Infrastructure and pipeline are part of the architecture
The future of the web is distributed and managed
web = systems engineering
16. Questions?
polomodov.tech
All slides and links are in the Telegram channel
Alexander Polomodov, Engineering manager, Tinkoff.ru acquisition
@book_cube