Disposable-First Architecture: Build Fast, Kill Faster [ukr]

Wanna listen

How to design architecture for a product that already has a successful production environment, but where you still want to launch startup-like initiatives inside it? How do you avoid breaking a stable system, keep user trust, and at the same time give the business room for experiments?

Painful cases of “heavy features” that didn’t stick
How we turned the business desire for “more and faster” into architecture
A successful case of fast features: Secret Boxes in Expirenza
Problems that came after the success of a “temporary” feature
Shifting the development team’s mindset

Oleksandr Khomenko

Solution Architect, mono

Oleksandr is part of the large mono team; he works as a Solution Architect on the monomarket project and has also contributed to Expirenza by mono
His focus areas include platform architecture, feature delivery, observability, and incident management
With over 10 years in IT, he has worked on both complex B2B and high-load B2C/fintech products. He knows how to balance business needs with solution stability
He loves cats, Java, and good food