Application and catalogue
The documented stack combines Next.js, an Express.js API and MongoDB Atlas. Catalogue records keep product attributes separate from presentation so the interface can compare rates, benefits and eligibility consistently.
← Explore the engineering portfolio
Engineering portfolio
CarteDeCredit.tn
Article updated
A platform for comparing credit-card features and eligibility information from Tunisian banks. The project connects a structured product catalogue with a web interface and a container-based release workflow.
Discuss a similar engineering challengeContext
The problem
Bank product information uses different labels and eligibility rules. The comparison model needs to preserve those differences while presenting a consistent view. Keeping catalogue updates separate from application deployments helps maintain the information without rebuilding the whole service.
Responsibility and scope
The documented WebNasr scope covers application architecture, catalogue storage, container packaging, deployment automation and web security controls. The portfolio describes the technical work; it does not claim endorsement by the banks represented in the catalogue.
Engineering decisions
Architecture and tradeoffs
Use a structured catalogue with explicit product fields and validate changes before publishing them. The comparison interface can then filter comparable features without treating differently named products as equivalent by accident.
Container delivery
Docker packages the application and its runtime dependencies. GitLab CI/CD provides a repeatable route from a reviewed change to a deployable application.
Operational controls
PM2 and application monitoring support process visibility. ModSecurity adds a web application firewall layer; access controls, validation and dependency maintenance remain part of the application’s security responsibilities.
What the work establishes
Outcome and evidence
The architecture supports bank-product comparison, structured catalogue updates and repeatable container delivery. The useful outcome is the connected information and release workflow. Bank/card counts, delivery duration and uptime are omitted until a dated inventory or monitoring report can substantiate them.
Plan your next platform change
Discuss your current architecture, delivery constraints and the evidence you need to measure progress.
Talk to WebNasr