Architecture Schema

Below is a simplified diagram and explanation of the application's architecture. This is designed for non-technical readers.

+-------------------+
|    User/Client    |
+-------------------+
          |
          v
+-------------------+
|   Controller      |  <-- Handles requests from users (like a receptionist)
+-------------------+
          |
          v
+-------------------+
|    Service        |  <-- Makes decisions and processes information (like a manager)
+-------------------+
          |
          v
+-------------------+
|   Repository      |  <-- Stores and retrieves data (like a filing cabinet)
+-------------------+
          |
          v
+-------------------+
|     Database      |  <-- Where all information is kept
+-------------------+

Other important parts:
- Security: Protects the system and manages who can access what.
- Integration: Connects to external services (like DigiKey) to get more information.

How it works

1. The user sends a request (for example, to see a list of components).
2. The Controller receives the request and passes it to the Service.
3. The Service decides what to do and asks the Repository for data.
4. The Repository gets the data from the Database.
5. The Service sends the result back to the Controller.
6. The Controller sends the answer to the user.

Security checks happen at every step to make sure only authorized users can access sensitive information.