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. We’ll start by looking at OpenWhisk’s architecture and what happens when you invoke a function. Then, I’ll show you how I implemented the PHP support and walk though some example PHP serverless actions.
Purchase a video of this course at NomadPHP.
Slim Framework OverviewPresented at PHPEM Unconference, November, 2017
An overview of Slim Framework in 20 minutes.
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.
OAuth 2 is the gold standard for authentication in APIs and in this talk I took a deep dive into how it works and how to implement an OAuth 2 server in your API. There are a number of work flows in OAuth 2 for different scenarios including mobile apps and websites connecting via JavaScript, so I looked at each one and showed how to implement the password and client credentials grant types.
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.
