One of the newest and most powerful features in PHP 5.4 is Traits, or the ability to implement horizontal design into your application. In this session we will take a look at what traits are and how to use them (including examples of when to use horizontal design) as well as review the ReflectionClass and how it can be used to describe the traits in your code base.

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, looking at other REST APIs, planning our architecture, building the API in Zend Framework 2, and then looking at and solving API related challenges.

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, looking at other REST APIs, planning our architecture, building the API in Zend Framework 2, and then looking at and solving API related challenges.

PHP is one of the most popular programming languages used for web development, and one of the easiest to learn. In this 4 hour workshop we’ll cover the basics of PHP programming and take a look at how you can incorporate PHP into your web development from a practical standpoint to create dynamic content and interact with your users.

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.

RESTful API Modeling Language (RAML) is a simple and succinct way of describing practically-RESTful APIs. It encourages reuse, enables discovery and pattern-sharing, and aims for merit-based emergence of best practices. In this session we’ll take a look at writing and using RAML to design and prototype APIs, as well as utilize the power of RAML, Ruby, and open source to provide up to date, easy to read API documentation.

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.

RESTful API Modeling Language (RAML) is a simple and succinct way of describing practically-RESTful APIs. It encourages reuse, enables discovery and pattern-sharing, and aims for merit-based emergence of best practices. In this session we’ll take a look at writing and using RAML to create interactive documents using open source tools.

One of the newest and most powerful features in PHP 5.4 is Traits, or the ability to implement horizontal design into your application. In this session we will take a look at what traits are and how to use them (including examples of when to use horizontal design) as well as review the ReflectionClass and how it can be used to describe the traits in your code base.

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.

Sure you can spend hours implementing different APIs, searching for documentation, and debugging code… Or with MuleSoft’s FREE Anypoint Studio you can drag, drop, connect. In this session we’ll take a look at how you can use Anypoint Studio and Mule ESB to do even more with your application in less time, covering important basics including installation, connectors, using incoming data, the payload, accessing APIs (including REST and SOAP), connecting to Databases, and more!

Sure you can spend hours implementing different APIs, searching for documentation, and debugging code… Or with MuleSoft’s FREE Anypoint Studio you can drag, drop, connect. In this session we’ll take a look at how you can use Anypoint Studio and Mule ESB to do even more with your application in less time, covering important basics including installation, connectors, using incoming data, the payload, accessing APIs (including REST and SOAP), connecting to Databases, and more!

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.

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.

RESTful API Modeling Language (RAML) is a simple and succinct way of describing practically-RESTful APIs. It encourages reuse, enables discovery and pattern-sharing, and aims for merit-based emergence of best practices. In this session we’ll take a look at the importance of designing your API as well as how to use RAML to create define, mock, and create interactive documents using open source tools.

When: November 17, 2014Where: San Diego, CAWhat: Building Your API for Longevity

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.