Nikola Petrovic
@nikolapetrovic.bsky.social
Fullstack Developer
- The more you try, the more you get -
- The more you try, the more you get -
Hot take: adding caching before understanding query patterns is technical debt.
Measure first → fix data access → then cache.
Otherwise you’re just freezing inefficiencies in Redis.
Measure first → fix data access → then cache.
Otherwise you’re just freezing inefficiencies in Redis.
February 10, 2026 at 10:33 AM
Hot take: adding caching before understanding query patterns is technical debt.
Measure first → fix data access → then cache.
Otherwise you’re just freezing inefficiencies in Redis.
Measure first → fix data access → then cache.
Otherwise you’re just freezing inefficiencies in Redis.
Most “slow APIs” I debug aren’t slow because of code.
They’re slow because of data shape: overfetching, N+1 queries, and missing indexes.
Performance tuning usually starts in SQL, not in the framework.
They’re slow because of data shape: overfetching, N+1 queries, and missing indexes.
Performance tuning usually starts in SQL, not in the framework.
February 10, 2026 at 10:33 AM
Most “slow APIs” I debug aren’t slow because of code.
They’re slow because of data shape: overfetching, N+1 queries, and missing indexes.
Performance tuning usually starts in SQL, not in the framework.
They’re slow because of data shape: overfetching, N+1 queries, and missing indexes.
Performance tuning usually starts in SQL, not in the framework.