PHP is no longer limited to sitting behind a web server like Apache or NGINX waiting for requests to process. Serverless PHP with AWS’s lambda service is now possible. At the same time, you can also write event-driven, asynchronous servers with ReactPHP. In this issue, we take a look at these new ways to use PHP.

In recent years, a different way to build applications has arisen called serverless computing. This term is not a good name; I’m reminded of the adage that there are two hard problems in programming: naming things, cache invalidation, and off-by-one errors. Serverless computing as a name implies no servers, but there are servers—you don’t think about them though. A better way to think about it is that the servers and the management of them are abstracted away and the provider manages the allocation of resources, not the application architect. In this article, I’m going to walk through how to use Lambda with PHP to execute a function.

Writing clean code, managing technical debt, testing with Mockery, Toxic Tech, API specifications, and more.

PHP Unit, Mockery, Type Hints, Async PHP, building a REST API, training programs, PHP isolation and security, serverless computing, Laravel auth, and more.

The new kid on the block is this “serverless” technology. But what’s the fuss about? This new concept seems intriguing if only for the name, and has perhaps even garnered skepticism because of the name. I’m sure you’ve heard the joke “there is no cloud, it’s just someone else’s computer” before, but serverless appears to […]