SolidProfessor Architecture

AWS Cloud Infrastructure

GitHub CI/CD

Version Control & Deployment

DataDog

Monitoring & Analytics

SonarCloud

Code Quality & Security

Customer Experience

plt.solidprofessor.com/experience

Platform Admin

admin.solidprofessor.com

SolidCareer

sc.solidprofessor.com

Onboarding Experience

plt.solidprofessor.com

Content Library (CMS)

plt.solidprofessor.com/library

VAR (Value-Added Reseller)

var.solidprofessor.com

SolidProfessor Live Training

live.solidprofessor.com

Assessment Experience

skills.solidprofessor.com

Laravel REST API

platform-backend

MySQL Database

Primary Data Store

Component Details

Engineering's Purpose and Path to Success

Our engineering team builds the technical foundation for the 3D design community, creating reliable platforms and tools for creators, educators, and engineers. We transform ideas into user-friendly experiences, focusing on scalability, performance, and empowering creativity.

This vision addresses challenges like inconsistent architecture, outdated tech, slow development, and quality concerns.

Success looks like:

For Customers: Easy creation, learning, and collaboration with intuitive, fast, and reliable tools.
For the Business: Rapid, consistent value delivery, sustainable growth, and becoming the central hub for the 3D community.

We measure success through real outcomes (user behavior changes, faster developer work) with metrics like Learning Velocity, Deployment Frequency, and API Response Time.

Technical Strategy: Modular Monolith

Our technical strategy centers on the Modular Monolith for both backend (Laravel) and frontend (Vue 3) development.

Key Benefits:

Simplicity: Easier to deploy, debug, and develop than complex distributed systems
Organization: Keeps code clean and maintainable with clear separation between business domains
Flexibility: Modules can be easily extracted into microservices or micro-frontends later if needed

We maintain consistent development patterns, only deviating when extreme scale, unique team autonomy, or fundamentally different technology needs arise.

Engineering Practices

Version Control: Trunk-Based Development with Semantic Versioning
CI/CD: Automated builds, testing, and deployment via GitHub Actions
Testing: Continuous testing with Pest, Playwright, Vitest, Storybook
Feature Management: LaunchDarkly for feature flagging
Small Batches: Incremental changes with continuous integration

Color Key

Frontend Properties (Vue 3)

Backend API (Laravel)

Database (MySQL)

Third Party Services

AWS Cloud Infrastructure

API Connections

Database Connection

MySQL Database

Primary relational database management system storing all application data.

Key Features

High-performance relational database
ACID compliance for data integrity
Scalable architecture
Automated backups

Connections

Connected to Laravel API only
Receives queries from Laravel API
Data accessed by frontend apps through API

Laravel REST API

Central API layer built as a Modular Monolith, handling all business logic and data operations with clear domain separation.

Architecture Approach

Modular Monolith: Single deployable unit with clear module boundaries
Domain-Driven Design: Each module represents a distinct business domain
Future-Ready: Modules can be extracted to microservices when needed
Simplified Operations: One deployment, one database, easier debugging

Key Features

RESTful API architecture
Authentication & authorization
Request validation
Response caching
Rate limiting

Business Domains

User & Account Management
Content Management System
Learning & Assessment
Analytics & Reporting
Commerce & Billing

GitHub CI/CD

Central hub for version control and automated deployment pipelines following Trunk-Based Development practices.

Development Workflow

Trunk-Based Development: Single main branch, short-lived feature branches
Small Batches: Frequent commits with incremental changes
Continuous Integration: Automated builds on every commit
Branch for Release: Release branches for production deployments
Semantic Versioning: Clear version management (MAJOR.MINOR.PATCH)

CI/CD Pipeline

GitHub Actions: Primary CI/CD automation tool
Automated Testing: Pest, Vitest, Playwright tests on every PR
Code Quality: OxLint, ESLint, Prettier enforcement
Automated Deployment: Direct to AWS infrastructure
Feature Flags: LaunchDarkly integration for safe rollouts

Testing Strategy

Unit Tests: Pest (PHP), Vitest (JS/TS)
Integration Tests: API endpoint testing
E2E Tests: Playwright for user workflows
Component Tests: Storybook for UI components
Performance & Security: Automated scans in pipeline

SolidProfessor Ecosystem

Component Details

Engineering's Purpose and Path to Success

Technical Strategy: Modular Monolith

Engineering Practices

Color Key

MySQL Database

Key Features

Connections

Laravel REST API

Architecture Approach

Key Features

Business Domains

GitHub CI/CD

Development Workflow

CI/CD Pipeline

Testing Strategy