How sucodelarangela/backend-tech-challenge works
Project type and purpose
• This is a Node.js/Express backend API for a Finance Tech Challenge. It provides REST endpoints for accounts, transactions, statements and user management, backed by MongoDB (via Mongoose). It is consumed by a Backend-for-Frontend (BFF) service and exposes Swagger documentation.
File structure
• Top level:
• Dockerfile, package.json/lock, README.md, Postman collection
• src/index.js (application entry point)
• src/routes.js & src/publicRoutes.js (Express routing layers)
• src/swagger.js (Swagger/OpenAPI setup)
• src/controller (Account.js, User.js): Express controller layer
• src/feature: business-service layer (get/save/update/delete functions for Account, Card, Transaction, User)
• src/infra/mongoose: persistence layer
• mongooseConect.js (DB connection)
• modelos.js (schema definitions)
• repository/*Repository.js (data access via repository pattern)
• src/models: domain-model definitions used across the app
README for additional insights
• Describes the layered architecture (controller → feature/service → repository → Mongo)
• Lists the primary REST endpoints, Docker instructions and Swagger UI at /docs
Elements
→ Client to Router
→ Router to Controller
→ Controller to Service
→ Service to Repository
→ Repository to MongoDB
• Business Logic (Features) in another
• Data Access (Repository/DB) in a third
• Deployment (Docker/Render) as a border or background