seregazhuk

Introduction to DriftPHP. Create an application, configure async controller, and route.

For many of you, ReactPHP and especially its EventLoop component looks like magic. We know that it handles concurrency, but the way it works inside is a sort of black box. In these tutorials I want to dig into it, to figure out how it works under the hood. How it handles all these events inside.

The third interview with Marc Morera, an author of DriftPHP. At this time we talk about using CQRS in async PHP and ReactPHP.

The second interview with Marc Morera, an author of DriftPHP. We talk about the problem of the database persistence layer in asynchronous PHP. We discuss DBAL and ORM for ReaectPHP.

Interview with Marc Morera, an author of DriftPHP. We talk about asynchronous PHP, DriftPHP and ReactPHP.

Now we can protect some resources in our RESTful API ...

It's now time to add sign-in functionality to our RESTful API. We'll have to use JWT for that...

REST is the most widespread and effective standard to develop APIs for internet services. When building RESTful services, it is really important to choose the right framework. If you are a PHP developer and performance is critical for you, ReactPHP with its asynchronous, event-driven architecture, is exactly the right choice for building RESTful APIs. This book explains in detail how to create your own RESTful API in asynchronous PHP that can be consumed by other users in your organization.

A package to automatically restart PHP application once the source code changes. Can be very useful for developing long-running PHP applications

Time to add authentication. Let's start with user signup.

Let's see how we can serve static images asynchronously!

Monitor for any changes in your php application and automatically restart it (suitable for async apps).

When building a traditional web application in PHP we don’t care about reloading it. We make some changes in the source code, save it, then make the request in the browser or some other client and we can see these changes. They have already applied automatically because of the nature of PHP, its request-response model. On every new request each time we bootstrap the whole application.

We are already storing data in our database but what about files? Let's upload images!

After finishing products now its time to also connect our order routes to the database.

Let's improve our Http responses and make them self-descriptive.

Let's ensure that only right data makes it into the database.

It's time to actually persist the data in the database.

It's time to actually persist the data in the database.

Let's add a database connection and make our first asynchronous query.

Let's parse the request body so that our RESTful API can receive and use data.

Previously we have used Basic HTTP Authentication to protect our RESTful API. This authentication method is pretty simple, but in most cases, it can be used only in the internal network with server-to-server communication. For example, we can’t store Basic Authentication credentials to mobile devices. JSON Web Tokens is another solution to protect our RESTful API.

In the previous article, we have created a RESTful API on top of ReactPHP HTTP server. Now we want to protect our API and add authentication. When it comes to securing a RESTful API things became interesting because a truly RESTful API should remain stateless. It means that the server doesn’t store sessions, all the information that the server needs to handle each request should be contained in the request itself.

In this tutorial, we will use a proxy server to hide our scraper.