How paulfriki55/pruebatecnicanetby works
Main Components
• Backend Microservices:
– ProductService: Manages product data (create, read, update, delete).
– TransactionService: Handles transaction records (purchases and sales) and updates to the inventory.
• Database:
– A SQL Server instance initialized via the provided crearBDD.sql script (creates the InventoryDB and tables).
• Frontend:
– An Angular application (located in frontend/gestion-productos) that uses standalone components to manage product and transaction views.
• External Tools:
– API endpoints for each microservice shown in the README (swagger endpoints for easy testing/documentation).
Process Flow
• Start at the User Interface:
– The Angular frontend displays pages for listing products, product details, forms for adding/editing products, as well as similar components for transactions.
• When a user interacts with the UI, the frontend sends RESTful API calls to the appropriate backend service:
– If a product is being viewed or modified, the frontend calls the ProductService API.
– If a transaction is initiated, the frontend interacts with the TransactionService API.
• The Microservices communicate with the SQL Server database:
– Both ProductService and TransactionService use their respective ApplicationDbContext implementations to interact with the same underlying SQL Server database.
• Data Flow Summary:
– User action in the frontend → HTTP request to appropriate microservice → Microservice logic and database query/update → HTTP response returned → UI updates accordingly.
Architectural Patterns
• Microservices Architecture:
– Note that the backend is split into multiple services (ProductService and TransactionService) that communicate through REST APIs.
– Highlight that each service has its own set of endpoints.
• Separation of Concerns:
– The frontend is entirely decoupled from the backend logic, communicating only through standardized REST calls.
• Process Flow: