Platform Overview

Platform Overview

Mixcore CMS is built on a modern microservices architecture using .NET 9.0. This document provides an overview of the platform's architecture and its key components.

System Architecture

graph TD
    A[Client Applications] --> B[API Gateway]
    B --> C[Main Application]
    B --> D[Platform Services]
    C --> D
    D --> E[Database & Storage]

Loading

Core Components

1. Applications Layer

Main Application (mixcore)

• Core CMS functionality
• Content management
• User interface
• Business logic

API Gateway (mixcore.gateway)

• API routing and management
• Request aggregation
• Load balancing
• Security enforcement

Service Host (mixcore.host.aspire)

• Service orchestration
• Service discovery
• Health monitoring
• Configuration management

2. Platform Services

Authentication & Identity

• mix.auth - Authentication services
• mix.identity - Identity management
• JWT-based authentication
• Role-based access control

Database & Storage

• mix.database - Core database operations
• mix.scylladb - NoSQL database integration
• mix.storage.lib - Storage services
• mix.repodb - Repository pattern implementation

Communication

• mix.signalr - Real-time communication
• mix.signalr.hub - SignalR hub implementation
• mix.communicator - Messaging services
• Event-driven architecture

Core Services

• mix.service - Service infrastructure
• mix.queue - Queue management
• mix.quartz - Job scheduling
• Background task processing

Shared Components

• mix.shared - Shared utilities
• mix.constant - Constants and configurations
• mix.library - Core libraries
• mix.log - Logging services

Data Flow

1. Request Processing

   • Client request received by API Gateway
   • Request routed to appropriate service
   • Authentication and authorization checks
   • Service processing and response

2. Service Communication

   • Inter-service communication via SignalR
   • Event-driven architecture for async operations
   • Queue-based processing for long-running tasks

3. Data Management

   • Repository pattern for data access
   • Multiple database support
   • Caching and optimization
   • Transaction management

Security

• JWT-based authentication
• Role-based access control
• API key management
• Secure communication channels
• Data encryption at rest

Scalability

• Microservices architecture
• Container-based deployment
• Load balancing
• Service discovery
• Auto-scaling support