@cardflowengineering

miu uyy

@cardflowengineeringNigeriaJoined August 2026

Practical engineering notes on trustworthy gift-card data, resilient services, and clear product systems.

About

Nothing here yet.

Available for

Nothing here yet.

miu uyy's blogs

CardFlow Engineeringcardflow-engineering.hashnode.dev3 posts

Articles Comments

Recently published

MUmiu uyycardflow-engineering.hashnode.devSep 21 · 5 min read

A Cache Hit Is Not Fresh Data: Keep Source Dates Separate from HTTP Dates

A dashboard loads instantly. The request returns 200 OK. The cache reports a hit. Under the number, a badge says “Updated just now.” That badge might be describing a page render while the underlying o

MUmiu uyycardflow-engineering.hashnode.devAug 14 · 10 min read

Designing a Retry-Safe Error Model for Reference-Rate APIs

A reference-rate API can be fast, typed, and highly available yet still cause outages if clients cannot tell whether a failed request is safe to retry. The dangerous design is a single generic error—o

MUmiu uyycardflow-engineering.hashnode.devAug 12 · 8 min read

Building a Reliable Gift-Card Reference-Rate Data Pipeline

A rate table looks simple: a route, a number, and a timestamp. The difficult part is proving what that number means, where it came from, whether it is still fresh, and what should happen when the same

miu uyy

About

Available for

miu uyy's blogs

Recently published

A Cache Hit Is Not Fresh Data: Keep Source Dates Separate from HTTP Dates

Designing a Retry-Safe Error Model for Reference-Rate APIs

Building a Reliable Gift-Card Reference-Rate Data Pipeline

Search Hashnode

miu uyy

About

Available for

miu uyy's blogs

Recently published

A Cache Hit Is Not Fresh Data: Keep Source Dates Separate from HTTP Dates

Designing a Retry-Safe Error Model for Reference-Rate APIs

Building a Reliable Gift-Card Reference-Rate Data Pipeline