How softwaredelta/gnp works
Project type and purpose
• From the file tree and README, this is a full-stack web application (“Delta Software | GNP (RAM)”) composed of:
• A React/TypeScript frontend (in ram-front)
• A Node.js/TypeScript backend (in ram-back) following a clean/hexagonal architecture (layers: arch, app/use-cases, controller, infra)
• An infrastructure module (in ram-infra) describing CI/CD, Docker, AWS, Fly.io deployment, load-testing, and supervision
File structure
• Top-level folders:
• ram-front (single-page React app with Vite, Recoil, hooks, components, pages, API wrappers)
• ram-back (Express-style HTTP controllers, domain “app” services, entities, database client, S3 client, Jest tests)
• ram-infra (Dockerfile, AWS CloudFormation/YAML, Fly.io config, buildspec, supervisord, Locust scripts)
• Patterns:
• Backend uses a layered/hexagonal pattern—“arch” for low-level ports (db-client, s3-client), “app” for business logic, “controller” for HTTP adapters, “entities” for ORM models.
• Frontend is structured by features (auth, deliveries, prospects) with generic UI atoms, API wrappers under src/lib/api, routing under src/routes, global state under src/recoil.
README for additional insights
• Quickstart script (“dev”) to launch both front and back locally
• Links to infra, local environment, and production‐deployment documentation—indicates a multi-environment deployment pipeline
Final advice
• Be exhaustive in identifying every external/infrastructure dependency (S3, database, CI/CD, load-tester).
• Clean architecture layering inside the backend to guide maintainers.