[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"site-settings":3,"blog-post:laravel-queues-and-jobs":8,"blog-posts-latest:24":30,"blog-comments:6e45f39b-1ade-47f0-a0b0-b4cd386a10dc":323,"site-content":324},{"id":4,"accent_theme":5,"font_theme":6,"updated_at":7},1,"midnight","saas","2026-10-28T07:05:59.308034+00:00",{"id":9,"title":10,"slug":11,"excerpt":12,"content":13,"cover_image":14,"meta_title":15,"meta_description":16,"og_image":17,"tags":18,"status":24,"published_at":25,"view_count":26,"deleted_at":27,"deleted_reason":28,"created_at":29,"updated_at":29},"6e45f39b-1ade-47f0-a0b0-b4cd386a10dc","Laravel Queues & Jobs: How Background Processing Works","laravel-queues-and-jobs","Laravel queues move slow work off the HTTP request. You push a Job onto a queue, a worker runs it later, and the user gets a fast response. Use them for mail, webhooks, image work, and anything that can fail and retry.","\u003Ch2 id=\"quick-answer\">Quick Answer\u003C\u002Fh2>\n\u003Cp>Laravel queues run work after the HTTP response. You build a Job class, \u003Ccode>dispatch()\u003C\u002Fcode> it, and a worker process pulls it from a driver (database, Redis, SQS). Use this when the request would otherwise wait on mail, image resize, third-party APIs, or anything that can fail and needs a retry. The request stays fast; the job can take its time.\u003C\u002Fp>\n\n\u003Ch2 id=\"quick-facts\">Quick Facts\u003C\u002Fh2>\n\u003Ctable>\n\u003Cthead>\u003Ctr>\u003Cth>Item\u003C\u002Fth>\u003Cth>Details\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\u003Ctd>Topic\u003C\u002Ftd>\u003Ctd>Laravel Queues &amp; Jobs\u003C\u002Ftd>\u003C\u002Ftr>\n\u003Ctr>\u003Ctd>Category\u003C\u002Ftd>\u003Ctd>Laravel \u002F PHP \u002F Background Processing\u003C\u002Ftd>\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\n\u003Cnav class=\"blog-toc\" aria-label=\"Table of contents\">\n\u003Ch2 id=\"table-of-contents\">Table of Contents\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"#what-is-laravel-queues-jobs\">What Is Laravel Queues &amp; Jobs?\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#why-it-matters\">Why It Matters\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#how-it-works\">How It Works\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#step-by-step-guide\">Step-by-Step Guide\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#real-world-example\">Real-World Example\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#pros-cons\">Pros &amp; Cons\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#best-practices\">Best Practices\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#common-mistakes\">Common Mistakes\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#frequently-asked-questions\">FAQs\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"#key-takeaways\">Key Takeaways\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fnav>\n\n\u003Ch2 id=\"what-is-laravel-queues-jobs\">What Is Laravel Queues &amp; Jobs?\u003C\u002Fh2>\n\u003Cp>A Job is a class with a \u003Ccode>handle()\u003C\u002Fcode> method. A queue is the place that Job sits until a worker picks it up. That is it.\u003C\u002Fp>\n\u003Cp>This is not “async PHP magic” inside the same request. The web process serializes the job (or a reference to it), sticks it in a table\u002Flist, and returns. A separate process — \u003Ccode>php artisan queue:work\u003C\u002Fcode> — does the real work later.\u003C\u002Fp>\n\u003Cp>If you have ever returned 200 to the browser and then sent email in the same controller, you already felt the pain queues solve. Mailgun hiccups, SMTP timeouts, 30-second gateway kills. Push it to a job and the HTTP path stays boring.\u003C\u002Fp>\n\n\u003Ch2 id=\"why-it-matters\">Why It Matters\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Users wait on what you do in the request. Resize a cover image inline and the upload form feels broken even when the file landed fine.\u003C\u002Fli>\n\u003Cli>External APIs fail. Queues give you retries and a \u003Ccode>failed_jobs\u003C\u002Fcode> table instead of a half-finished signup with no welcome mail.\u003C\u002Fli>\n\u003Cli>You can scale workers without touching PHP-FPM. More mail backlog? Spin another worker. The web boxes stay the same.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2 id=\"how-it-works\">How It Works\u003C\u002Fh2>\n\u003Cp>Two timelines. Request path: validate, save, dispatch, respond. Worker path: pop job, run \u003Ccode>handle()\u003C\u002Fcode>, ack or fail.\u003C\u002Fp>\n\n\u003Cfigure class=\"blog-figure blog-figure--diagram\" contenteditable=\"false\">\n\u003Cdiv class=\"blog-mermaid\">\n\u003Cpre class=\"mermaid-source\">sequenceDiagram\n  participant Browser\n  participant App as Laravel HTTP\n  participant Q as Queue store\n  participant W as queue:work\n  Browser-&gt;&gt;App: POST \u002Fregister\n  App-&gt;&gt;App: Save user\n  App-&gt;&gt;Q: Push SendWelcomeMail job\n  App--&gt;&gt;Browser: 201 Created (fast)\n  W-&gt;&gt;Q: Reserve next job\n  W-&gt;&gt;W: handle() send mail\n  W-&gt;&gt;Q: Delete job \u002F mark done\u003C\u002Fpre>\n\u003C\u002Fdiv>\n\u003Cfigcaption>HTTP returns before mail finishes. Worker owns the slow part.\u003C\u002Ffigcaption>\n\u003C\u002Ffigure>\n\n\u003Cp>Pieces that actually matter:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Driver\u003C\u002Fstrong> — \u003Ccode>sync\u003C\u002Fcode> runs the job inline (fine for local “does it explode?”). \u003Ccode>database\u003C\u002Fcode> uses a \u003Ccode>jobs\u003C\u002Fcode> table. Redis \u002F SQS for anything with real traffic.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Job class\u003C\u002Fstrong> — implements \u003Ccode>ShouldQueue\u003C\u002Fcode>, holds the payload (ids, not giant models if you can help it), runs \u003Ccode>handle()\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Worker\u003C\u002Fstrong> — long-running CLI. No worker = jobs pile up and nothing happens. That surprise still gets people.\u003C\u002Fli>\n\u003C\u002Fol>\n\n\u003Cfigure class=\"blog-figure blog-figure--diagram\" contenteditable=\"false\">\n\u003Cdiv class=\"blog-mermaid\">\n\u003Cpre class=\"mermaid-source\">flowchart LR\n  D[dispatch Job] --> Store[(jobs table \u002F Redis)]\n  Store --> W[Worker process]\n  W -->|success| Done[Delete \u002F ack]\n  W -->|exception| Retry{Attempts left?}\n  Retry -->|yes| Store\n  Retry -->|no| F[(failed_jobs)]\u003C\u002Fpre>\n\u003C\u002Fdiv>\n\u003Cfigcaption>Happy path deletes the job. Exhausted retries land in failed_jobs for you to inspect.\u003C\u002Ffigcaption>\n\u003C\u002Ffigure>\n\n\u003Cfigure class=\"blog-figure blog-figure--diagram\" contenteditable=\"false\">\n\u003Cdiv class=\"blog-mermaid\">\n\u003Cpre class=\"mermaid-source\">flowchart TB\n  subgraph sync [QUEUE_CONNECTION=sync]\n    S1[dispatch] --> S2[handle runs now]\n    S2 --> S3[Response waits]\n  end\n  subgraph async [database \u002F redis]\n    A1[dispatch] --> A2[Row \u002F payload stored]\n    A2 --> A3[Response returns]\n    A3 --> A4[Worker runs later]\n  end\u003C\u002Fpre>\n\u003C\u002Fdiv>\n\u003Cfigcaption>sync is not a queue. It is “run handle() before you respond.” Useful for debugging. Dangerous in production.\u003C\u002Ffigcaption>\n\u003C\u002Ffigure>\n\n\u003Ch2 id=\"step-by-step-guide\">Step-by-Step Guide\u003C\u002Fh2>\n\n\u003Ch3 id=\"step-1\">Step 1: Create the jobs table and pick a driver\u003C\u002Fh3>\n\u003Cp>If you use the database driver:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">php artisan queue:table\nphp artisan queue:failed-table\nphp artisan migrate\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Ccode>.env\u003C\u002Fcode>:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-env\">QUEUE_CONNECTION=database\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Redis instead? Set \u003Ccode>QUEUE_CONNECTION=redis\u003C\u002Fcode> and make sure the Redis connection in \u003Ccode>config\u002Fdatabase.php\u003C\u002Fcode> actually works. I still start projects on \u003Ccode>database\u003C\u002Fcode> when Redis is not in the stack yet — slower, but one less moving part.\u003C\u002Fp>\n\n\u003Cfigure class=\"blog-figure blog-figure--diagram\" contenteditable=\"false\">\n\u003Cdiv class=\"blog-mermaid\">\n\u003Cpre class=\"mermaid-source\">flowchart LR\n  Env[QUEUE_CONNECTION] --> Sync[sync]\n  Env --> Db[database]\n  Env --> Redis[redis]\n  Env --> Sqs[sqs]\n  Sync --> Local[Local debug]\n  Db --> Small[Small apps \u002F simple deploys]\n  Redis --> Prod[Most production apps]\n  Sqs --> Scale[Multi-server \u002F AWS]\u003C\u002Fpre>\n\u003C\u002Fdiv>\n\u003Cfigcaption>Pick the driver for where you deploy, not what the tutorial used.\u003C\u002Ffigcaption>\n\u003C\u002Ffigure>\n\n\u003Cp>Check: \u003Ccode>jobs\u003C\u002Fcode> and \u003Ccode>failed_jobs\u003C\u002Fcode> tables exist (database driver), or Redis accepts a ping.\u003C\u002Fp>\n\n\u003Ch3 id=\"step-2\">Step 2: Generate a Job and dispatch it\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-bash\">php artisan make:job SendWelcomeMail\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cpre>\u003Ccode class=\"language-php\">namespace App\\Jobs;\n\nuse App\\Models\\User;\nuse App\\Mail\\WelcomeMail;\nuse Illuminate\\Contracts\\Queue\\ShouldQueue;\nuse Illuminate\\Foundation\\Queue\\Queueable;\nuse Illuminate\\Support\\Facades\\Mail;\n\nclass SendWelcomeMail implements ShouldQueue\n{\n    use Queueable;\n\n    public function __construct(public User $user) {}\n\n    public function handle(): void\n    {\n        Mail::to($this-&gt;user-&gt;email)-&gt;send(new WelcomeMail($this-&gt;user));\n    }\n}\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Controller after create:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-php\">SendWelcomeMail::dispatch($user);\n\u002F\u002F or: dispatch(new SendWelcomeMail($user));\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Prefer passing \u003Ccode>$user-&gt;id\u003C\u002Fcode> and reloading inside \u003Ccode>handle()\u003C\u002Fcode> if the model is heavy or might change before the worker runs. Serializing a full Eloquent model works until it does not (missing attributes, stale state, huge relations).\u003C\u002Fp>\n\n\u003Cfigure class=\"blog-figure blog-figure--diagram\" contenteditable=\"false\">\n\u003Cdiv class=\"blog-mermaid\">\n\u003Cpre class=\"mermaid-source\">flowchart TB\n  C[Controller] -->|dispatch user id| Q[(Queue)]\n  Q --> H[handle]\n  H --> Find[User::find id]\n  Find --> Mail[Mail::send]\u003C\u002Fpre>\n\u003C\u002Fdiv>\n\u003Cfigcaption>Ids travel better than fat models. Worker loads a fresh User when it runs.\u003C\u002Ffigcaption>\n\u003C\u002Ffigure>\n\n\u003Cp>Smoke test with \u003Ccode>QUEUE_CONNECTION=sync\u003C\u002Fcode> once so exceptions show up in the request. Then switch back to database\u002Fredis and run a worker.\u003C\u002Fp>\n\n\u003Ch3 id=\"step-3\">Step 3: Run a worker and handle failures\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-bash\">php artisan queue:work --tries=3 --timeout=90\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Production: Supervisor (or Horizon for Redis) so the worker restarts when it dies. Deploy without a worker and your \u003Ccode>jobs\u003C\u002Fcode> table grows while users wonder why mail never arrived.\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-php\">public int $tries = 3;\npublic int $backoff = 30; \u002F\u002F seconds between retries\n\npublic function failed(\\Throwable $e): void\n{\n    \u002F\u002F log, notify, mark signup as \"mail pending\"\n}\u003C\u002Fcode>\u003C\u002Fpre>\n\n\u003Cfigure class=\"blog-figure blog-figure--diagram\" contenteditable=\"false\">\n\u003Cdiv class=\"blog-mermaid\">\n\u003Cpre class=\"mermaid-source\">flowchart LR\n  Fail[Job throws] --> T1[Retry 1 after backoff]\n  T1 --> T2[Retry 2]\n  T2 --> T3[Retry 3]\n  T3 --> FJ[failed_jobs + failed]\n  FJ --> RetryCmd[\"queue:retry id\"]\u003C\u002Fpre>\n\u003C\u002Fdiv>\n\u003Cfigcaption>Retries are automatic. failed() is your hook after the last attempt. queue:retry puts it back when the API is healthy again.\u003C\u002Ffigcaption>\n\u003C\u002Ffigure>\n\n\u003Cp>Watch: \u003Ccode>php artisan queue:failed\u003C\u002Fcode>. Empty after a deliberate bad job means you are still on \u003Ccode>sync\u003C\u002Fcode> or the worker is not running.\u003C\u002Fp>\n\n\u003Ch2 id=\"real-world-example\">Real-World Example\u003C\u002Fh2>\n\u003Cp>Stack: Laravel 11 API, Nuxt signup form. On register we created the user, then sent welcome mail with Mailgun in the same request.\u003C\u002Fp>\n\u003Cp>Local: fine. Staging: fine. Production spike: Mailgun latency jumped, PHP-FPM workers sat on SMTP, Nuxt showed a spinner past 30s, some clients got 504, user row already existed. Support got “I signed up but nothing happened” tickets for accounts that did exist.\u003C\u002Fp>\n\n\u003Cfigure class=\"blog-figure blog-figure--diagram\" contenteditable=\"false\">\n\u003Cdiv class=\"blog-mermaid\">\n\u003Cpre class=\"mermaid-source\">sequenceDiagram\n  participant Nuxt\n  participant API\n  participant Mailgun\n  Nuxt-&gt;&gt;API: POST \u002Fregister\n  API-&gt;&gt;API: INSERT users\n  API-&gt;&gt;Mailgun: Send mail (slow \u002F timeout)\n  Note over Nuxt,API: Gateway 504 — user exists, mail maybe not\n  Nuxt--&gt;&gt;Nuxt: Error UI\u003C\u002Fpre>\n\u003C\u002Fdiv>\n\u003Cfigcaption>Before: mail on the request path. Timeout after the insert is the worst kind of bug.\u003C\u002Ffigcaption>\n\u003C\u002Ffigure>\n\n\u003Cp>Fix was boring on purpose:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-php\">$user = User::create($data);\nSendWelcomeMail::dispatch($user-&gt;id);\nreturn response()-&gt;json(['user' =&gt; $user], 201);\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Worker on the API box via Supervisor. \u003Ccode>$tries = 3\u003C\u002Fcode>, \u003Ccode>$backoff = 60\u003C\u002Fcode>. Mailgun blip? Job retries. Exhausted? Row in \u003Ccode>failed_jobs\u003C\u002Fcode>, Horizon\u002Femail alert, \u003Ccode>queue:retry\u003C\u002Fcode> after the outage.\u003C\u002Fp>\n\n\u003Cfigure class=\"blog-figure blog-figure--diagram\" contenteditable=\"false\">\n\u003Cdiv class=\"blog-mermaid\">\n\u003Cpre class=\"mermaid-source\">sequenceDiagram\n  participant Nuxt\n  participant API\n  participant Q as Queue\n  participant W as Worker\n  participant Mailgun\n  Nuxt-&gt;&gt;API: POST \u002Fregister\n  API-&gt;&gt;API: INSERT users\n  API-&gt;&gt;Q: Push SendWelcomeMail\n  API--&gt;&gt;Nuxt: 201 in ~100ms\n  W-&gt;&gt;Q: Pop job\n  W-&gt;&gt;Mailgun: Send mail\n  alt Mailgun down\n    W-&gt;&gt;Q: Release \u002F retry later\n  end\u003C\u002Fpre>\n\u003C\u002Fdiv>\n\u003Cfigcaption>After: signup returns. Mail is the worker’s problem. Retries do not block the browser.\u003C\u002Ffigcaption>\n\u003C\u002Ffigure>\n\n\u003Cp>Second footgun the same week: \u003Ccode>QUEUE_CONNECTION=sync\u003C\u002Fcode> left on a staging env that “felt like prod.” Jobs ran inline again. Always verify the connection string on the box that is failing.\u003C\u002Fp>\n\n\u003Ch2 id=\"pros-cons\">Pros &amp; Cons\u003C\u002Fh2>\n\u003Ch3>Advantages\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>HTTP stays short. Slow I\u002FO does not own the user’s spinner.\u003C\u002Fli>\n\u003Cli>Retries and \u003Ccode>failed_jobs\u003C\u002Fcode> beat “hope the webhook worked.”\u003C\u002Fli>\n\u003Cli>Workers scale sideways without resizing the web tier for mail volume.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Disadvantages\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Another process to deploy and watch. No worker = silent backlog.\u003C\u002Fli>\n\u003Cli>Jobs are eventually consistent. UI that assumes “mail already sent” will lie.\u003C\u002Fli>\n\u003Cli>\u003Ccode>sync\u003C\u002Fcode> in production hides all of this until traffic hits.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2 id=\"best-practices\">Best Practices\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Dispatch ids (or small DTOs). Reload models in \u003Ccode>handle()\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>Set \u003Ccode>$tries\u003C\u002Fcode>, \u003Ccode>$timeout\u003C\u002Fcode>, and backoff on jobs that talk to the network.\u003C\u002Fli>\n\u003Cli>Idempotent \u003Ccode>handle()\u003C\u002Fcode> when you can — retries will run it again.\u003C\u002Fli>\n\u003Cli>Supervisor or Horizon in production. \u003Ccode>queue:work\u003C\u002Fcode> in a tmux tab is not a plan.\u003C\u002Fli>\n\u003Cli>Keep \u003Ccode>sync\u003C\u002Fcode> for tests\u002Flocal when you want stack traces in the request; never for prod.\u003C\u002Fli>\n\u003Cli>Failed job alerts. A growing \u003Ccode>failed_jobs\u003C\u002Fcode> table nobody reads is how welcome mail dies for a week.\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2 id=\"common-mistakes\">Common Mistakes\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Forgetting the worker. Jobs insert, nothing runs. Start \u003Ccode>queue:work\u003C\u002Fcode> (or Horizon) and confirm the row leaves \u003Ccode>jobs\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>Serializing huge models \u002F uploaded files into the payload. Pass paths or ids; read the file in the worker.\u003C\u002Fli>\n\u003Cli>Leaving \u003Ccode>QUEUE_CONNECTION=sync\u003C\u002Fcode> on a server. Check \u003Ccode>php artisan tinker\u003C\u002Fcode> → \u003Ccode>config('queue.default')\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>No timeout on a job that can hang on HTTP. Worker stuck, queue blocked for that process. Set \u003Ccode>$timeout\u003C\u002Fcode> and \u003Ccode>--timeout\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>Assuming order. Multiple workers do not promise FIFO across all jobs. If order matters, one queue + one worker, or explicit chaining (\u003Ccode>Bus::chain\u003C\u002Fcode>).\u003C\u002Fli>\n\u003C\u002Ful>\n\n\u003Ch2 id=\"frequently-asked-questions\">Frequently Asked Questions\u003C\u002Fh2>\n\u003Ch3 id=\"faq-what-is-laravel-queues-jobs\">What are Laravel queues and jobs?\u003C\u002Fh3>\n\u003Cp>A Job is a unit of work (\u003Ccode>handle()\u003C\u002Fcode>). A queue stores jobs until a worker runs them. Together they move slow or flaky work off the HTTP request so the user gets a quick response.\u003C\u002Fp>\n\u003Ch3 id=\"faq-how-to\">How do I start using Laravel queues?\u003C\u002Fh3>\n\u003Cp>Run the queue migrations (if database driver), set \u003Ccode>QUEUE_CONNECTION\u003C\u002Fcode>, \u003Ccode>make:job\u003C\u002Fcode>, \u003Ccode>dispatch()\u003C\u002Fcode> from your controller, then \u003Ccode>php artisan queue:work\u003C\u002Fcode>. Confirm a job row appears and disappears.\u003C\u002Fp>\n\u003Ch3 id=\"faq-vs\">queue:work vs queue:listen?\u003C\u002Fh3>\n\u003Cp>\u003Ccode>queue:work\u003C\u002Fcode> boots the app once and keeps it warm — use this in production (with restarts on deploy). \u003Ccode>queue:listen\u003C\u002Fcode> reboots every job — slower, sometimes handy in local when you change code a lot. Horizon sits on top of Redis workers with a dashboard.\u003C\u002Fp>\n\u003Ch3 id=\"faq-worth-it\">Are Laravel queues worth it?\u003C\u002Fh3>\n\u003Cp>Yes as soon as a request talks to mail, SMS, image tools, or someone else’s API. For a CRUD form that only writes MySQL, skip them. The cost is ops (worker + monitoring), not the Job class.\u003C\u002Fp>\n\u003Ch3 id=\"faq-database-vs-redis\">Database queue vs Redis?\u003C\u002Fh3>\n\u003Cp>Database: simple, fine for low volume. Redis: faster pop\u002Fpush, better with Horizon and multiple workers. SQS when you want the broker off your app servers. I use database until Redis is already required for cache\u002Fsessions.\u003C\u002Fp>\n\n\u003Ch2 id=\"summary\">Summary\u003C\u002Fh2>\n\u003Cp>Queues split “save the user” from “email the user.” Dispatch a Job, let a worker run \u003Ccode>handle()\u003C\u002Fcode>, retry on failure. \u003Ccode>sync\u003C\u002Fcode> is for debugging. Production needs a real driver and a process manager watching \u003Ccode>queue:work\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>Today: pick one slow thing in your app (welcome mail is the classic), move it to a Job, run a worker, and watch the request time drop in Telescope or your network tab.\u003C\u002Fp>\n\n\u003Ch2 id=\"key-takeaways\">Key Takeaways\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Laravel jobs are background units of work; the queue is where they wait.\u003C\u002Fli>\n\u003Cli>HTTP dispatches and returns; \u003Ccode>queue:work\u003C\u002Fcode> (or Horizon) actually runs \u003Ccode>handle()\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Ccode>sync\u003C\u002Fcode> runs inline — not production queueing.\u003C\u002Fli>\n\u003Cli>Retries + \u003Ccode>failed_jobs\u003C\u002Fcode> beat silent mail failures on the request path.\u003C\u002Fli>\n\u003Cli>No running worker means a growing backlog and confused users.\u003C\u002Fli>\n\u003C\u002Ful>","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1787286979145-0i7ewp.webp","Laravel Queues & Jobs Explained","How Laravel queues and jobs work: dispatch, workers, retries, failed_jobs, and sync vs database\u002FRedis. Diagrams plus a real mail-timeout fix.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fog\u002F1787287010552-amv4rf.webp",[19,20,21,22,23],"Laravel","Queues","Jobs","PHP","backend","published","2026-08-21T04:36:56.222+00:00",20,null,"","2026-08-21T04:36:56.606735+00:00",[31,46,63,79,93,107,119,131,133,146,157,168,180,193,207,218,229,238,249,263,275,284,295,308],{"id":32,"title":33,"slug":34,"excerpt":35,"cover_image":36,"tags":37,"published_at":43,"updated_at":44,"view_count":45},"1fac09f2-990e-4ebf-99b1-0cc532e7cb08","Soft Delete Inventory Bug — Phantom Serial Stock After Purchase Delete","soft-delete-inventory-bug-phantom-serial-stock-after-purchase-delete","Soft-deleting a purchase looked fine until serial-tracked products stayed sellable. The movement ran, quantity didn’t move, and serials were never detached.","https:\u002F\u002Fik.imagekit.io\u002F93se7t7h4e\u002Fportfolio\u002Fposts\u002Fblog\u002Fcovers\u002F1793165769172-Phantom-Inventory_-Deleted-Warehouse-Order_Z0BIZdhyJ.webp",[38,39,40,41,42,6],"laravel","inventory","soft-delete","serial-numbers","stock-movements","2026-10-28T05:36:31.148+00:00","2026-10-28T05:36:32.188948+00:00",21,{"id":47,"title":48,"slug":49,"excerpt":50,"cover_image":51,"tags":52,"published_at":60,"updated_at":61,"view_count":62},"b2a6b718-c6e5-42fa-9358-22e84035aaf2","Multi-Tenant Inventory Manager with Nuxt 3 and Supabase","multi-tenant-inventory-manager-nuxt-supabase","A shop-billing SaaS on Nuxt 3 and Supabase: stock, invoices, UPI links, AI bill scan, and per-shop storefronts — with RLS so shop_id is never trusted from the client.","https:\u002F\u002Fik.imagekit.io\u002F93se7t7h4e\u002Fportfolio\u002Fposts\u002Flibrary\u002F1792583563566-Modern-Retail-POS-Dashboard-Network_-BFGj_TT0.webp?updatedAt=1792583565092",[53,54,55,39,6,56,57,58,59],"nuxt","supabase","multi-tenancy","vue","pinia","vuetify","ai","2026-10-21T12:07:58.857+00:00","2026-10-21T12:07:59.070373+00:00",16,{"id":64,"title":65,"slug":66,"excerpt":67,"cover_image":68,"tags":69,"published_at":76,"updated_at":77,"view_count":78},"58f0adc6-f4e9-4501-bc0e-ab83cc2cc073","Laravel Sanctum 419 Fix — Why XSRF-TOKEN Must Stay Encrypted","laravel-sanctum-419-xsrf-token-encryption","Sanctum SPA login kept returning 419 CSRF token mismatch. The bug wasn’t domains or cookies “not sticking” — it was excluding XSRF-TOKEN from EncryptCookies while Laravel decrypts the X-XSRF-TOKEN header.","https:\u002F\u002Fik.imagekit.io\u002F93se7t7h4e\u002Fportfolio\u002Fposts\u002Fblog\u002Fcovers\u002F1792229994752-From-CSRF-Error-to-Secure-Fix_FIVIW5po2.webp",[19,70,71,72,73,74,75],"Sanctum","CSRF","419","SPA","Nuxt","API Authentication","2026-10-17T09:40:04.212+00:00","2026-10-17T09:40:06.051151+00:00",17,{"id":80,"title":81,"slug":82,"excerpt":83,"cover_image":84,"tags":85,"published_at":90,"updated_at":91,"view_count":92},"7b4bee90-b35b-4ced-ae8c-0a71e7d968fb","ImageKit Nuxt Upload — Keep Private Keys Off the Client","imagekit-nuxt-upload-secure","ImageKit Nuxt upload means the browser never sees your private key. Sign or upload on the server, return a CDN URL, and store that URL in your CMS or database.","https:\u002F\u002Fik.imagekit.io\u002F93se7t7h4e\u002Fportfolio\u002Fposts\u002Fblog\u002Fcovers\u002F1792216420019-Secure-Upload-Architecture-Flow_MGyvtL5tR.webp",[74,86,87,88,89],"ImageKit","Vue","TypeScript","SEO","2026-10-17T05:55:24.556+00:00","2026-10-17T05:55:24.735773+00:00",23,{"id":94,"title":95,"slug":96,"excerpt":97,"cover_image":98,"tags":99,"published_at":105,"updated_at":106,"view_count":62},"bd55b3c6-8bd3-447d-99ad-d46a97490d7b","Apache 2 Installation on Ubuntu: Step-by-Step","apache-2-installation-ubuntu","Install Apache 2 on Ubuntu with apt, start the service, open the firewall, and verify the default page. Part 2 of the Apache 2 series — clean setup before virtual hosts.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1788925690969-7zm2c2.webp",[100,101,102,103,104],"Apache","Ubuntu","Installation","Linux","Web Server","2026-09-09T03:49:25.809+00:00","2026-09-09T03:49:26.679843+00:00",{"id":108,"title":109,"slug":110,"excerpt":111,"cover_image":112,"tags":113,"published_at":116,"updated_at":117,"view_count":118},"8c75a723-b1a7-4fab-9bb9-71a111c9d4f8","Apache vs Nginx: What They Are and When to Use Each","apache-vs-nginx","Apache and Nginx are web servers. They take HTTP requests and return files or pass work to PHP, Node, or another app. Apache fits shared hosting and .htaccess; Nginx is the usual reverse proxy on an Ubuntu VPS.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1788524039845-wrez6s.webp",[100,114,101,104,103,115],"Nginx","DevOps","2026-09-04T12:14:08.218+00:00","2026-09-04T12:14:08.430018+00:00",9,{"id":120,"title":121,"slug":122,"excerpt":123,"cover_image":124,"tags":125,"published_at":128,"updated_at":129,"view_count":130},"40dd3304-99d2-4948-b8c1-44625f1f4306","What Is a Virtual Host? Host Multiple Sites on One Ubuntu VPS","virtual-host-linux-multiple-websites","A virtual host maps each domain to its own folder on one server. Developers use this on Ubuntu VPSes so portfolio, API, and staging share one bill. Same idea on any Linux — Ubuntu is just what most tutorials and clouds default to.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1788523755345-javhet.webp",[126,101,114,103,127,115],"Virtual Host","VPS","2026-09-04T12:09:22.623+00:00","2026-09-04T12:09:22.931401+00:00",12,{"id":9,"title":10,"slug":11,"excerpt":12,"cover_image":14,"tags":132,"published_at":25,"updated_at":29,"view_count":26},[19,20,21,22,23],{"id":134,"title":135,"slug":136,"excerpt":137,"cover_image":138,"tags":139,"published_at":143,"updated_at":144,"view_count":145},"938c7bd9-2cf3-4a81-8dae-cf88c09e64ca","Laravel N+1 Query Problem: How to Detect and Fix It","laravel-n-plus-1-query-problem","The Laravel N+1 query problem is when one listing query is followed by one extra query per row. You spot it in Telescope or the query log, then fix it with with(), withCount(), and nested eager loads.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1787199419649-niq9k8.webp",[19,140,141,142,22],"Eloquent","N+1","performance","2026-08-20T04:17:43.609+00:00","2026-08-20T05:50:24.297698+00:00",14,{"id":147,"title":148,"slug":149,"excerpt":150,"cover_image":151,"tags":152,"published_at":154,"updated_at":155,"view_count":156},"76717847-4080-4ae6-a2d8-b35badc46be3","Laravel Eloquent Relationships","laravel-eloquent-relationships","Laravel Eloquent relationships map how models connect — hasMany, belongsTo, belongsToMany, and more. Define them once, then load related rows with with() instead of stuffing joins into every query.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1787122982331-16979e.webp",[19,140,22,153,23],"ORM","2026-08-19T07:03:17.721+00:00","2026-08-20T04:19:08.829027+00:00",18,{"id":158,"title":159,"slug":160,"excerpt":161,"cover_image":162,"tags":163,"published_at":166,"updated_at":167,"view_count":62},"6bbe0ad8-0c6d-4172-b279-ded8e2ca9416","Laravel Database Transactions: When and Why to Use DB::transaction()","laravel-database-transactions","DB::transaction() runs a closure inside a SQL transaction: Laravel commits if it finishes, and rolls back if it throws. Use it when one action writes more than one row and a half-finished write would leave bad data.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1787114417893-hp3hmc.webp",[19,164,140,22,165],"Database","Transactions","2026-08-19T04:44:00.327+00:00","2026-08-19T05:14:18.190197+00:00",{"id":169,"title":170,"slug":171,"excerpt":172,"cover_image":173,"tags":174,"published_at":178,"updated_at":179,"view_count":145},"d1020b7b-b410-414f-9ceb-eb0501bc905e","Laravel Auditing Package — Track Model Changes the Right Way","laravel-auditing-package","The Laravel auditing package records old and new model values, the user who changed them, and when it happened—without you inventing a second history table for every feature.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1786778101029-mwb9sf.webp",[19,175,22,176,177],"Auditing","Security","Activity Log","2026-08-15T21:24:32.135+00:00","2026-08-15T21:24:32.194447+00:00",{"id":181,"title":182,"slug":183,"excerpt":184,"cover_image":185,"tags":186,"published_at":190,"updated_at":191,"view_count":192},"3d5eb867-6288-48c4-af04-8b7ece8b874e","Laravel Lifecycle — How a Request Becomes a Response","laravel-lifecycle","The Laravel lifecycle is the path from HTTP request to response: bootstrap, service providers, middleware, routing, then the controller. Know that path and most “random” bugs stop being random.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1786777544862-khxf92.webp",[19,22,187,188,189],"Request Lifecycle","Middleware","Backend","2026-08-15T07:15:13.877+00:00","2026-08-15T07:15:13.978037+00:00",11,{"id":194,"title":195,"slug":196,"excerpt":197,"cover_image":198,"tags":199,"published_at":205,"updated_at":206,"view_count":145},"2ab5e08a-7117-43c5-87eb-0789a2fd3af4","Claude Code Best Practices for Large Codebases — Scope Before You Ship","claude-code-best-practices-large-codebases","On a big repo, Claude Code only helps if you lock rules in CLAUDE.md, scope every ticket, plan multi-file edits, and review the diff like a PR.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1786178453897-dulbmv.webp",[200,201,202,203,204],"claude-code","ai-coding","large-codebases","monorepo","developer-tools","2026-08-08T08:41:03.571+00:00","2026-08-08T08:41:03.839922+00:00",{"id":208,"title":209,"slug":210,"excerpt":211,"cover_image":212,"tags":213,"published_at":216,"updated_at":217,"view_count":156},"ddd55ce1-48fd-40b4-ae91-48a6bec20a2a","Nuxt Middleware Explained — Auth, Redirects & Route Guards Deep Dive","nuxt-middleware-explained","Nuxt middleware runs before a page loads so you can check auth, redirect users, or block a route — on the server for the first hit and in the browser on later navigations.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785902953511-osy6pt.webp",[74,188,214,215,87],"SSR","Auth","2026-08-05T04:09:38.347+00:00","2026-08-05T04:09:38.496803+00:00",{"id":219,"title":220,"slug":221,"excerpt":222,"cover_image":223,"tags":224,"published_at":227,"updated_at":228,"view_count":130},"e0d9941b-467d-45cc-bf12-45390cf9aeaa","Nuxt Lifecycle Explained — Server, Client & Hooks Made Simple","nuxt-lifecycle-explained","Nuxt lifecycle is the order your app boots, fetches data, renders HTML on the server, hydrates in the browser, then runs page navigation — so you know where to put code safely.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785901639981-9tgcl5.webp",[74,87,214,225,226],"Lifecycle","JavaScript","2026-08-05T03:54:08.301+00:00","2026-08-05T03:54:08.919676+00:00",{"id":230,"title":231,"slug":232,"excerpt":233,"cover_image":234,"tags":235,"published_at":236,"updated_at":237,"view_count":92},"23c9cf92-232b-460f-9825-a9c53e350600","How to Use Laravel Sanctum for API Authentication — SPA Cookies & Tokens","laravel-api-authentication","Laravel Sanctum authenticates first-party SPAs with secure cookies and issues API tokens for mobile or third-party clients—without the complexity of full OAuth.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785833713437-wcqb6c.webp",[19,70,75,22,73,176],"2026-08-04T08:56:17.304+00:00","2026-08-06T04:07:09.059636+00:00",{"id":239,"title":240,"slug":241,"excerpt":242,"cover_image":243,"tags":244,"published_at":247,"updated_at":248,"view_count":156},"f50b774a-c745-41aa-a3b0-72ac1f5b7117","Laravel Sanctum vs Passport — Which API Auth Should You Use?","laravel-sanctum-vs-passport","Laravel Sanctum is the lighter choice for SPAs and simple API tokens; Passport is full OAuth2 for third-party apps. Pick Sanctum for most apps, Passport when you need real OAuth2.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785817155174-054d6s.webp",[19,70,245,75,22,246,73],"Passport","OAuth2","2026-08-04T04:19:37.286+00:00","2026-08-04T04:49:08.25034+00:00",{"id":250,"title":251,"slug":252,"excerpt":253,"cover_image":254,"tags":255,"published_at":260,"updated_at":261,"view_count":262},"ef36ca16-73ab-4f9a-9584-ff70a60da5f5","Laravel vs NestJS in 2026: Which Backend Should US Startups Choose?","laravel-vs-nestjs-2026-us-startups","Laravel vs NestJS for US startups in 2026: compare speed, TypeScript, hiring, SaaS MVPs, and real-time apps — and pick the backend that matches your team.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785609396341-ungcby.jpg",[19,256,189,257,258,22,88,259],"NestJS","SaaS","Startups","Web Development","2026-08-01T18:40:05.071+00:00","2026-08-01T18:40:05.261242+00:00",38,{"id":264,"title":265,"slug":266,"excerpt":267,"cover_image":268,"tags":269,"published_at":273,"updated_at":274,"view_count":130},"c4e41758-834c-476e-8830-f776c963a784","What Is TypeScript? A Beginner’s Guide to Safer JavaScript","what-is-typescript","TypeScript is JavaScript with types. Learn what it is, how it works, and how to write your first typed script with clear examples and FAQs.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785574204088-8bc8es.jpg",[88,226,259,270,271,272],"Programming","Beginners","Frontend","2026-08-01T08:50:45.861+00:00","2026-08-01T08:50:45.958378+00:00",{"id":276,"title":277,"slug":278,"excerpt":279,"cover_image":280,"tags":281,"published_at":282,"updated_at":283,"view_count":145},"37ee32f1-7b8d-4c4d-92b4-37bb37ff64c5","What Is JavaScript? A Beginner’s Guide to Modern Web Development","what-is-javascript","JavaScript is the programming language that makes websites interactive. Learn what it is, how it works, and how to write your first script with clear examples and FAQs.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785561346515-utrr91.jpg",[226,259,270,271,272],"2026-08-01T05:16:12.728+00:00","2026-08-01T08:50:11.164531+00:00",{"id":285,"title":286,"slug":287,"excerpt":288,"cover_image":289,"tags":290,"published_at":293,"updated_at":294,"view_count":156},"f238da13-8416-41e6-8281-a6185efd4bd4","Laravel Sanctum Explained: Simple API Authentication for Modern Apps","laravel-sanctum-api-authentication","Laravel Sanctum makes API authentication simple — whether you need token-based APIs for mobile apps or cookie-based auth for SPAs. Here’s how it works, without the jargon.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785470074981-vejfi4.jpg",[19,70,291,292,73],"API","Authentication","2026-08-01T04:13:15.178+00:00","2026-08-01T08:50:11.393519+00:00",{"id":296,"title":297,"slug":298,"excerpt":299,"cover_image":300,"tags":301,"published_at":305,"updated_at":306,"view_count":307},"d8c77913-46f4-4012-ade6-bd5a81676001","Laravel Module Structure Explained: Keep Large Apps Clean","laravel-module-structure-explained","A practical guide to Laravel module architecture — folder layout, providers, routes, and boundaries that keep features independent as your app grows.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785385385865-8oyk12.png",[19,22,302,303,189,304],"Modules","Architecture","Clean Code","2026-07-30T04:54:17.431+00:00","2026-08-01T08:50:11.599795+00:00",6,{"id":309,"title":310,"slug":311,"excerpt":312,"cover_image":313,"tags":314,"published_at":321,"updated_at":322,"view_count":26},"26ccd19c-a8bb-419d-be11-efd1d221b415","Cursor vs Claude vs ChatGPT: Which AI Actually Helps with Laravel & Nuxt?","cursor-ai-vs-claude-code-vs-chatgpt-for-laravel-nuxt-development-2026","Tired of constantly copying and pasting code between your Vue frontend and PHP backend? I tested Cursor, Claude Code, and ChatGPT to see which one actually speeds up a real-world Laravel and Nuxt workflow. Here is my breakdown.","https:\u002F\u002Fkjnzswhfjfkhvplczgfs.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fimages\u002Fblog\u002Fcovers\u002F1785300697566-pn766r.png",[19,315,316,317,318,319,320],"Nuxt 3","AI for Developers","Cursor","Claude Code","ChatGPT","Full Stack","2026-07-29T04:46:50.88+00:00","2026-08-01T08:50:11.809909+00:00",[],{"variant":325,"profile":330,"heroStats":343,"aboutParagraphs":347,"aboutPillars":354,"aboutFacts":367,"skillCategories":380,"experiences":419,"education":446,"projects":465,"languages":535,"interests":538},{"id":326,"slug":327,"label":328,"is_active":329,"sort_order":4},"481b2725-e0f6-43df-beea-937ec806a438","full-stack-developer","Full Stack Developer",true,{"name":331,"title":332,"tagline":332,"photo_url":333,"summary":334,"email":335,"phone":28,"location":336,"linkedin":337,"github":338,"instagram":339,"hero_headline":340,"hero_headline_accent":341,"hero_subheadline":342},"Mohd Anish","Full Stack Developer ","\u002Fprofile.png","Full Stack Developer with 3.5+ years of experience specializing in Laravel, Vue.js, Nuxt.js, MySQL, and modern web technologies. Experienced in designing, developing, and maintaining scalable web applications with a strong focus on performance, security, and code quality.","anhali736@gmail.com","Rajasthan, India","linkedin.com\u002Fin\u002Fmohd-anish-23096635a","https:\u002F\u002Fgithub.com\u002Fmrmolani76","https:\u002F\u002Fwww.instagram.com\u002Fmohdanish.me\u002F","Building Scalable Web Apps","using Modern Technologies","Building secure, scalable, and high-performance web applications using Laravel, Vue.js, Nuxt.js, and MySQL.",[344],{"value":345,"label":346},"3.5+","Yrs Development",[348,350,352],{"html":349},"I'm a \u003Cspan class=\"text-gold font-medium\">Full Stack Developer\u003C\u002Fspan> passionate about building secure, scalable, and high-performance web applications. I enjoy solving complex problems and creating modern digital experiences with clean, maintainable code.",{"html":351},"I specialize in \u003Cspan class=\"text-gold font-medium\">Laravel\u003C\u002Fspan>, \u003Cspan class=\"text-foreground\">Vue.js\u003C\u002Fspan>, \u003Cspan class=\"text-foreground\">Nuxt.js\u003C\u002Fspan>, \u003Cspan class=\"text-foreground\">MySQL\u003C\u002Fspan>, and \u003Cspan class=\"text-foreground\">REST APIs\u003C\u002Fspan>, building responsive and scalable applications with a strong focus on performance, security, and code quality.",{"html":353},"With \u003Cspan class=\"text-foreground\">3.5+ years of experience\u003C\u002Fspan>, I've contributed to enterprise-grade applications, including compliance-critical modules for the \u003Cspan class=\"text-foreground\">Complere eQMS\u003C\u002Fspan> platform. I'm committed to continuous learning and building software that is reliable, maintainable, and ready for real-world use.",[355,359,363],{"icon":356,"label":357,"description":358},"lucide:code-2","Build","Scalable, clean web apps",{"icon":360,"label":361,"description":362},"lucide:trending-up","Grow","Marketing-driven results",{"icon":364,"label":365,"description":366},"lucide:shield-check","Ship","Reliable, compliant systems",[368,372,376],{"icon":369,"label":370,"value":371},"lucide:settings","Core Stack","Laravel · Nuxt · Vue · MySQL",{"icon":373,"label":374,"value":375},"lucide:building-2","Currently","Complibued — eQMS Platform",{"icon":377,"label":378,"value":379},"lucide:map-pin","Availability","Open to opportunities",[381,394,403,414],{"title":382,"icon":383,"color":384,"show_on_home":329,"show_on_resume":329,"skills":385},"Backend Development","lucide:database","from-gold-soft to-gold-deep",[19,22,386,387,388,389,390,391,392,393],"Supabase (BaaS)","MySQL","REST APIs","Git","Docker","Redis","GitHub Actions","Cloudflare",{"title":395,"icon":396,"color":384,"show_on_home":329,"show_on_resume":397,"skills":398},"Frontend Development","lucide:code",false,[399,400,401,88,402,226],"Nuxt.js","Vue.js","React","Tailwind CSS",{"title":404,"icon":405,"color":384,"show_on_home":329,"show_on_resume":397,"skills":406},"AI & Automation","lucide:zap",[407,408,409,410,411,412,413],"Prompt Engineering","ChatGPT & Claude","Google Gemini","AI Grok","GitHub Copilot","AI Content Strategy","Workflow Automation",{"title":415,"icon":416,"color":384,"show_on_home":329,"show_on_resume":329,"skills":417},"Development","lucide:wrench",[19,22,400,399,226,88,402,388,387,418],"Git & GitHub",[420],{"role":328,"company":421,"note":422,"period":423,"description":424,"stack":425,"color":384,"icon":426,"points":427},"Complibued","Complere eQMS — Pharmaceutical SaaS","2023 – Present","Building Complere eQMS, a cloud-based Quality Management System for regulated life sciences using Laravel and Nuxt.js. Developed compliance-critical modules — Document Control, LMS, Events, CAPA, Change Control, Audit, and Risk Assessment.","Laravel · Vue\u002FNuxt · MySQL · Tailwind CSS","lucide:folder-git-2",[428,431,433,435,437,440,442,444],{"text":429,"surface":430},"Developing and maintaining a pharma-focused eQMS platform using Laravel and Nuxt.js.","resume",{"text":432,"surface":430},"Built compliance-critical modules: Document Control, Training (LMS), Event Handling, CAPA, Change Control (CR), Audit, and Risk Assessment (RA).",{"text":434,"surface":430},"Implemented approval workflows, version control, and immutable audit trails aligned to 21 CFR Part 11.",{"text":436,"surface":430},"Collaborated with QA teams to meet pharmaceutical compliance standards.",{"text":438,"surface":439},"Built Document Control & LMS (training) modules","home",{"text":441,"surface":439},"Implemented CAPA and Event management workflows",{"text":443,"surface":439},"Developed Change Control (CR) with impact-assessed approvals",{"text":445,"surface":439},"Delivered Audit & Risk Assessment (RA) modules with audit trails",[447,452,456,461],{"degree":448,"school":449,"period":450,"score":451},"M.Sc. (Computer Science)","MDS University, Ajmer","2023 – 2025","73%",{"degree":453,"school":449,"period":454,"score":455},"BCA","2020 – 2023","71%",{"degree":457,"school":458,"period":459,"score":460},"Senior Secondary (12th)","RBSE, Ajmer","2018 – 2019","68.80%",{"degree":462,"school":458,"period":463,"score":464},"Secondary (10th)","2016 – 2017","48.75%",[466,483,500],{"title":467,"slug":468,"description":469,"why":470,"category":471,"image":472,"emoji":473,"link":474,"is_active":329,"stack":475,"features":477,"metrics":482},"Inventory Manager","inventory-manager","Professional inventory management system for tracking stock, orders, and enterprise operations. Powered by Supabase auth and a relational MySQL backend.","Stock and order tracking needed a reliable source of truth for enterprise operations. This system was built so teams can monitor inventory, manage orders, and report status from one authenticated app.","Enterprise","bg-gradient-to-br from-gold-soft\u002F15 via-gold\u002F5 to-transparent","📦","https:\u002F\u002Fruby-enterprise.vercel.app\u002F",[400,476,387,402,88],"Supabase",[478,479,480,481],"Stock Tracking","Order Management","User Authentication","Reporting & Analytics",[],{"title":484,"slug":485,"description":486,"why":487,"category":488,"image":489,"emoji":490,"link":491,"is_active":329,"stack":492,"features":494,"metrics":499},"Random Video Chat","random-video-chat","Omegle-style platform for spontaneous 1-on-1 video conversations with strangers. Uses WebRTC for peer-to-peer video and Supabase Realtime for matchmaking and signaling.","I wanted to explore real-time peer connections without a heavy media server. The app was built to practice WebRTC + realtime matchmaking and deliver instant 1-on-1 video chat with no account friction.","Real-time","bg-gradient-to-br from-gold\u002F15 via-gold\u002F5 to-transparent","🎥","https:\u002F\u002Fomegle-seven-xi.vercel.app\u002F",[400,493,476,402,88],"WebRTC",[495,496,497,498],"Peer-to-Peer Video","Random Matchmaking","Realtime Signaling","No Sign-up Required",[],{"title":501,"slug":502,"description":503,"why":504,"category":505,"image":489,"emoji":506,"link":507,"is_active":329,"stack":508,"features":516,"metrics":525},"Nexro","nexro","Multi-tenant retail web app for GST billing and inventory — products, purchases, sales, POS, quotations, supplier ledgers, and reports. Landing page: nexro.me.","Retail shops were juggling billing, stock, purchases, and supplier dues across sheets and separate tools. Nexro was built as a multi-tenant SaaS so each shop gets its own data on a shared Laravel + Nuxt stack, with GST invoices, live stock, and day-to-day ops from one login.","Web App \u002F SaaS","🏪","https:\u002F\u002Fnexro.me",[509,510,511,512,402,88,387,513,514,515,390],"Laravel 12","Nuxt 4","Vue 3","Vuetify 3","stancl\u002Ftenancy","Laravel Sanctum","Spatie Permission",[517,518,519,520,521,522,523,524],"Multi-tenant shop isolation","GST billing & POS","Inventory with SKU \u002F barcode \u002F serial","Purchases & supplier ledger","Quotations → invoice","Sales, stock & dues reports","Thermal & A4 print","Region-aware landing (nexro.me)",[526,529,532],{"value":527,"label":528},"1","Product platform",{"value":530,"label":531},"7+","Core modules",{"value":533,"label":534},"MT","Multi-tenant",[536,537],"Hindi","English",[259,539,540],"Video Content","New Tools & Tech"]