Book Image

PHP 7 Programming Blueprints

By : Jose Palala, Martin Helmich
Book Image

PHP 7 Programming Blueprints

By: Jose Palala, Martin Helmich

Overview of this book

When it comes to modern web development, performance is everything. The latest version of PHP has been improvised and updated to make it easier to build for performance, improved engine execution, better memory usage, and a new and extended set of tools. If you’re a web developer, what’s not to love? This guide will show you how to make full use of PHP 7 with a range of practical projects that will not only teach you the principles, but also show you how to put them into practice. It will push and extend your skills, helping you to become a more confident and fluent PHP developer. You’ll find out how to build a social newsletter service, a simple blog with a search capability using Elasticsearch, as well as a chat application. We’ll also show you how to create a RESTful web service, a database class to manage a shopping cart on an e-commerce site and how to build an asynchronous microservice architecture. With further guidance on using reactive extensions in PHP, we’re sure that you’ll find everything you need to take full advantage of PHP 7. So dive in now!
Table of Contents (15 chapters)
PHP 7 Programming Blueprints
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Preface
4
Build a Simple Blog with Search Capability using Elasticsearch

First steps with Ratchet


In this section, you will learn how to install and use the Ratchet framework. It's important to note that Ratchet applications work differently than regular PHP applications that are deployed in a web server and work on a per-request basis. This will require you to adopt a new way of thinking of how PHP applications are run and deployed.

Architectural considerations

Implementing a WebSocket server with PHP is not trivial. Traditionally, PHP's architecture revolves around the classical request/reply paradigm: the web server receives a request, passes it to the PHP interpreter (which is typically built into the web server or managed by a process manager such as PHP-FPM), which processes the request and returns a response to the web server who in turn responds to the client. The lifetime of data in a PHP script is limited to a single request (a principle that is called Shared Nothing).

This works well for classical web applications; especially the Shared Nothing principle...