Weave Code
Laravel Wallet Warmup Laravel Package
bavix/laravel-wallet-warmup
A companion package for bavix/laravel-wallet that helps warm up wallet data in Laravel applications. Prepare wallets ahead of use so balance checks and transaction flows avoid cold-start overhead and stay responsive.
At a glance
Frequently asked questions about Laravel Wallet Warmup
- What is bavix/laravel-wallet-warmup used for?
- It is a companion package for bavix/laravel-wallet that pre-computes and caches wallet balance aggregates so reads do not hit the transaction ledger on every request. The goal is to avoid cold-start overhead and keep balance checks and transaction flows responsive. It is a performance sidecar, not a standalone wallet implementation, so you need bavix/laravel-wallet already in the application.
- Does bavix/laravel-wallet-warmup 4.0 require laravel-wallet 12?
- Yes. Version 4.0.0 adds support for laravel-wallet 12, and that dependency alignment is the main functional change in the release. If your application is still on wallet 11 or earlier, this major version does not apply. Plan the wallet upgrade first, then bump warmup to ^4.0.
- Which Laravel and PHP versions does laravel-wallet-warmup 4.0 support?
- The release notes do not spell out the full framework support matrix, so check the composer.json in the 4.0.0 tag for the declared Laravel constraints. The PHPUnit ^11.0 dev dependency signals a PHP 8.2+ toolchain expectation for the package's own tests. Confirm your runtime PHP version against the package's require block before assuming parity.
- How do I install bavix/laravel-wallet-warmup?
- Install it with Composer alongside bavix/laravel-wallet 12, publish the package config with vendor:publish, and schedule the warmup command or job. The setup is low effort in principle, but the real cost is dependency alignment with the wallet 12 line. Rebuild warmup artifacts from scratch after install rather than relying on carried-over cache data.
- How do I schedule the wallet warmup in Laravel?
- The package provides a warmup command or job that you register in your Laravel scheduler so balances are prepared ahead of traffic. Run it often enough to cover your read paths without rebuilding the entire ledger unnecessarily. After any wallet upgrade or config change, trigger a full rebuild rather than an incremental warmup.
- Is laravel-wallet-warmup worth it or premature optimization?
- It is worth it if your application already uses bavix/laravel-wallet and your read volume makes ledger-backed balance checks a bottleneck. For low read volume or simple wallets, it is probably premature optimization that adds a cache to invalidate. Measure balance-read cost first, then adopt warmup only if the cold-start overhead is real.
- How do I upgrade laravel-wallet-warmup from 3.x to 4.0?
- Treat the wallet upgrade as its own change: inventory your current laravel-wallet version, read the wallet 12 upgrade guide, and get wallet 12 stable in staging first. Then bump warmup to ^4.0 and run composer update bavix/laravel-wallet-warmup --with-dependencies. Republish and diff the config, rebuild warmup caches, and verify sampled balances against raw ledger sums. The 3.0.1 to 4.0.0 diff is more reliable than the dependabot-heavy release notes.
- Do I need to rebuild warmup caches after upgrading laravel-wallet?
- Yes. If wallet 12 changes balance calculation or invalidation semantics, previously warmed caches can silently diverge from ledger truth. Rebuild warmup artifacts from scratch after the upgrade and verify a sample of warmed balances against raw ledger sums. Your rollback plan should include cache invalidation, not just a Composer revert, because stale warmed balances can persist after code rollback.
- Can warmup caches show stale or incorrect wallet balances?
- Yes, that is the main technical risk. Warmup caches are pre-computed aggregates, so any change in how laravel-wallet computes or invalidates balances can leave warmed data out of sync. Mitigate with a full rebuild after upgrades, sampled verification against ledger sums, and cache invalidation in rollback procedures.
- Is bavix/laravel-wallet-warmup actively maintained?
- It is a small-maintainer, bus-factor-one project with an automated release pipeline, and the release notes are largely dependabot-driven. That means you should treat the diff and composer.json as the source of truth rather than expecting prose upgrade guides. It is low touch but not zero, so pin ^4.0 explicitly and review changes before upgrading.
Weaver
How can I help you explore Laravel packages today?