How webvella/webvella-erp works
This project is a robust, open-source ERP system designed for extreme customization and plugability. It is built in ASP.NET Core 7 and primarily targets PostgreSQL as its database. The purpose of the project is to manage a wide array of business data and processes via a modular, extensible architecture. Its components are organized into a core ERP system, numerous plugins (such as CRM, Mail, MicrosoftCDM, Project, Next, and SDK), several site and web interface projects (including web, site, and even WebAssembly client/server applications), and support for console-based utilities and background jobs.
Main Components Identification
• Core ERP Kernel – Representing the central business logic and services (found in the “WebVella.Erp” folder). This includes fundamental APIs, entity management, hook managers, job/process managers, utilities (like authentication, logging, and security), and data access repositories.
• Plugins Layer – A modular collection of additional business functionality. Each plugin (CRM, Mail, MicrosoftCDM, Next, Project, SDK, etc.) is its own project/component that depends on the core ERP kernel while adding or overriding specific functionality.
• Presentation/UI Layer – Several web frontends are implemented:
• ASP.NET Core based sites and web projects (e.g., “WebVella.Erp.Site”, “WebVella.Erp.Web”) that serve the primary user interface using Razor Views, controllers, and tag helpers.
• A WebAssembly client–server pair that provides a modern, client-side SPA experience.
• Console Application – A separate project for tasks such as initialization, maintenance, or background operations.
• Background Jobs and Middleware – Components that handle scheduled tasks, error handling, security concerns, and other cross-cutting concerns.
• Database Layer – Although not directly part of the code tree, annotate the PostgreSQL database as the persistence layer supporting the system.
Relationships and Interactions
• The Core ERP Kernel is at the center of the system; the Plugins register and interact with this core through well-defined hooks and APIs.
• The Presentation/UI Layer interacts with the Core ERP Kernel through API controllers and service calls, leveraging middleware (e.g., authentication, error handling) to manage requests.
• The background jobs subsystem asynchronously processes tasks; this part interacts with the core services and sometimes with plugins.
• Data access components (repository classes, data source managers) sit between the core logic and the PostgreSQL database.
• The WebAssembly projects feature a client (browser) and server integration that communicates with the API and core system via custom services.
Architectural Patterns and Design Principles
• Layered Architecture: Separate the system into presentation, business, plugin, and data layers.
• Modular/Plugin Architecture: Emphasize the extensibility points (hooks, service interfaces) where plugins register with and extend core functionality.
• Dependency Injection and Middleware: Components such as controllers, repositories, and job managers use dependency injection provided by ASP.NET Core.
• Event-based and Hook-Driven Processing: Detail the hook managers and event-driven modules where different actions (record creation, update, deletion, etc.) have extensibility points.
Relevant Technologies and Frameworks
• ASP.NET Core 7 for the core framework.
• PostgreSQL as the database.
• Razor Views, Controllers, and TagHelpers for the web front end.
• WebAssembly for the client-side SPA module.
• C# and .NET libraries.
• Build, deployment, and configuration files (such as JSON config files) that govern the environment setup.