Episode 132: Top 10 Architecture Mistakes with Eoin Woods

Disaster Recovery

Disaster recovery is often overlooked in software architecture, yet its absence can lead to catastrophic consequences. Eoin Woods emphasizes that integrating disaster recovery plans from the outset is crucial, as retrofitting them later is fraught with challenges 1. He compares disaster recovery to house insurance, noting that while it's tempting to defer it, the cost of not having it can be severe 2.

For every piece you add, you have to work out how you're going to do recovery or failover on that piece, adding it afterwards to a system that's had no thought of disaster recovery from the beginning.

--- Eoin Woods

Woods advises that disaster recovery should be incrementally introduced during the system design phase to avoid inefficiencies and manual errors during actual disasters 3.

   

Performance Assumptions

Assumptions about system performance can lead to significant pitfalls if not properly tested. Eoin Woods warns against relying on vendor benchmarks without verification, as they often don't reflect real-world conditions 4. He suggests building performance prototypes and conducting hands-on testing to ensure systems meet non-functional requirements 5.

Don't assume that all the stuff in your environment works the way that people tell you.

--- Eoin Woods

By understanding dependencies and isolating technology-specific components, developers can avoid spreading issues throughout the system 4.

   

Security Challenges

Security architecture often suffers from do-it-yourself approaches that can introduce vulnerabilities. Eoin Woods highlights the dangers of attempting to create custom security solutions without expert knowledge, which can lead to significant issues in production 5. He stresses the importance of using proven, reusable infrastructure to avoid security holes 6.

There's a whole lot of moving parts and they need to be integrated. Otherwise you have security holes right through the.

--- Eoin Woods

Woods advises against locking into specific security products, advocating for the right abstractions to maintain flexibility and security 5.