Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Containers and Micro-Services

Sponsored · Ship Features Fearlessly Turn features on and off without deploys. Used by thousands of Ruby developers.

Containers and Micro-Services

Presented at the Container Summit, hosted by Joyent, in New York City on April 8th, 2015.

Avatar for Jason Pincin

Jason Pincin

April 08, 2015
Tweet

Other Decks in Technology

Transcript

  1. #nodebf @walmartlabs @jasonpincin • microservice platform • 900+ processes •

    multiple DCs Analytics Mobile Device Config • 1,540 processes • multiple DCs • 150,000 msg/sec peak
  2. Scalability & Availability • Simple to increase capacity • Failure

    tolerant • Failure isolation • Efficiency
  3. Microservice Properties • Simple, does one thing • API exposed

    to network • Independently deployable • Disposable • Collections form applications
  4. Did it work? • Reduce complexity • Avoid developer gridlock

    • Ship constantly • Fewer meetings • Simple to increase capacity • Failure tolerant • Failure isolation • Efficiency
  5. More Microservice Benefits • Simplified & asynchronous delivery pipeline •

    Implementation agnostic; avoids commitment to technology stack • Loose coupling
  6. Zone Images cont. • Robust server support • Limited/No tooling/support

    for other platforms • Required additional plumbing to be applicable to microservice deployment process • Led to arbitrary process division
  7. Docker • All the advantages of zones • Able to

    run same container in all environments • Big and growing ecosystem • Excellent tooling
  8. Docker (but…) • Required Linux (back to virtualization) • Another

    layer on top of that • Concerned about performance, overhead, and efficiency that led to zones to begin with • Giving up DTrace, MDB, etc
  9. Triton • Native speed • Keep the Debugging toolchain •

    Single Docker host means simplified, consistent provisioning and deployment - let platform figure it out • Microservices’ BFF