RESTful APIs are often designed and implemented before a client gets to see how they work, but once an API is made public, it can be hard to change. Dave Forgac and Ian Zelikman explain how to improve this process by explicitly designing the API contract and getting client feedback before implementation and outline processes and tools for building RESTful APIs with a design-first approach. Dave and Ian show how you can use these tools together in a contract-first development workflow and take you through the process of developing a new feature from beginning to end.
Dave Forgac is a senior software engineer at Complion in Cleveland, OH. Dave has been a FOSS enthusiast ever since installing Linux for the first time in the late ’90’s. He loves building communities and is an organizer of PyOhio, ClePy, and the Cleveland API Meetup.
Ian Zelikman is a software engineer at IBM Watson Health, where he works with big data and healthcare. Ian has worked with web technologies for over 10 years, ever since his first job developing applications for weather forecasting and analysis. Ian has been a Pythonista for over four years experience developing scalable and reliable backend systems and designing and integrating with web APIs.
©2017, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org