How mickedevx/restaurantproject works
Main Components
a. Salesforce Platform: At the heart of the architecture, the Salesforce backend serves both as the data store and execution environment.
b. UI Components:
• Aura Components: Found under the “aura” directory. They represent part of the user interface.
• Lightning Web Components (LWC): Located in the “lwc” directory. Components like "containerProducts" and "productComponent" define the modern, dynamic frontend.
c. Backend Business Logic:
• Apex Classes: Controllers such as InsertPedidoController.cls and SearchAvailableProducts.cls encapsulate business logic and handle requests initiated from the UI.
d. Data Model:
• Custom Objects: The objects are defined in directories “Detalle_del_pedido__c”, “Pedido__c”, and “Producto__c” along with their associated fields and list views. These represent the core business entities (e.g., orders, products, and order details).
Relationships and Interactions
• UI Components (both Aura and LWC) to the Apex Controllers, signifying that user actions trigger business logic.
Architectural Patterns and Principles
• Separation of Concerns: UI components (Aura and LWC) handle the presentation layer, while Apex controllers manage the business logic and act as the API between the UI and the data layer.
• Declarative/Data-Driven Design: The custom objects’ structure and relationships drive the core data model.
• Salesforce DX Project Structure: Note the importance of the “sfdx-project.json,” how metadata is organized under “force-app,” and integration of configuration resources.
Relevant Technologies and Frameworks
• Salesforce DX for development and deployment.
• Lightning Web Components and Aura Framework for the user interface.
• Apex as the server-side programming language.
• Salesforce Metadata API (visible by the presence of .object-meta.xml and field-meta.xml files) for managing custom object definitions.