Architecture Synthesis

Description

Welcome to the Leanpub Launch video for Architecture Synthesis: The Next Correct Step https://leanpub.com/architecture-synthesis-the-next-correct-step by Sergiy Yevtushenko! 0:00 Sergiy introduces himself and the book's goal of turning architecture from art into engineering 0:48 The ticketing system example: same domain, entirely different architectures 1:39 How business scale and requirements — not domain — determine architecture 2:26 The unified runtime project: a layer between business logic and infrastructure 3:12 Comparing the unified runtime to Kubernetes and the BEAM virtual machine for Elixir 3:58 Mention of Sergiy's other Leanpub books: Java Backend Coding Technology and Process First Design 0:00 Architecture Synthesis as the completion of a series moving software development toward engineering 1:39 Why domains don't define architecture — business context does 2:26 One more book planned, focused on a new kind of deployment model 3:12 Architecture Synthesis described as combining direct theoretical language tightly with practical examples About the Book Architecture Synthesis derives where computation happens — deployment topology, data placement, consistency boundaries, recovery — from a system's service-level objectives, instead of choosing it from a catalog of styles. Derived, not chosen. Most architecture books are one of two kinds: a catalog of styles and patterns you pick from and defend, or a physics of how replication, queues, and consensus actually behave. Neither tells you what to do on Monday. This is the missing third kind — a procedure. The method runs on nine questions, translated into six architecture axes through a fixed set of rules, and closed with verification arithmetic: back-of-envelope capacity and availability math that checks a derived architecture against its own budget before anything is built. An architecture produced this way is never a one-time choice — it is re-derived whenever the answers change, on a greenfield system and on one you inherited, by the same procedure. Part I builds the toolkit: an answer sheet whose questions each had to earn their seat, a ledger of what every architectural value provides and what it costs, the derivation procedure itself, and the verification gate. Small enough to apply from memory — a worksheet and a deck of reference cards. Part II puts it on trial. The method re-derives one system on home ground, then derives four systems it does not control — Stack Overflow, Shopify, Discord, and a national companies registrar — blind, from their public commitments alone, with predictions registered in advance and graded in the open. The hits are shown. So are the misses, because a method that never fails is a parlor trick. The registered predictions, answer sheets, and grading rubrics are public in a replication kit, and counterexamples are invited. A practicing architect can start here directly. A reader arriving from Process-First Design will recognize this as the next step. Less art, more engineering — in the one decision that was still run on taste. About the Author Sergiy Yevtushenko is a Senior Software Architect with over 35 years of hands-on programming experience. Based in Poland, he specializes in building robust, high-performance backend systems using Java and Rust, with a particular focus on type safety and functional programming patterns that make invalid states unrepresentable. He is the creator of Pragmatica Lite, a zero-dependency Java library providing monadic types (Result, Option, Promise) that eliminate null pointer exceptions and simplify asynchronous code. His technical writing on functional programming in Java has appeared on Medium and DEV Community, where articles like "Beautiful World of Monads" and "We Should Write Java Code Differently" have introduced thousands of developers to pragmatic functional approaches. Sergiy's work bridges theory and practice - he believes that well-designed types and patterns can transform backend development from an error-prone craft into an engineered discipline. This book distills those insights into a practical methodology for modern Java development. Thank you for watching, please like and leave a comment, we'd love to hear from you! Please Subscribe and Follow! YouTube: https://www.youtube.com/leanpub X: https://x.com/leanpub Instagram: https://www.instagram.com/leanpub Facebook: https://www.facebook.com/leanpub Create Your Own Leanpub Book! You can create your own book anytime here: https://leanpub.com/create/book Here's the tutorial showing how to write and publish a Leanpub book in your browser (it's free!): http://help.leanpub.com/en/articles/2932527-getting-started-writing-a-book-in-the-web-browser-writing-mode If you're a Leanpub author and you'd like to submit your own Launch video for us to publish, or if you'd like to record a Launch video with Len, please go here: https://leanpub.com/launch. #books #leanpublishing #selfpublishing #leanpub #writing #softwarearchitecture #systemdesign #architecturedecisions #backendengineering #distributedsystems