JeremyDeane

Architecture documentation is crucial for comprehending requirements, steering design, validating implementation, and maintaining solutions. Unfortunately, it is often overlooked, either tackled at the beginning or pushed to the end of a project cycle. Consequently, the documentation quickly becomes outdated, making it ineffective when extending a solution or resolving a production incident. This session offers guidance on creating and maintaining architecture documentation that remains current and useful.

Software architecture involves inherent trade-offs. Some of these trade-offs are clear, such as performance versus security or availability versus consistency, while others are more subtle, like resiliency versus affordability. This presentation will discuss various architectural trade-offs and strategies for managing them.

No matter the techniques used to make enterprise solutions Highly Available (HA), failure is inevitable at some point. Resiliency refers to how quickly a system reacts to and recovers from such failures. This presentation discusses various architectural resiliency techniques and patterns that help increase Mean Time to Failure (MTTF), also known as Fault Tolerance, and decrease Mean Time to Recovery (MTTR).

This presentation teaches you how to strategically introduce technology innovations by applying specific change patterns to groups and individuals. By using these patterns and techniques, you'll not only benefit your organization but also enhance your career as a technologist, making you a more effective influencer, writer, and speaker.