1 / 15

Design For Failure Is The Path To Success In Cloud

Design For Failure Is The Path To Success In Cloud. Ashay Chaudhary. Requirements. Journey thru the computing models. Mainframe Desktop Client-Server Internet Cloud Computing. Reliability Availability Serviceability Performance + Security + Agility. Evolution of Requirements.

talbot
Download Presentation

Design For Failure Is The Path To Success In Cloud

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Design For Failure Is The Path To Success In Cloud Ashay Chaudhary

  2. Requirements Journey thru the computing models

  3. Mainframe • Desktop • Client-Server • Internet • Cloud Computing • Reliability • Availability • Serviceability • Performance + • Security + • Agility Evolution of Requirements

  4. Availability Non-Cloud Model

  5. Design for Non-Failure • Deploy with Redundancy • Manage Effectively Guiding Principles

  6. Design for Non-Failure • Quality Hardware • Deploy with Redundancy • Specialty Hardware • Manage Effectively • Expert Staff • Processes

  7. Availability Cloud Model

  8. Design for Failure • Design for Redundancy • Monitor Extensively • Track Dependencies Guiding Principles

  9. Assume nothing • Expect failures • Anywhere and everywhere • If it is available now, doesn’t mean it is there later • Failures cascade • Unhandled failures propagate • Poorly handled failures adds complexity • Difficulty increases exponentially with complexity • Embrace failure, make it a first class citizen Design For Failure

  10. Unhandled failures is a very bad idea • Poorly handled trivial failure in one part becomes a critical one somewhere else • Two types of failures: Transient and Resource • Transient failures are difficult, treat them like Resource failures and fail fast • Delays are transient failures, define response time guarantees • Failure injection is a lifestyle Handle All Failures

  11. Eliminate single points of failure • Architect distributed applications • Minimize duration of statefulness Design For Redundancy

  12. Self assess and report health • Complementary external monitoring • Load and latency monitoring • Proactively restart components Monitor Extensively

  13. Identify all dependencies • Hardware, 3rd Party Libraries, Other servers, Network • Infrastructure/Platform services, External services • Your own components • Track their health and availability Track Dependencies

  14. If there’s only one thing you could do • Design for Failure • It is a paradigm shift • It is a cultural change • It is not easy • It is the key to success in the cloud Key Takeaways

  15. Ashay Chaudhary Cloud Consultant Corporate Education Private Cloud Solutions Highly Scalable SaaS Applications SaaS Business Intelligence & Analytics ashay@kloudpros.com @ashay_c

More Related