How can I listen to the db in real time?

Define realtime? View it how?

You can listen to all db queries being run in the boot() method of the AppServiceProvider (or another provider)

public function boot() {
    \DB::listen(function($query) {
        $sql = $query->sql;
        $bindings = $query->bindings;
        $executionTime = $query->time;

        // do something with the above. Log it, stream it via pusher, etc
    });
}

Yes, but for example I do not make a request, but I received a request from an external service, how do I know if I need to process it?

I'm not sure what you're meaning, and that seems different than your original question of "listen the db in real time." The above is how you retrieve the queries in "realtime"...as they are executed by laravel.

As far as

but I received a request from an external service, how do I know if I need to process it

That would depend on how you're handling the "receiving a request from an external service." I don't know your criteria for "needing to know if I need to process it," but it seems the logic would go in that.

Simplest way is to enable query logging in the database software and then just read that file.

For instance, for MySQL there is the General Query Log (https://dev.mysql.com/doc/refman/8.0/en/query-log.html). All actions and queries are written to a file. Using command line, you can then use 'tail -f logfile' to see all queries run across your screen in real time.

Maybe you could also use a package like https://github.com/samuele-artuso/mysql-query-monitor? I don't know exactly what it does, I only found it while Googling for "mysql watch query real time".

Database triggers

@Cronix Unfortunately, this does not work, because the query is executed only when the client loads the page. I want to reduce everything to the autonomous operation of the system. When the client filled out the form and got the result. I have a very large database and I can not get the client to wait for a response from the server.

@Thyrosis As one of the options, so maybe I'll try in my next project, I really liked the chips of the new version.

@jimmck Could you please clarify, as far as I understand, the trigger is triggered when the event occurs, but the question is how to launch the first wiretapper of the event? Create cron?

I made it through the queue https://laravel.com/docs/5.6/queues#delayed-dispatching This is what you need to solve problems

Just for future implementation... I made this to work with mysql binlog as mentioned by @thyrosis using this project: https://github.com/telanflow/laravel-binlog

All steps are documented in the wiki, but basically are this. - Enable mysql replication. - Install swoole extension for php. - Configure the binlog project. - Start de binlog service. - Do whatever you need with the data.