The cloud promises cost savings, agility, and more. But the increasing complexity of modern IT systems often prevents businesses from realizing the outcomes they sought by moving to the cloud in the first place. At the core of this complexity is technical debt. Ad hoc decisions, traditional approaches, and "quick and dirty" solutions add up to fragile, more complex systems (and organizations)--reducing the pace of change, driving up costs, and degrading security. To succeed in the cloud, you first have to manage the problems IT complexity creates. This practical guide will help. If you're tasked with designing, delivering, or approving IT systems that support business growth, this book will teach you the principles and strategies you need to break out of silos, reassess traditional thinking, provide the business a better competitive position, and achieve cloud success across the company. You'll
Lee Atchison is a software architect, author, and recognized voice on cloud computing and engineering leadership.
He is the author of *Architecting for Scale* (O'Reilly Media, now in its second edition) and *Overcoming IT Complexity* (O'Reilly), and the creator of multiple courses for O'Reilly Media and LinkedIn Learning. He writes the *Software Architecture Insights* newsletter and co-hosts on *Software Engineering Daily*.
Lee has spent more than three decades in the software industry. That includes seven years at Amazon and AWS, where he worked on Amazon Retail systems and built AWS Elastic Beanstalk, and eight years at New Relic, where he led architecture for New Relic's SaaS observability platform.
He most recently served as CTO at AI company, Product Genius.
Today he writes and consults through his own practice, Atchison Technology.
His work has taken him to engineering teams at Nike, Disney, Starbucks, MLB, Deutsche Telekom, and Bank of America, and to conference stages including AWS re:Invent. The thread connecting all of it is a question he keeps hearing from developers, architects, and engineering leaders alike: as AI changes what software work means, how do we stay relevant?
Interesting conceptualization of a topic that will likely see increasing relevance. Flexibility is desirable to give employees choice, but the trade-off is that it breeds complexity, which breeds fragility vs. rigidity in processes and design, and that is why an adaptive architecture is needed.
As the topics covered can be abstract, the points could be strengthened and linked with more real-world examples and counterexamples, but overall, this is a quick and worthwhile perspective on nurturing the "right" sort of IT ecosystem.