•  

API Strategy and Practice Conference 2016 schedule

Thursday 3rd November 2016

  • The Past, Present, and Future of the API Economy

    by Mark O'Neill

    At 9:15am to 9:40am, Thursday 3rd November

  • The lost and found of API business Models

    by Susan Danziger

    Ever wonder what it’s like to launch an API – and then switch your business model mid-stream? Learn from our journey to find the right model for Ziggeo’s video API business -- and how we ultimately managed to launch a unique win-win solution.

    At 9:40am to 10:05am, Thursday 3rd November

    In Marriott Long Wharf

  • Keynote - Hacking on the Amazon Alexa with AWS Lambda and APIs

    by robmccauley

    Amazon has been an early pioneer in transforming legacy systems to a services-based API model. More recently, the Amazon Alexa team has refactored the Alexa Skills Kit reference architecture from one requiring server instances into a serverless model using AWS Lambda. Rob will provide an overview of the Alexa Skills Kit API endpoints, and discuss best practices and tools for building and consuming API services.

    At 10:05am to 10:30am, Thursday 3rd November

  • How to talk about APIs

    by Andrew Seward

    One of the more challenging aspects of working with APIs is that outside of your own little tech bubble, nobody actually knows what an API is – despite being hopelessly dependent on APIs for their day to day lives. So how do you talk about APIs to the masses of people who have no idea what they are? You're going to have to do it – you'll need to talk to your non-technical colleagues about it, many of whom you're entirely dependent upon to improve your API or get it out to the masses; there'll be potential customers out there for whom your API is the exact solution to the problem they're having and there's the people you meet who ask you what it is you do.

    In this talk we'll discuss how overcome this huge challenge for all of us in the business of APIs, how to establish not just a clear ubiquitous language when talking about our APIs but clarity and consistency of content - making sure your developers, salespeople, support and marketing are all talking about your APIs in a way that is accessible, meaningful and useful to all concerned, and how that consistency of understanding can be the difference between the success or failure of your API.

    At 11:00am to 12:30pm, Thursday 3rd November

  • How to train your API: Experiences from the wilderness and back again

    by Mandy whaley

    How do you design APIs in the context of lots of smart, divergent ideas? How do you do this when hardware is involved? In this talk we will share some of the methods and practices we are using and some of the lessons learned from the from the battle tested Cisco DevNet team.

    At 11:00am to 12:30pm, Thursday 3rd November

  • How to train your API: Experiences from the wilderness and back again

    by ashley roach

    How do you design APIs in the context of lots of smart, divergent ideas? How do you do this when hardware is involved? In this talk we will share some of the methods and practices we are using and some of the lessons learned from the from the battle tested Cisco DevNet team.

    At 11:00am to 12:30pm, Thursday 3rd November

    In Marriott Long Wharf

  • The 3 Ways Melvin Conway Saved Our Enterprise API Governance

    by Matthew Reinbold

    What happens when a company decides to API everything? Organizations may be quick to follow Netflix and Amazon in the pursuit of microservice and service orientated architecture (SOA). But without the application of Conway's Law, any governance effort (and, by extension, the API program) will fall short. Matthew has been instrumental in establishing and growing API governance programs at multiple enterprise companies.

    In this talk he will discuss effective API governance and the challenges in achieving it.

    At 11:00am to 12:30pm, Thursday 3rd November

  • The Death of Data

    by Heidi Waterhouse

    Hoarding is only really painful when we run out of space. In a world with very cheap data storage, it never occurs to us that we should be getting rid of data instead of just storing it in giant silos. I'll explain why we are storing increasingly dangerous poison in our databases, and why we ought to care about automated de-acquisition and deletion. Data gets senile. It forgets its links, it only wants to tell you about the old days. Wikis overgrow like the thorns around Sleeping Beauty's castle, and reference manuals accrete into sedimentary layers. APIs gather and leak data like municipal water systems Even with search, we can't find what we're looking for. Too much data is as bad or worse than no data. We are building giant predictive structures on big data, but we are not evaluating the age or value of that data. Have you ever been boggled by your credit report? We are building thousands of reports like that with no consideration for the quality of the data we are using. This talk is not about data in the abstract, it's about ergot poisoning and hoarding and konmari and bitrot. When and why to kill your precious data, why data is a double-edged sword.

    At 11:00am to 12:30pm, Thursday 3rd November

  • The Desire for Perfection vs. Reality

    by Matt Bernier

    We all want perfectly intuitive and amazing APIs that people look at and know how to use, documentation that changes lives, and API libraries that write the code for our customers. We would also love to have that yesterday. The reality is that there's never enough time, the team isn't big enough, some languages don't do [super sexy feature], and docs don't change lives. There have to be concessions. We found ways to innovate within reality and selectively chose our concessions in order to provide better features and functionality to our customers with a relatively small team.

    At 11:00am to 12:30pm, Thursday 3rd November

  • The end of polling: why and how to transform a REST API into a Data Streaming API.

    by Audrey Neveu

    IoT & Mobile, User eXperience, Interactivity and RESTful APIs...those topics are big trends in development today. The last one brings fast adoption and reduced development costs but is in opposition with the three others needs. IoT & Mobile need low latency whereas UX and interactivity need real-time data to keep user interest alive. As a developer you need to poll APIs to provide these real-time information, with all the limitations that this involves.

    On the other side as an API provider, being massively polled can become an issue and you're probably looking for a more resilient solution to offer to your consumer. What if we can apply the "Hollywood principle" to REST APIs? Don't poll us, we will push you! And why not going further by reducing the amount of data to transfer? In this talk, we'll see together which technology you should opt for and how to implement them to turn your API into a Data Streaming API.

    At 11:00am to 12:30pm, Thursday 3rd November

  • Your Documentation Is Your UX

    by Marc Cuva

    As APIs are becoming more widespread and used by an increasing number of people from non-technical backgrounds, documentation needs to evolve. When trying to use an API instead of consulting a long website with just paragraphs of text, documentation will need to be more tailored to the reader. How technical a user is, which technologies they are using to interact with an API, and how much they've used it in the past should all affect the documentation they are viewing. Being able to include API keys in code samples, adjust examples based on if a user is using Ruby, Node, etc. and showing relevant documentation after they encounter an error are all examples of how documentation can adapt to provide the most utility. Documentation is the user experience for the API, so it needs to be a first class citizen.

    At 11:00am to 12:30pm, Thursday 3rd November

  • API Product Management People, Price, and Product – In That Order

    by Jonathan Spinney

    When designing a new commercial API offering, People come first, Price comes second, and the Product third, and when approached this way it can inform your decisions for business support systems needed to support a self-service developer offering with variable pricing, unified currency, unified contracting, and unified billing.

    This talk will share vital lessons learned from Pitney Bowes, a global technology company processing billions of transactions a day, both digital & physical, across the borderless world of commerce. You will learn about their implementation and gain valuable insight into defining target personas, pricing APIs, and designing business systems support infrastructure needed to scale and introduce new APIs rapidly.

    At 1:30pm to 3:00pm, Thursday 3rd November

  • Documenting Hypermedia APIs

    by Irakli Nadareishvili

    Hypermedia API design style is one of the most exciting API design style currently practiced. Largely because it promises fundamentally valuable traits such as: evolvability, brows-ability and long-term sustainability. All great, however for everybody who has developed public-facing Hypermedia APIs, there's one painfully vivid and well-kept secret: documenting Hypermedia APIs is tough. There''s a lot of very mature tooling for documenting so-called "RESTful" APIs, at this point, some of them even being standardized but those tools don''t really match the style of Hypermedia well.

    Based on speaker's experience building Hypermedia APIs at multiple organizations, including the current company, as well as previous consulting experience helping organizations design and build Hypermedia APIs, we will give a look at the current state of the art of documenting Hypermedia APIs: best practices, worst practices and the prospect for the future.

    At 1:30pm to 3:00pm, Thursday 3rd November

  • How I got the CTO to pay for Open APIs

    by Melissa Jurkoic

    Companies have been integrating their systems internally and externally via APIs for many years. APIs are not new, but the idea of them being openly accessible and available to be discovered by someone without your permission is indeed new for companies. Our company had dealt with integrating with partners for over 20 years, but these were necessary due to customer demand, not seen as an opportunity to increase our reach or revenue for that matter.

    In order to convince C-level executives that there is an opportunity worth investing in, it is sometimes necessary to charge forward and create the outcome you need them to see. Using the experiences through this journey from integration to opportunity, this talk will explain how we achieved justification for an entire development team to be dedicated to deliver our future API strategy.

    At 1:30pm to 3:00pm, Thursday 3rd November

    In Marriott Long Wharf

  • Hypermedia vs Graphs: Best buddies or the next API battleground?

    by Gareth Jones

    We all wonder if this is the year that hypermedia becomes mainstream? But coming up on the rails, there is a new challenger: Graph-shaped APIs that predefine a wide network of relationships promise some of the benefits of hypermedia APIs, but present a more familiar programming model. Will graphs push aside hypermedia before it's even had a chance, or will both styles play nicely? Is this trend a blocker to HATEOS nirvana or a stepping stone?

    I'll challenge the audience to consider combining these two approaches to open the door to mainstream hypermedia use, enriching a fixed graph with dynamic data and behavior. Volatile data and logic can use hypermedia and more foundational data can use graph approaches. In this way we can add value and depth to our apps without the drastic rewrites we so often expect from the transition to hypermedia.

    At 1:30pm to 3:00pm, Thursday 3rd November

  • Protecting Ourselves from Ourselves: 3 Ways to see if an API Security Architecture is Working Properly

    by Pamela Dingle

    At 1:30pm to 3:00pm, Thursday 3rd November

  • Reverse Engineering Undocumented APIs with mitmproxy

    by chris busse

    mitmproxy (https://mitmproxy.org/) is a popular tool for observing HTTP(S) traffic between client applications and their API services by acting as a "man in the middle". The resulting service calls and their payloads can then be extracted and used in other applications and scripts. It also enables savvy users to hold apps accountable for how they transmit a user's private data. Popular apps such as Snapchat have had their APIs reverse engineered in this way, enabling user behavior that is unexpected (and sometimes undesirable) for app publishers. Another example is the small but growing open source community focused on studying the Robinhood stock brokerage app and its undocumented API that, as of this writing, remains open – enabling developers to experiment with $0 commission stock trading scripts.

    This presentation will show how to set up mitmproxy on a workstation, connect a second device, and log otherwise secure HTTPS traffic – capturing the underlying API calls to understand the functioning of undocumented 3rd-party APIs. We will also explore what this means for API publishers, app developers, and users concerned about their digital security.

    At 1:30pm to 3:00pm, Thursday 3rd November

  • Securing the Things: APIs in the IoT Era

    by Randy Westergren

    The explosion of IoT has brought numerous changes to the way we use technology. From massive enterprises to the individual consumer, improvements in convenience and automation of most aspects of our lives has seen dramatic progress – yet security continues to be an ongoing concern in the software and devices we've all grown to depend on. The talk will focus on examining the protocols used in popular IoT devices, including how each operates in the wild, the inherent security concerns during design, as well as real world examples of practical attacks against them.

    At 1:30pm to 3:00pm, Thursday 3rd November

  • Using Hypermedia APIs to Drive Interactive Mobile Applications

    by Ben Greenberg

    At Comcast, the backbone of cross-platform Xfinity TV experience is a hypermedia API supporting both XHTML and HAL as media types. It's given us several expected benefits: self-documentation, loose coupling, and discoverability. At the same time, it also uncovered some limitations of hypermedia.

    Hypermedia is designed so that the API works very similarly to a traditional web site—load a resource, follow a link, and then load the next resource. Modern, native mobile apps, on the other hand, try very hard to not present a page-oriented, wait and load experience. Users expect their apps to be responsive, fast, and not beholden to a page-like paradigm.

    In this presentation, Benjamin will discuss the design of our hypermedia API and demonstrate some of the strategies we''ve come up with to address these concerns. We'll use different examples from our API to illustrate how we promoted parallel requests, improved cacheability, and minimized response sizes, all while staying true to the link- and form-driven spirit of hypermedia.

    At 1:30pm to 3:00pm, Thursday 3rd November

  • API, Re-invented: How to Ship a Major New API Version Without Losing Your Mind (Or Your Developers)

    by Steve Rice

    The only thing harder than writing a new API is updating one that already exists. Learn about our real-world experience at PagerDuty designing, developing, releasing, and evangelizing a new version of our REST API with thousands of existing customers and a large developer community at stake. We'll cover what worked, what didn't, and what we learned about versioning, adoption, deprecation, documentation, developer experience, frameworks, tooling, customer impact, and more while bringing a 5-year-old, complex API at the core of our product up to date. No minds were lost (at least, not completely) in the making of this talk.

    At 3:05pm to 4:35pm, Thursday 3rd November

  • Creating a Great Developer Experience Through SDKs

    by Taylor Barnett

    Many of us know it can be difficult to maintain SDKs for an API; meanwhile, developers keep asking for them. So how do we ensure a great developer experience while working on decreasing the pains of maintaining SDKs? In this talk, we will explore how we can create a great developer experience through our SDKs with strategies like using data to make informed SDK decisions, defining community and product SDKs more clearly, determining when to treat SDKs as products, and much more. We will also look at examples of existing SDKs to learn documentation tips and tricks and what common pitfalls to avoid. The landscape of who is using our APIs is changing, and SDKs can be helpful for many new API users. So, let's learn how to use SDKs to maximize developer adoption while making sure they don't become a headache.

    At 3:05pm to 4:35pm, Thursday 3rd November

  • Effortless microservices running in production with Kubernetes

    by Ken Wronkiewicz

    With the Amazon API Gateway and Amazon Lambda, you can run a complete simple microservice in the cloud with no operations. But what if you are running a custom database or a sophisticated set of workflow services? Can you run that with as-close-to-NoOps-as-possible?

    In this presentation, Ken Wronkiewicz will demonstrate how to run an entire stack (from database to load balancer) inside of Kubernetes using the newly merged Ingress resources as an API gateway, how persistent storage works and which database engines best fit into the Kubernetes environment, and how to go from nothing to a chaos-monkey-ready self-healing infrastructure in weeks.

    At 3:05pm to 4:35pm, Thursday 3rd November

  • Microservices: gRPC or REST? Why not both?

    by Sandeep Dinesh

    Building APIs for microservices can be a challenge. They have to be well designed, easily understandable, and highly performant. The tried and true platform for modern APIs is JSON/REST, but the ridiculous demands that a microservices architecture places on the network and API stack has made many of us look to new open source technologies such as HTTP/2, Protobuf, and gRPC. With features like bi-directional streaming and binary compression, gRPC is an great choice for microservice deployments. However, migrating to new technologies can be a challenge, especially in a microservices world. They lack the robust tooling and ecosystems provided by JSON/REST, and the other microservices may depend on it, make moving to a pure gRPC implementation difficult.

    In this talk, I'll show you how you can build a gRPC endpoint that can intelligently serve gRPC over HTTP/2 while simultaneously serving JSON/REST over HTTP/1.1 on the same port! Then, I'll walk through some benchmarks and best practices for deploying these microservices in a scalable way.

    At 3:05pm to 4:35pm, Thursday 3rd November

  • Why writing our own documentation framework and tools was a terrible idea and how to recover

    by Brendan Cartledge

    Everyone knows that having good documentation for your API is vital, but what happens when you do it wrong the first time? This talk describes the rocky road of going from a manual, bespoke website for documentation, to an automated dream and everything we learned along the way.

    At 3:05pm to 4:35pm, Thursday 3rd November

  • Keynote - Scaling the Fitbit Web API

    by Jeremiah Lee Cohick

    Fitbit launched its Web API in 2011. It's now used by millions of people through Fitbit's apps and a vibrant third-party ecosystem. Jeremiah will share the product strategy, internal processes, and lessons learned from his experience managing the Fitbit Web API for three years.

    At 5:00pm to 5:25pm, Thursday 3rd November

  • Keynote - Unleash the Chaos

    by Mike Amundsen

    Throughout the history dating back before the Middle Ages, Chaos has led to important technical and social innovations. And, it turns out, introducing a selected level of Chaos into your organization is a proven way to increase the rate and success of innovative problem solving and product designs. Why is this so? And how can you take advantage of this important "superpower" of consistently innovative companies?

    Based on the work of Ori Brafman and others, this talk shows examples of three key traits of innovative cultures including "Whitespace", "The Unusual Suspects", and "Organized Serendipity" and provides guidance on how you can encourage these traits in your own team or company.

    At 5:50pm to 6:20pm, Thursday 3rd November

  • Keynote - How Low Can You Go? Reducing Costs and Development Time with AWS Lambda, API Gateway, Elastic Beanstalk, and 3scale

    by Erin McKean

    More than 18,000 developers have keys to the Wordnik API, which they use to build everything from edtech applications to word games to Twitterbots! Our original architecture has served more than 2bn calls since 2010, and has largely been a free service.

    When Wordnik relaunched as a nonprofit in late 2014, we realized we had to monetize our API to create a sustainable foundation for future development, and in order to monetize, we needed to reduce our operating costs and introduce new features -- neither of which our previous architecture made simple.

    Enter AWS Lambda+API Gateway! By breaking down our current API into tiny functions, we can take advantage of the current microservice craze with minimal ops headaches. And by using Elastic Beanstalk and 3Scale to manage a reverse proxy, handling routing between the old and new API calls and managing billing is much easier, too. Add a pretty Swagger interface on top and you''re good to go ... faster and cheaper!

    At 6:20pm to 6:30pm, Thursday 3rd November

Friday 4th November 2016

  • Keynote - A Problem Worth Solving

    by Charles L. Ashley III

    Empowering communities traditionally overlooked through code. We're heavily focused on the Native American communities in New Mexico (primarily the four corners area). Our mission for 2017 and beyond is to provide the same opportunities to areas like Yuma, AZ., Savannah, GA., El Centro, CA., and along with the various cities in NM that are suffering from high unemployment rates and lack of diversity in the technology job sector.

    At 9:55am to 10:20am, Friday 4th November

  • Panel - Media Panel: How APIs are causing a seachange

    by Tyler Love

    At 10:20am to 10:50am, Friday 4th November

  • An Introduction to the AAARRRP Developer Relations Strategy Framework and How You Can Use It

    by Phil Leggetter

    Many companies are considering building a developer relations programme. But deciding how you go about building that programme can be difficult. What are the goals of the programme, how do they align with the company goals, what activities should the new Developer Relations team undertake, how do those activities help other departments within the company and how should the success of the team be measured? In this talk I''ll introduce the AAARRRP Developer Relations Strategy Framework and talk through a practical example of how it''s been applied when building a DevRel strategy at Nexmo. More details on the AAARRRP framework can be found here.

    At 11:15am to 12:45pm, Friday 4th November

Schedule incomplete?

Add a new session

Filter by Day

Filter by coverage

Filter by Venue