2 - 2. Technical stack
Structure
💬
The monorepo structure simplifies version management, avoids dependency issues, and ensures consistency across projects.
NX is particularly effective for managing shared configurations like ESLint and Jest, while features like build caching and affected file tracking greatly optimize workflows. It’s a highly reliable tool for streamlining development.
I’m going to use Docker for production only, i want to create images for each major version and deploy them to easily navigates between them.
NX is particularly effective for managing shared configurations like ESLint and Jest, while features like build caching and affected file tracking greatly optimize workflows. It’s a highly reliable tool for streamlining development.
I’m going to use Docker for production only, i want to create images for each major version and deploy them to easily navigates between them.
- NX as a Monorepo
- Pnpm (chosen for efficient dependency management and workspace support)
- Docker
Backend
💬
To ensure Taskly remains dynamic and supports real-time updates efficiently, a REST API with WebSocket support is preferred over GraphQL, which can add unnecessary complexity for this use case.
- NodeJS
- API Rest
- PostgreSQL
Frontend
- ReactJS (for a modern, component-based architecture)
- React-query (to simplify and optimize API call management)
- TypeScript (for type safety and improved code maintainability)
CI/CD Pipeline
- Github actions
Tests
- Jest and Playwright for Unit and E2E Testing