La parole est aux speakers : Ben Smith

Publié le

Jusqu’au Forum PHP 2020, retrouvez nos interviews de speakers pour mieux comprendre leur parcours et le sujet qu’ils ou elles aborderont lors de leur conférence !

La conférence

The new LAMP stack is Serverless

AWS Lambda, Amazon API Gateway, MySQL, PHP - it’s LAMP but not as you know it. In this session, I’ll show why there has never been a better time to build serverless applications with PHP.

Using this new LAMP stack to build serverless applications allows PHP developers to benefit from the agility and scalability enabled by the serverless paradigm, all without needing to manage servers. I’ll demo how to get started running your PHP code using functions as a service. You’ll learn how to connect to databases at scale with spiky workloads, and continue to use your favourite libraries and tools, without impacting performance or availability.

Learn how to become a serverless PHP developer, and use the world’s most popular web runtime to build scalable, agile apps without the server management

Grace Hopper
23/10/2020
15:15-15:55

Do you think that there is only one LAMP stack?

No – the original meaning of the acronym itself can be applied differently, depending on your flavour of language be it Perl, PHP, or Python. Then, there’s a number of variations of LAMP packages. LAPP substitutes PostgreSQL for MySQL, a WAMP stack uses Microsoft Windows. XAMPP is a cross-platform version of the bundle that can be downloaded and installed on Microsoft Windows, Mac OS X, Solaris, or Linux. Essentially, they all refer to an application stack that is typically both free to use and open source, which functions as a general purpose web server.

More than LAMP stack, it’s also an architecture approach to move on FaaS (Function as a service) architecture. How to migrate when you use applications like WordPress, Magento and not building one from scratch?

Moving to a serverless LAMP stack does not necessarily mean moving to a multi-FaaS architecture. It’s feasible to host your application codebase in a single AWS Lambda function that automatically scales in line with application demand. This can be a good middle ground for those legacy systems which may be over-complicated to “detangle”. It is also a good first step for understanding some serverless architecture concepts without having to pull apart the application codebase.

The next stage is to identify and migrate components of the application that can be decoupled from the monolith with minimum risk. Typical examples are backend, asynchronous or scheduled tasks but varies for each application. After repeating this process a couple of times, the application begins to migrate into a decoupled multi FaaS serverless architecture.

Serverless sometimes feels like adding a lot of complexity to an application with the usage of more and more vendor lock. What do you respond to this?

A decoupled application can seem complex when like your application codebase and infrastructure is spread across multiple functions or services. However, what this means is that developers are able to offload much of the operational complexity. Backend infrastructure management tasks are completely abstracted away from your team. Engineers, no longer have to worry about provisioning servers or clusters, patching, operating system maintenance, capacity provisioning, and more. By stripping infrastructure management tasks away from the developers, businesses free up their teams to focus on applications and foster innovation. Moreover, this also makes it easier to get applications to market faster.

Une conférence présentée par

Ben SMITH
Ben SMITH
Ben Smith is a Senior developer advocate at AWS with a passion for serverless, automation and web development. With his AWS blog series on “The serverless LAMP stack”, Ben is especially interested in making serverless technologies more accessible for PHP developers.

Autres interviews