Track: Modern API Architecture - Tools, Methods, Tactics

Location:

Day of week:

How would you design and implement your APIs if you were starting today? If you already have a lot of APIs, what should you be thinking about to keep up with competition? This track will highlight the latest tools and techniques around API design and usage; from things like contract-first API development and client generation techniques, to how APIs are changing for use cases like big data and streaming, to testing and operational aspects of dealing with APIs at scale.

Track Host:
Jean Barmash
Director of Engineering @Tradeshift & Organizer @CTOSchool Meetup
Jean Barmash is currently Sr.Director of Engineering at Tradeshift. He has over 15 years of experience in software industry, and has been part of 4 startups over the last seven years, 3 as CTO / VPE and one of which he co-founded. Prior to his entrepreneurial adventures, Jean held a variety of progressively senior roles in development, integration consulting, training, and team leadership. He worked for such companies as Trilogy, Symantec, Infusion and Alfresco, consulting to Fortune 100 companies like Ford, Toyota, Microsoft, Adobe, IHG, Citi, BofA, NBC, and Booz Allen Hamilton. Jean is passionate about raising the level of technical leadership, and for the last five years has been organizing CTO School meetup, an organization he co-founded and grew to over 1,600 members. Jean speaks frequently at conferences, meetups, blogs (infrequently) at http://hellofoobar.com, and tweets almost just as infrequently at @jbarmash. Jean lives in NY with his awesome and supportive wife and two hilariously-funny kids.
10:35am - 11:25am

by Stefanie Schirmer
API Lead @Etsy

At Etsy we have been doing some pioneering work with our APIs. We switched to API-first design, have experimented with concurrency handling in our composition layer, introduced strong typing into our API design, experimented with code generation, and built distributed tracing tools for API as part of this project.

We faced a common challenge: much of our logic was implemented twice. All of the code that was built for the...

11:50am - 12:40pm

by Manny Pelarinos
Senior Director of Distribution Platforms @ESPN

In this talk, Manny will discuss the tension of optimizing APIs for different experiences, while supporting hundreds of endpoints and many web and mobile applications at extreme scale. In the last few years ESPN has made many iterations on its API platform, eventually settling on developing a Product centric architecture along with a new platform to build APIs. This new platform supports a two-layer architecture that allows ESPN to optimize both for engineering...

1:40pm - 2:30pm

by Todd Montgomery
Ex-NASA researcher, Consultant

Today we have new protocols, such as WebSocket and HTTP/2, asynchronous APIs, such as ReactiveStreams, and microservice architectures. All of these bring the promise of high scalability, resiliency, and ease of development. But do they really deliver? What can evolve when the latest web protocols are leveraged fully with an asynchronous API design? In this session, we will look at these questions and explore what can be done and what effect different techniques may have.

2:55pm - 3:45pm

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

Open Space
4:10pm - 5:00pm

by Michael Uzquiano
CTO of CloudCMS, Alpaca.js Committer

In this talk, we will discuss how to scale API to accept many items. We will examine how to evolve the Evolution of ReST over HTTP to transactional, asynchronous bulk operations. Some of the things covered will include Discussion on job descriptors, workers, the job queue and scaling workers across an API cluster elastically. We will also discuss pPolling methods for job completion including HTTP long polling and Web Sockets (using library such as socket.io).

5:25pm - 6:15pm

by Stevie Graham
Founder @Tellerapi

What do you do when you want a fully transactional banking API but PSD 2 is years away and you doubt that banks will ever make a good faith effort to ship a usable API anyway? You attack the bank's own mobile app and reverse engineer its API, that's what. This talk will present a case study of reverse engineering APIs from several banks, and compare their design decisions to best practices.

Tracks

Monday, 13 June

Tuesday, 14 June

Wednesday, 15 June