Building an API is easy. Building an API that meets both the needs of your users and your company while being scalable and flexible enough to evolve – that’s another matter altogether. Thankfully, the API space has evolved drastically over the last two years, and new technologies and tools make this extremely complicated process a lot easier.

When: March 4-5, 2016Where: Minneapolis, MNWhat: Services in the Enterprise: How Not to Fail

Many many years ago the idea of microservices was born, but in a slightly different fashion. The idea was simple, create modules that would talk to each other and could easily be plugged in or pulled out. The result today is known as SOA in the enterprise space, a problem that requires expensive middleware and fancy solutions. Are we doomed to let history repeat itself with microservices, or how can we ensure that our services are truly decoupled and that we are as agile to scale and expand as we were from day one. In this talk we’ll take a look at why the enterprise space failed with SOA, and how we can succeed with APIs.

Building a strong, collaborative community begins with understanding that each member of your community is an individual, with their own unique goals and desires. So how can you take thousands of people who communicate with different styles and have different life goals and help them to become one community? In this session we’ll focus on how to do just that, helping you build a strong community while also helping you help each of your members reach their personal, individualistic goals.

When: March 31, 2016Where: San Francisco, CAWhat: APIs for Microservices

The concept of Microservices is changing the way we build and architect our systems, but are we really setting ourselves up for success? How can we ensure that our APIs act as a contractual, yet flexible representation of our service – and how do we address the “glue” issue to prevent ourselves from service lock-in? In this session we’ll jump back into history to see what’s worked and what hasn’t, look at how to build truly decoupled services, and explore tools and technologies that make the entire process easier.

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.

Building a REST API is easy, but building an API that is designed to last – well that’s another story. In this workshop we’ll cover everything needed to design and build an API that is flexible enough to evolve over time, including design best practices, a dive into hypermedia (and the specs out there), and a look at community tools designed to make the entire process (this includes testing and documentation) more efficient. Each participant will also receive a complimentary copy of “Undisturbed REST,” the book we’ll use during this workshop.

As someone who is familiar with Mule, you may be wondering what you could be doing, or what products or features you could be using to make your life even easier. Join our developers as they share some advanced use cases within the platform, followed by an open Q&A session.

Documentation is a critical component of any API. But it goes beyond just explaining the API into understanding who your users are, what their use cases are, and then working to make their journey as simple as possible – while accounting for different learning styles.

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.

The concept of Microservices is changing the way we build and architect our systems, but are we really setting ourselves up for success? How can we ensure that our APIs act as a contractual, yet flexible representation of our service – and how do we address the “glue” issue to prevent ourselves from service lock-in? In this session we’ll jump back into history to see what’s worked and what hasn’t, look at how to build truly decoupled services, and explore tools and technologies that make the entire process easier.

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.

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’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.

When: July 26, 2016Where:OnlineWhat: Defend Your Brand With Help From Your Advocates

It doesn’t take much to deter potential customers from buying your product. When their careers are on the line, negative reviews and competitive smear campaigns only reinforce the fear, uncertainty, and doubt in their minds — and there’s nothing you can say to fix it. They don’t trust you…but they do trust the voices of their peers.

The key to battling that fear, uncertainty, and doubt is to connect those skeptical buyers with your happy customers — their peers. Join this live Google Hangout On Air to learn how companies like MuleSoft, BillTrust and Acquisio are sparking a movement behind their brands with advocate marketing.

Create beautiful RESTful APIs designed to meet your customers needs while also being agile enough to meet the demands of ever changing platforms and businesses. Along with learning about the different types of API formats, you’ll learn how to take a user first approach, take advantage of modern design techniques, and leave with a strong understanding of API design and development – including HATEOAS/ hypermedia usage.

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.

RAML 0.8 revolutionized the way we design, test, build, document, and share our APIs. Allowing for code reuse, pattern design, visual editing, easy mocking/ prototyping, and the ability to generate unit tests for test driven development, create documentation, and create SDKs all without writing a single line of code! RAML 1.0 goes even further in enabling companies with the ability to have a single specification with overlays for your different dev, QA, and production environments. Libraries allow you to pull in models quickly and easily in a namespaced manner without having to retype all of the code – allowing for reuse not just within your API, but across multiple APIs! Annotations give you flexibility to include vendor specific items in your RAML specification – without impacting other applications. And data types will further revolutionize how we plan our APIs, allowing you to focus on the data model and automatically generate schemas/ examples – instead of having to have separate and strict schemas for each content type as you do with some other specifications. Come learn how RAML makes the entire API lifecycle easy, and how RAML 1.0 makes it developer friendly.

The concept of Microservices is changing the way we build and architect our systems, but are we really setting ourselves up for success? How can we ensure that our APIs act as a contractual, yet flexible representation of our service – and how do we address the “glue” issue to prevent ourselves from service lock-in? In this session we’ll jump back into history to see what’s worked and what hasn’t, look at how to build truly decoupled services, and explore tools and technologies that make the entire process easier.

The concept of Microservices is changing the way we build and architect our systems, but are we really setting ourselves up for success? How can we ensure that our APIs act as a contractual, yet flexible representation of our service – and how do we address the “glue” issue to prevent ourselves from service lock-in? In this session we’ll jump back into history to see what’s worked and what hasn’t, look at how to build truly decoupled services, and explore tools and technologies that make the entire process easier.

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.

Everyone wants the perfect REST API but to truly conform to Fielding’s constraints means taking advantage of hypermedia, and using it as the engine of application state. This means going beyond just implementing a specification like HAL, Siren, or JSON API, and creating your links to provide enough information for both humans and machines. In this session, we’ll take a deep dive into what hypermedia is, what role it plays in RESTful APIs, the differences between specifications, and how to implement it and represent it correctly.

Building a REST API is easy, but building an API that is designed to last – well that’s another story. In this workshop we’ll cover everything needed to design and build an API that is flexible enough to evolve over time, including design best practices, a dive into hypermedia (and the specs out there), and a look at community tools designed to make the entire process (this includes testing and documentation) more efficient. Each participant will also receive a complimentary copy of “Undisturbed REST,” the book we’ll use during this workshop.

For many APIs, user experience is still an afterthought. The product has been developed, documentation is what it is, and developers are expected just to use your API. But the reality is, unless user (ie developer) experience is interwoven into every stage of your API’s lifecycle, you’re setting your users, and your API up for failure… while setting up your competitors (including future ones) for success. Join this session to learn how easy it is to be user first, while also learning how you can eliminate redundancies, save money, and build an experience your developers will love.

Building a REST API is easy, but building an API that is designed to last – well that’s another story. In this workshop we’ll cover everything needed to design and build an API that is flexible enough to evolve over time, including design best practices, hypermedia, and a look at community tooling to make the entire process (this includes testing and documentation) more efficient. Each participant will also receive a complimentary copy of “Undisturbed REST,” which we’ll use during this workshop.

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.

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.

Documentation is a critical component of any API. But it goes beyond just explaining the API into understanding who your users are, what their use cases are, and then working to make their journey as simple as possible – while accounting for different learning styles.