API First: Design First, Prototype First with RAML

API dev today is code first and design later. In this session we’ll take a look at how to test your API before writing one line of code!

The greatest challenge in software development is designing for longevity, especially when your application is being used by thousands of other developers and needs to remain backwards compatible. In this session we’ll take a look at building a solid REST API with a quick overview of what it means to be REST, best practices, and how to use RAML to build a prototype of your API that can be critically reviewed by your developers before ever writing one line of code. We’ll wrap up showing how the same RAML you wrote for designing your API works to keep your documentation up to date and provides even more powerful tools to get developers using your API right away.

Speaker: Mike Stowe (@mikegstowe (https://twitter.com/mikegstowe)) is a professional, Zend Certified Engineer with over 10 years experience building applications for law enforcement, the medical field, nonprofits, and numerous industrial companies. Over the last two years he has been focused on APIs and ways to improve industry standards and efficiency. He now works for MuleSoft, a company on the leading edge of API development and management, as well as SOA/ ESB architectures. You can view slides from his other talks at http://mikestowe.com/slides or follow him: @mikegstowe (https://twitter.com/mikegstowe)

Sponsors: MuleSoft

MuleSoft’s mission is to connect the world’s applications, data and devices. MuleSoft makes connecting anything easy with Anypoint Platform™, the complete integration platform for SaaS, SOA and APIs. Thousands of organizations in 60 countries, from emerging brands to Global 500 enterprises, use MuleSoft to innovate faster and gain competitive advantage.