Blog

Blog

13 articles

Laravel’s AI SDK reached v1. Where should it fit in your application?

Laravel AI SDK v1 adds tool approvals and new conversation storage. Keep authority in the app, treat state as data and plan the upgrade before you deploy.

#AI agents

One application, several businesses, and separate sets of keys

Sharing an app between businesses means following the tenant past the browser: queries, files, caches, queued jobs and notifications, tested with real accounts.

#Architecture

Laravel 13 brings AI closer. Keep your business rules close, too.

Laravel 13 and its AI SDK make AI features easier to add. Give AI one defined job, keep decisions and permissions in your own code and plan for bad days.

#AI

The backup exists. Can you bring the business back from it?

A backup is not a recovery. Set recovery point and time objectives, map what lives outside the database and rehearse bringing a real workflow back.

#Backups

Real-time updates are useful when there is something worth watching

Use polling when a little delay is fine and push when people are waiting. Publish changes after they are accepted and treat reconnection as part of the feature.

#Laravel

If the queue is failing quietly, the business is failing loudly

A portal can look fine while background jobs have stopped. Give every alert an owner and a useful question so failed work never goes unnoticed.

#Alerts

Laravel Cloud: choose hosting for the work after the first deployment

Laravel Cloud simplifies deployment. For a real business app, rehearse queues and schedules, compare the operating model and keep an exit route.

#Deployment

Laravel 12 looks fairly boring. That can be excellent news.

Laravel 12 is a deliberately calm upgrade. Use the breathing room to check dependencies, treat the new starter kits as a starting point and plan support.

#Laravel 12

Inertia 2 gives Laravel portals a useful middle ground

Inertia 2 gives Laravel portals an interactive frontend without a separate API product. When it fits, when an API earns its place and when simple pages win.

#Customer portals

The page can wait a second. The customer should not have to.

Laravel’s deferred functions, Cache::flexible and queues change when work happens. Choose which kind of later a task can safely tolerate.

#Caching

Meal delivery software has a deadline. Dinner is fairly unforgiving.

A paid order can still miss the kitchen. Set clear cutoffs, separate acceptance from notifications and plan recovery when one step in a Laravel order fails.

#Laravel

Laravel 11 got leaner. Your business rules still need a home.

Laravel 11 brought a slimmer app structure and Reverb. A smaller skeleton isn’t an architecture: give each business change one coherent path.

#Architecture

Turn reading into results

Like what you’re reading? Let’s put it to work on your brand.