1 / 9

Reducing Business Risk with Ken

Reducing Business Risk with Ken. Resilience in One Slide. Failures will happen Acceptable: Looks like slow performance Unacceptable: Manual intervention, lost work Ken R educes set of unacceptable failures Reduces scope of affected parties Ken is infrastructure

jamar
Download Presentation

Reducing Business Risk with Ken

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. ReducingBusiness Riskwith Ken

  2. Resilience in One Slide • Failures will happen • Acceptable: Looks like slow performance • Unacceptable: Manual intervention, lost work • Ken • Reduces set of unacceptable failures • Reduces scope of affected parties • Ken is infrastructure • Don’t need to code resilience into each app • Ken resilience is composable • Independent services written to Ken • Composition is resilient when they interact

  3. More Detail • But not too much 

  4. Be Afraid, Be Very Afraid

  5. Problem • SOA is distributed by its nature • Failures will occur • Processing: OS panic, CPU failure • Network: Partition, message replay • Loss of entire data center • Failure types • Tolerated: Looks like slow performance at worst • Untolerated: Manual intervention, lost work • Want to minimize untolerated failures

  6. Ken Reduces Cost and Risk • Implemented in the infrastructure • Reduces development costs and resilience errors • Restartable on different hardware • Handles permanent hardware failures • Loss of entire data centers • Composable Resilience for free • When two Ken services start interacting, • Composition has same resilience with no work.

  7. Issues • Only for event driven programs • Avoids risk of transient deadlocks in production • Interactions with non-Ken components • Handled with drivers • Need libraries that obey Ken rules • Most do, but must review to be sure

  8. Ken Status • Parts of Ken for C/C++ in production use • Indigo • Google’s V8 • Waterken for Java • Passed security review run by David Wagner (UCB) • Easier to write resilient, secure programs in Java • Replaces the need for most of the programmers to learn how to write reliable code for distributed systems with the need to enhance and support the waterken open source code.

  9. Next Steps • Identify resilience today • Categorize tolerated vs. untolerated failures • Evaluate impact of untolerated failures • Compare with Ken resilience • Many untolerated failures affect subset of users • Evaluate relative business risk • Evaluate issues with both approaches • Decide to use Ken or not

More Related