Application delivery
Next.js and TypeScript provide the comparison interface. Server-rendered pages make essential information available in the initial HTML and provide a foundation for crawlable rate pages.
← Explore the engineering portfolio
Engineering portfolio
TauxDeChange.tn
Article updated
A currency comparison platform that brings exchange-rate information from Tunisian banks into one interface. The engineering work connects data collection, caching, web delivery and operational visibility.
Discuss a similar engineering challengeContext
The problem
Bank exchange-rate information is published across separate sources and can change on different schedules. A useful comparison experience needs a consistent data model, clear refresh boundaries and a page that remains usable when an upstream source is slow or unavailable.
Responsibility and scope
The documented engineering scope covers the web application, source integration, cache design, infrastructure configuration and deployment pipeline. Mohamed Nasr leads WebNasr’s platform engineering work. The project is presented as part of the WebNasr engineering portfolio.
Engineering decisions
Architecture and tradeoffs
Separate rate collection from page requests. A request should read a prepared view of the data rather than wait for every bank source. Cache expiry and refresh handling make the freshness tradeoff explicit and keep an upstream outage from becoming an application outage.
Data and caching
Python collection workflows normalize source data before it reaches the application. Redis supports cached reads; refresh and failure handling belong in the collection layer rather than being hidden in the user interface.
Release and security
GitHub Actions and Terraform describe the release and infrastructure workflow. Cloudflare WAF provides an edge security layer, complemented by application validation and monitoring.
What the work establishes
Outcome and evidence
The platform combines multi-source rates, a reusable cache layer and a repeatable delivery workflow. Those are observable engineering features of the documented design. Traffic, Google position, availability and page-speed improvements are not quantified here because a dated measurement record is not published.
Plan your next platform change
Discuss your current architecture, delivery constraints and the evidence you need to measure progress.
Talk to WebNasr