Persist normalized date/location times
Persist normalized date/location times rather than calculate every public request.
🌙 District-aware Sehri and Iftar schedules for Bangladesh, with PDF exports and protected timetable management. Next.js, PostgreSQL, Prisma.

Sehri/Iftar schedules need a clear local-time public view and an auditable maintenance workflow because external prayer-time sources, district selection, and timetable corrections can change the result.
Calculated times depend on source, method, location, and local authority.
External fetching requires retry/rate limiting and must not overwrite validated data indiscriminately.
Duplicate date/location rows and malformed bulk imports must be rejected.
Next.js public/admin UI; schedule service for query/import/status/formatting; Prisma/PostgreSQL with unique (date, location) records and tagged cache; Aladhan adapter with retry/token-bucket controls plus export generators.
Next.js public/admin UI.
Schedule service for query/import/status/formatting.
Prisma/PostgreSQL with unique (date, location) records and tagged cache.
Aladhan adapter with retry/token-bucket controls plus export generators.
Persist normalized date/location times rather than calculate every public request.
Validate JSON/CSV size, fields, row limits, and duplicates before writes.
Use tagged caching/revalidation for reads and explicit source/method caveats for accuracy.

Share your challenge, scope, and timeline to start a focused conversation.