laravel-websockets VS laravel-debugbar

I'm working on a real-time chat application but facing some issues while working with broadcasting events using the laravel-websockets package. Things were working fine yesterday and I was receiving messages from private and public channels but I don't know why I'm not receiving messages anymore.

Yes I did and even found that documentation but I just wanted to confirm that I'm on the right track. Do you suggest using Laravel-Websockets or Pusher as a broadcaster? I am inclined to use Laravel-Websockets just because it's free (so I wouldn't have recurrent costs), however I don't want to end up with limitations or issues later on.

Laravel Echo is free and part of Laravel. You need to use it with a websockets server or a service like Pusher or Ably, and that is what you pay for. But if you make your own websockets server with Laravel Websockets, as u/phoogkamer suggested, you can host your own websockets server on your infrastructure.

Laravel Websockets

I'm using beyondcode/laravel-websockets with laravel/echo on localhost. Public channels work fine, I also tested private channels by giving productId manually and it works.

https://github.com/beyondcode/laravel-websockets is an OSS Pusher implementation. /u/serenityphp

debugbar And n+1 query

tldr using debugbar is a good point, everything else is just use laravel when using laravel and avoid n+1 problem

Nice but I can get the same functionality with the debugbar - what makes this better?

We then used platform-specific performance analysis tools to determine which of these endpoints needed the most attention. The highest-traffic sites we needed to optimize used Laravel, a popular PHP framework. We used Laravel Debugbar to analyze those web apps.

Try installing laravel-debugbar, it will show you which parts of the app are slow (e.g. boot up vs views), which queries are slow, and how many queries run (helpful when you forgot to eager load some models).

I wanted to tweak Laravel Debugbar, so it could also work with any JSON API, but I ended up writing a minimal package of my own to do the trick.