Laravel or NestJS for a new backend
PHP or Node for a greenfield service: what each ecosystem gives you for free, where hosting and hiring differ, and the conditions that actually decide it.
$ full-stack engineer · India / remote
I'm Sandeep. I work on backend performance, caching, technical SEO and AI features on LLM APIs, and I write up what I learn along the way.
// writing
PHP or Node for a greenfield service: what each ecosystem gives you for free, where hosting and hiring differ, and the conditions that actually decide it.
The slowest Laravel pages are usually one loop issuing a query per row. How to make N+1 visible, fix it with eager loading, and stop it coming back.
Cache::remember is the easy part. Stampedes, tags, TTL jitter, locks and what actually belongs in the cache on a busy Laravel application.
A queued job will run twice and fail at the worst time. Configuring tries and backoff, making jobs safe to retry, and reading the failed_jobs table before users do.
Dropping a hosted CMS for files in the repo: exporting the content, converting rich text, keeping every URL alive, and verifying nothing was lost.
// focus
01
Caching, query and payload work on platforms where a slow page costs real traffic — measured before and after, never guessed.
02
Crawlability, canonicals, structured data and Core Web Vitals treated as engineering problems, built in from the first commit.
03
Claude API work with typed, validated output: structured extraction and classification that holds up outside a demo.
// stack
$ mail sandeep
If a post here helped, or you're stuck on something in the same territory — performance, caching, technical SEO, AI features — I'm happy to talk it through.