Livewire considerations

Рет қаралды 4,019

Күн бұрын

In this next part of our Livewire series, I want to discuss some concerns.
Previous videos:
- Building a game with PHP and Laravel Livewire: • Building a game with P...
- Extending my Laravel Livewire game, with ONE line of JavaScript: • Extending my Laravel L...
- Learn about how I made my map game: stitcher.io/blog/procedurally...

Пікірлер: 13

@aghitsnidallah7953 Жыл бұрын

I built an app using a full-page Livewire, a pretty big app that has been used in my country, nation-wide. After a year of inspecting, and doing some stress test here and there, I came with a conclusion that Livewire should not be used as a big, whole-app component. Imagine re-rendering more than 400KB worth of data to your browser, every time the user clicks. This is definitely my mistake, deciding to use a stack blindly without knowing how it behaves in the background. I think, the good approach on using Livewire is only when you need an interactive set of component or form, not a whole page. I would really like to see Livewire put a real case of scenario in their documentation page, along with warnings what might could happened if you do a wrong approach.

@JohnRoux Жыл бұрын

This is less a livewire problem and more an architecture problem with your app. Using livewire to handle the server-client comms doesn't mean you should ignore them entirely. You can use any tool badly

@lanrewaju Жыл бұрын

@@JohnRoux sure thing buddy

@phpannotated Жыл бұрын

In case you're wondering: I used Alpine.js as a way to hook into DOM events for my custom implementation, just FYI: alpinejs.dev/

@guramikutivadze Жыл бұрын

In my opinion it's better to render map with js and validate it on save. validation can be done much faster and will be used only one time on save.

@mayanksgajjar Жыл бұрын

I found performance issue with Livewire, when I use Post::with('comments') but due to Livewire nature of converting collection to array/json, it costs N+1 query in getters/setter

@guramikutivadze Жыл бұрын

it's not livewire issue.

@mayanksgajjar Жыл бұрын

@@guramikutivadze how?

@cristianbilu Жыл бұрын

You don't get N+1 queries in Livewire without getting them without using Livewire, if you want us to help you find a root cause please share a gist.

@martinh4982 Жыл бұрын

This happens if you serialize an entire model over the "wire", ie if you have public properties that are Eloquent models. What I tend to do is only store the model's id in a public property. This helps with performance, payload size, and I have more controller over how the model is re-instantiated on subsequent page calls.

@JohnRoux Жыл бұрын

@@martinh4982 Yep, in the same way, you shouln't serialize that whole collection when putting it in a job. Even with things like Laravel doing some magic to help you out a bit

@user-mm9ys6gn2e 11 ай бұрын

Isn't this solved with Livewire 3?

@DanielSpravtsev Жыл бұрын

I think in case of livewire you should pick the right tool for your task: Livewire or Alpinejs. Alpine works great with livewire, so there won’t be any problem if you just pick the right tool 😀