In this session we’ll take a look at building a Representational State Transfer (REST) API, starting off with a quick overview of what REST is, why REST over RPC/ SOAP, CRUD and HTTP Action Verbs, longevity, using HATEOAS/ HAL, responses and messaging, design and prototyping, documentation, and making your API easy to use.

One of the greatest challenges to developing an API is ensuring that your API lasts. After all, you don’t want to have to release and manage multiple versions of your API just because you weren’t expecting users to use it a certain way, or because you didn’t anticipate far enough down the roadmap. In this session we’ll talk about the challenge of API Longevity, as well as ways to increase your API lifecycle including having a proper mindset, careful design, agile user experience and prototyping, best design practices including hypermedia, and the challenge of maintaining persistence.

One of the greatest challenges to developing an API is ensuring that your API lasts. After all, you don’t want to have to release and manage multiple versions of your API just because you weren’t expecting users to use it a certain way, or because you didn’t anticipate far enough down the roadmap. In this session we’ll talk about the challenge of API Longevity, as well as ways to increase your API lifecycle including having a proper mindset, careful design, agile user experience and prototyping, best design practices including hypermedia, and the challenge of maintaining persistence.

In this session we’re going to take a hard look at hypermedia, and what it really means to utilize HATEOAS (hypermedia as the engine of application state). We’re also going to jump into different hypertext specifications, tackle the hypermedia vs documentation debate, and take a good hard look at how hypermedia can help extend the life of your API. But we’re also going to take a hard look at the cons of implementing hypermedia, and why not everyone is a fan. In short, we want to look at the good, the bad, and the downright ugly to make sure that we utilize hypermedia in our RESTful APIs in the most efficient manner possible.

Developer Relations/ evangelism is one of the hottest buzzwords in technology with more and more companies putting the focus on building and expanding their developer communities. In this session we’ll take a look at the common traps that cause developer relations programs to fail, and what your company can do to avoid them.

Mule ESB is the world’s most widely used ESB, and let’s you easily connect all your data, apps, and devices while also letting you quickly build flexible, extendable APIs with built in RAML support. Come learn how easy it is to quickly build and deploy apps, while also learning how you can contribute back to the community and make it easy for developers to connect and consume your API in this hour workshop.

One of the greatest challenges to developing an API is ensuring that your API lasts. After all, you don’t want to have to release and manage multiple versions of your API just because you weren’t expecting users to use it a certain way, or because you didn’t anticipate far enough down the roadmap. In this session we’ll talk about the challenge of API Longevity, as well as ways to increase your API lifecycle including having a proper mindset, careful design, agile user experience and prototyping, best design practices including hypermedia, and the challenge of maintaining persistence.

When: May 17, 2015Where: Regency Ballroom – San Francisco, CAWhat: The Danger of Creativity in the Workplace

Everyone says they’re looking for creativity, for people who think outside of the box. But are we really looking for creativity, or conformity? Let’s take a look at what creativity is, and why more times than not it results in workplace reprimands. Let’s talk about ideas that have been flat out rejected – only to make millions later on. Let’s talk about how creativity is inspired, and how it is mitigated. And above all, let’s talk about why, in the workplace, it’s seen as dangerous…

When: May 20-21, 2015Where: Broomfield, COWhat: Hypermedia: The Good, the Bad, and the Ugly

In this session we’re going to take a hard look at hypermedia, and what it really means to utilize HATEOAS (hypermedia as the engine of application state). We’re also going to jump into different hypertext specifications, tackle the hypermedia vs documentation debate, and take a good hard look at how hypermedia can help extend the life of your API. But we’re also going to take a hard look at the cons of implementing hypermedia, and why not everyone is a fan. In short, we want to look at the good, the bad, and the downright ugly to make sure that we utilize hypermedia in our RESTful APIs in the most efficient manner possible.

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.

IOT is one of the biggest buzz words in the industry right now, with more and more gadgets becoming “internet” devices. But where is IOT going, and what does it hold for the future? More importantly, how can one manage not just the internet of things, but the integration of things – and what does this mean for your API?

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.

When: July 2, 2015Where: San Francisco, CAWhat: Building APIs More Quickly 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!

One of the newer tools API developers have in their arsenal is RAML, or the RESTful API Modeling Language – a spec that lets you efficiently and easily design your API, gain valuable user feedback before writing any code, and even lets you start parallel development of your applications before the API is finished (as you have a working prototype, documentation, and even SDKs ready for use). Imagine being able to not just create an API that your team (and users) will love, but substantially cut the development time for mobile applications! RAML lets you do all of this, and much more.

Wouldn’t it be awesome if you could design your entire API, mock it out for developers to try out, and even generate multiple all of your documentation and tooling from SDKs to API tests in 15 minutes? Doesn’t seem possible – well with RAML and the open source tools surrounding it, you can do all that – and more!

One of the greatest challenges to developing an API is ensuring that your API lasts. After all, you don’t want to have to release and manage multiple versions of your API just because you weren’t expecting users to use it a certain way, or because you didn’t anticipate far enough down the roadmap. In this session we’ll talk about the challenge of API Longevity, as well as ways to increase your API lifecycle including having a proper mindset, careful design, agile user experience and prototyping, best design practices including hypermedia, and the challenge of maintaining persistence.

When: September 28-30, 2015Where: San Francisco, CAWhat: Hypermedia: The Good, the Bad, and the Ugly

In this session we’re going to take a hard look at hypermedia, and what it really means to utilize HATEOAS (hypermedia as the engine of application state). We’re also going to jump into different hypertext specifications, tackle the hypermedia vs documentation debate, and take a good hard look at how hypermedia can help extend the life of your API. But we’re also going to take a hard look at the cons of implementing hypermedia, and why not everyone is a fan. In short, we want to look at the good, the bad, and the downright ugly to make sure that we utilize hypermedia in our RESTful APIs in the most efficient manner possible.

Spec Driven Development isn’t just changing the way we build APIs, but even the way we share and document them. In this session we’ll take a look at what Spec Driven Development is, and how it ties developers and technical writers to the hip – helping keep documentation in sync, while reducing the work-load required to generate technical documentation, and even allows for use of modern tools such as RAML and the API Notebook that let us write and share documentation in a brand new, interactive way!

Version 1.0 of RAML, the RESTful API Modeling Language has been released, making code reuse, models, and covering the full API/ Software Life cycles even easier! With RAML 1.0 you can truly design, build, test, documenting, and share your API.

Microservices and SaaS applications are constantly increasing the need for agile, flexible, and scalable APIs. In this session we’ll take a look at some of the changes in the API space, and how these changes combined with hypermedia can help us succeed in developing the next generation of REST APIs.