Timothy256 @Timothy_codes

Every time you tap “Transfer” on your banking app, something wild happens in the background. Millions of people are doing the same thing, at the same time. Yet the money moves, balances update, and nothing breaks. Here’s how banks actually pull this off.

A skilled SQL engineer can build almost an entire backend inside the DB. That’s why some backend engineers see application code as merely a transport layer. PostgreSQL alone is practically an application platform now. When you build your logics in the DB, you are optimizing for: 1. data integrity 2. transactional consistency 3. performance 4. security This approach is good for banking and financial applications.

Visa has an offline chip protocol. M-Pesa works without internet. Modern fintech wallets process payments with zero connectivity. They're all building variations of the same architecture. Here's how offline payment systems are actually built.

Underrated Laravel feature 🚀 URI templates in the HTTP client are criminally slept on. Stop concatenating strings like it's 2012. Clean. Readable. No bugs hiding in string spaghetti. Small feature. Big upgrade. 🔥

Your Ratelimiting logic works until someone fires 100 concurrent requests on an endpoint that should be limited to 5 requests per minute🫠 The fix: Ensure you/your agents also check the incremented count returned by RateLimiter::hit() and that it doesn't exceed the max attempts.

If you’re using Spatie’s Activity Log to capture changes to models, you can easily miss attribution of model changes to a user who dispatched a job from an authenticated request. This is of course because the job is executed outside the HTTP request lifecycle To resolve this across all your jobs, you can add a causedBy property to a base queued job class, then set it using a listener on the JobQueueing event -- effectively capturing the authenticated user into all your queued jobs (if there is one) Then, when the job is unserialized from the queue, you can restore the causer captured within, effectively attributing model changes that occurred within it to the authenticated user who caused the dispatch of the job

keyboard_arrow_left Previous keyboard_arrow_right Next

@Alphapharmacist @DrSerunjogiEmma @grok Dr has several startups but the one personally have use is Videmak Research AI: An academic software tool designed for researchers to automate literature reviews, proposals, and citation management. $5 per month atleast the last time i used it

This Livewire RCE (>=3; < 3.6.4) is now actively being abused with an exploit available; securityonline.info/critical-flaw-… Hearing reports of: - new php files in public folder with backdoors - perl scripts active processes - weird jobs in the queue Check your version and update!

Barry vd. Heuvel @barryvdh

a year ago

Don't forget to update Livewire 3 as soon as possible! Not sure what the issue is exactly, but you probably want to have this security update live before it's public knowledge; github.com/advisories/GHS…

0 2 15 36K 1

🛠️ How to measure performance in Laravel There are some pretty simple tools you can start measuring your app's performance with: - ab - jmeter - Inspector - Telescope 🧵 Keep Reading

When our APIs need to return a big JSON and pagination is not an option, we can stream the JSON while it gets generated 🏄 This technique alleviates the server load and lets the client handle the stream instead of the whole response 🍃 @laravelnews #laravel #php

ever wondered what actually happens as your app grows from 10 users to 10,000? it’s not just about spinning up beefier servers. the real journey is all about evolving your system design. one painful bottleneck at a time. you start with a single API and database, and life is simple. but quickly, slow user requests crop up when someone uploads a giant video and the server's tied up transcoding. enter background jobs. still, even with a job queue running alongside your API, you’ll eventually have to split them up-dedicate servers just for workers, others for the API. at every step, you’re fighting new resource battles: a worker hogs CPU, an API runs low on memory, and suddenly, the next user to hit your site gets lag. scaling up means horizontal scaling. instead of one monster server, you add more small ones. load balancing requests, worrying about things you never considered before, like what happens if a user uploads a file to one server and then tries to access it from another. suddenly, you’re in the world of stateless services, object storage, cache strategies, distributed queues, and databases with replica followers. each phase brings new complexity, but also a ton of power. it’s a rite of passage for anyone who wants to build something that lasts longer than a side project. nobody tells you how non-linear this all is-it’s a messy, iterative process, and the only real constant is change. the main takeaway: design and scale your system in phases. don't start with microservices just because Netflix told you so. you're not Netflix. my new book, System Design with Laravel will be available on the 9th of September.

18/ Thank you if you're still here! I geek out on performance optimization so you don't have to. If your app needs a speed boost, my team and I have your back. Drop a DM and let's talk!

@vishal_viitor Is it by coincidence waking up to this post just when i slept thinking about optimization strategies for my current application which has large datasets for most of the key lists🤔🤔🤔Thanks a bunch

This is the tech stack I use to ship nonstop as an indie hacker in 2026 🖥️ Frontend – Next.js – Tailwind – Shadcn ⚙️ Backend – Next.js 🔐 Authentication – Auth.js 🗄️ Database – Postgres – Redis 💳 Payments – Polar 🤖 AI Coding – Claude Code ✉️ Emails – Resend ☁️ Hosting – Hetzner VPS – Coolify 🗂️ File Storage – Hetzner S3 📊 Analytics – Datafast

𝗟𝗮𝗿𝗮𝘃𝗲𝗹 𝗿𝘂𝗹𝗲𝘀 𝗖𝗧𝗢𝘀 𝗺𝘂𝘀𝘁 𝗲𝗻𝗳𝗼𝗿𝗰𝗲 𝗯𝘆 𝗱𝗲𝗳𝗮𝘂𝗹𝘁 Laravel moves fast. That’s exactly why it needs rules. If you don’t set these early, you’ll enforce them later — under pressure. Here are the Laravel rules every CTO should make non-negotiable 👇 𝟭. 𝗡𝗼 𝘂𝗻𝗰𝗼𝗻𝘁𝗿𝗼𝗹𝗹𝗲𝗱 𝗱𝗮𝘁𝗮 𝗳𝗲𝘁𝗰𝗵𝗶𝗻𝗴 If a query returns “everything,” it’s a bug. Large datasets must always be constrained, paginated, or streamed. 𝟮. 𝗥𝗲𝗹𝗮𝘁𝗶𝗼𝗻𝘀𝗵𝗶𝗽𝘀 𝗺𝘂𝘀𝘁 𝗯𝗲 𝗶𝗻𝘁𝗲𝗻𝘁𝗶𝗼𝗻𝗮𝗹 Lazy loading is never accidental at scale. If relationships are accessed, they must be planned and reviewed. 𝟯. 𝗜𝗻𝗱𝗲𝘅𝗶𝗻𝗴 𝗶𝘀 𝗽𝗮𝗿𝘁 𝗼𝗳 𝗳𝗲𝗮𝘁𝘂𝗿𝗲 𝗱𝗲𝗹𝗶𝘃𝗲𝗿𝘆 Any new filter, lookup, or foreign reference ships with an index — not as a follow-up task. 𝟰. 𝗥𝗲𝗾𝘂𝗲𝘀𝘁 𝗰𝘆𝗰𝗹𝗲𝘀 𝘀𝘁𝗮𝘆 𝗹𝗶𝗴𝗵𝘁𝘄𝗲𝗶𝗴𝗵𝘁 Anything slow, repeatable, or failure-prone runs outside the user request. Queues aren’t optional once traffic exists. 𝟱. 𝗖𝗼𝗹𝗹𝗲𝗰𝘁𝗶𝗼𝗻𝘀 𝗮𝗿𝗲 𝗻𝗼𝘁 𝗮 𝗱𝗮𝘁𝗮 𝗲𝗻𝗴𝗶𝗻𝗲 If logic can be pushed to the database layer, it should be. Memory-heavy collection work is a red flag. 𝟲. 𝗣𝗮𝗴𝗶𝗻𝗮𝘁𝗶𝗼𝗻 𝗶𝘀 𝗺𝗮𝗻𝗱𝗮𝘁𝗼𝗿𝘆 𝗳𝗼𝗿 𝗹𝗶𝘀𝘁𝘀 No exceptions. If a screen can grow, it must paginate from day one. 𝟳. 𝗧𝗵𝗲 𝗱𝗮𝘁𝗮𝗯𝗮𝘀𝗲 𝗶𝘀 𝗻𝗲𝘃𝗲𝗿 𝗮 𝗰𝗮𝗰𝗵𝗲 Repeat reads require a caching strategy. Database load should represent truth, not convenience. 𝟴. 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝗶𝘀 𝗺𝗲𝗮𝘀𝘂𝗿𝗲𝗱, 𝗻𝗼𝘁 𝗮𝘀𝘀𝘂𝗺𝗲𝗱 Query counts, execution time, and memory usage are reviewed regularly — not only during incidents. 𝟵. 𝗘𝗹𝗼𝗾𝘂𝗲𝗻𝘁 𝗰𝗼𝗻𝘃𝗲𝗻𝗶𝗲𝗻𝗰𝗲 𝗶𝘀 𝗮𝘂𝗱𝗶𝘁𝗲𝗱 Accessors, casts, appended attributes, and global scopes are treated as performance-sensitive code. 𝟭𝟬. 𝗦𝗰𝗮𝗹𝗶𝗻𝗴 𝗿𝘂𝗹𝗲𝘀 𝗮𝗿𝗲 𝗱𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝗲𝗱 𝗲𝗮𝗿𝗹𝘆 Every Laravel codebase needs written performance boundaries — before the team doubles. Laravel doesn’t collapse because it’s slow. It collapses because leaders let convenience replace discipline. CTOs don’t need to block speed. They need to protect the system from its own success. That’s how Laravel products survive real growth.

@FrancescoCiull4 @AnthropicAI Claude Sonnet/opus is in its own league. The rest are just trying. 😀

Want to lose money fast? Automatically redirect users based on their Accept-Language header or IP lookup. 👍

🔥 A quick case study of database indexing and some other techniques. Indexing and query optimization are hard, but there are some techniques you can use in almost any application: - Composite indexes - Column orders - Denormalizing columns 🧵 Keep Reading

Some React devs assume you need to npm install a library to get tooltips. Not true! For icon buttons, use a combo of the `title` attribute and screenreader text with @tailwindcss' sr-only class. Gives you a native tooltip for the label while improving a11y

When you're writing code, you need to think about designing systems that are scalable and maintainable. And inefficient software design can lead to issues like scope creep, miscommunication, delays, and so on. In this guide, Soham teaches you Software Design basics along with some helpful best practices to follow. freecodecamp.org/news/learn-sof…