Track: Microservices and Monoliths


Day of week:

Practical lessons on services. Asks the question when and when to NOT go with Microservices?

Track Host:
Sudhir Tonse
Cloud Pioneer managing Realtime Data @Uber
Sudhir Tonse manages the Realtime Data Intelligence team at Uber. Earlier, Sudhir managed the Cloud Platform Infrastructure team at Netflix and was responsible for many of the services and components that form the Netflix Cloud Platform as a Service. Many of these components have been open sourced under the NetflixOSS umbrella. Open source contribution includes Archaius: a dynamic configuration/properties management library, Ribbon: an Inter Process Communications framework that includes Cloud friendly Software load balancers, Karyon: the nucleus of a PaaS service etc. Prior to Netflix, Sudhir was an Architect at Netscape/AOL delivering large-scale consumer and enterprise applications in the area of Personalization, Infrastructure and Advertising Solutions. Sudhir is a weekend golfer and tries to make the most of the wonderful California weather and public courses.
10:35am - 11:25am

by Adrian Cockcroft
Tech Fellow @BatteryVentures best known for Microservice/Cloud Architectures @Netflix

Adrian Cockcroft has been at the fore front of the MicroServices revolution and helped coin many of the patterns and techniques that define that space. He will address the current trends and successes in this domain in terms of companies who have adopted this style and how they currently fare. He will also share his insights from the ring side view he has gained by observing companies via his Venture based interactions.


11:50am - 12:40pm

by Daniel Rolnick
CTO @Yodle

Who could say no to services that were fully testable, easy to scale, easy to re-write, composable, etc. You read a few books about micro-services and now you're hooked. Those blog posts by Martin Fowler made it sound so easy. Adrian Cockcroft’s videos were so convincing. All of the open source tools out there were going to make this a snap. But now you’re six months in and realize that it's not all so easy. We’ll discuss 6 things we wish we had known when we started our journey.


1:40pm - 2:30pm

by Richard Kasperowski
Author of The Core Protocols: A Guide to Greatness

Open Space
2:55pm - 3:45pm

by Emily Reinhold
Software Engineer @Uber

Uber had a monolith endearingly named "API" - which at the time comprised of the bulk of Uber's backend processing code. As this service was getting unwieldy to maintain - for scalability and a variety of reason - we launched on a journey to break this up into Microservices. Thus began "Project Darwin". Little did we realize what we were in for. Turns out that migrations are not easy, and take a long, long time. At Uber, the physical world depends on our service...

4:10pm - 5:00pm

by Daniel Bryant
Chief Scientist @OpenCredo

All is not completely rosy in microservice-land. It is often a sign of an architectural approach’s maturity that in addition to the emergence of well established principles and practices, that anti-patterns also begin to be identified and classified. In this talk we introduce the 2016 edition of the seven deadly sins that if left unchecked could easily ruin your next microservices project... This talk will take a tour of some of the nastiest anti-patterns in...

5:25pm - 6:15pm

by John Billings
Tech Lead @Yelp

At Yelp we value our ability to quickly ship code. One key factor in scaling our engineering process to over three hundred engineers and several million lines of Python has been our move to a microservices architecture; over the course of the past four years we've gone from zero to over one hundred production microservices. During this process we've had to solve many difficult technical issues, but some of the most interesting challenges have involved the human...


Monday, 13 June

Tuesday, 14 June

Wednesday, 15 June