Talks

Serverless systems allow us to concentrate solely on our code and let the provider deal with infrastructure issues such as scaling and routing. Serverless is best known for responding to events, however it is also an excellent choice for APIs and microservices. In this talk I looked at how to use Apache OpenWhisk to implement APIs using the Swift programming language.

Building line-of-business web applications for clients with traditional IT departments brings its own set of challenges when it comes to DevOps. In particular, the IT department adds additional constraints that you may not see in more forward-thinking companies. Rob Allen explores these complexities and shares some solutions he and his team came up with in order to use modern development practices in nontraditional environments. You’ll learn how CI tools with appropriate scripting enable reliable delivery of a quality product on IBM i and Windows. Rob also covers the organizational and technical challenges encountered when IT departments are not used to developers having a say in the server environment and shows you why it’s worth spending time getting them on board.

Serverless applications have a number of benefits and JavaScript is the most common language to write serverless functions in. Why not PHP? In this talk, I will discuss how I implemented first class PHP support into the Apache OpenWhisk platform. I look at how OpenWhisk works, how the PHP support is implemented and then walk though an example PHP serverless Slack application.

Serverless applications have a number of benefits and JavaScript is the most common language to write serverless functions in. Why not PHP? In this talk, I will discuss how I implemented first class PHP support into the Apache OpenWhisk platform. I look at how OpenWhisk works, how the PHP support is implemented and then walk though an example PHP serverless Slack application.

Everyone is writing APIs from micro-services through to full applications, but what makes a good one? In this session we’ll go back to the basics and look at what I consider to be five of the more important architectural features that you should think about when creating an API. These are the features that ensure that your API plays well with HTTP and, more importantly, make your API a delight to maintain and work with. I want you to ensure that your API is a good HTTP citizen, while also providing developer-friendly features like thoughtful error handling and documentation.

Everyone is writing APIs from micro-services through to full applications, but what makes a good one? In this session we’ll look at what I consider to be five of the more important architectural features that you should think about when creating an API. These are the features that ensure that your API plays well with HTTP and, more importantly, make your API a delight to maintain and work with. I want you to ensure that your API is a good HTTP citizen, while also providing developer-friendly features like thoughtful error handling and documentation.

Slim Framework builds on the PSR-7 HTTP message interfaces and provides useful features such as routing, and a DI container. It's lightweight and so is an ideal platform for building APIs. We'll look at how to use Slim as the basis for a fully featured API. We'll cover the key concepts around HTTP request-response resource APIs including handling content type and status codes, authentication and also returning errors appropriately. By the end of the session, you'll be able to build a Slim API.

We all know that the M in MVC stands for model, but what does that actually mean? Domain-driven design helps us map our software to the business requirements of our clients, but it can be quite hard to understand. In this talk I explored the fundamentals of Domain Driven Design and showed how to apply it to the design and implementation of the business logic of your application.

Apple has open sourced Swift, their new programming language, so you can now use it on Linux servers. Swift's static typing, concise syntax and speed make it a good language for all types of server-side software including APIs. In this session you'll learn how to build an API in Swift 3. We'll cover the key concepts around HTTP request-response resource APIs, including accepting and generating the correct content type, routing, authentication and also returning errors appropriately.

Photo

Apple's new Swift programming language is open source, fast and great for APIs. It's a great modern language which emphasises consistency, developer productivity and safety. As such, it's a great fit for writing APIs deployed to Linux, including microservices and server-less architectures.

This session will show you how to build a simple Swift API for deployment to IBM's OpenWhisk server-less environment. In order to do this, I will also cover key features of the Swift language and why it is good for server-side applications. I will discuss the *HTTP protocol* and how APIs fit within it and we'll look at how to build APIs in Swift before moving on to server-less ones.