Long Execution Paths
Business operations are split into repeated cross-process and cross-network calls between service frameworks, protocols, and databases.
Database as an Execution Platform
MuduDB
Bring Applications Into the Database Runtime
A unified execution and data management platform for data-intensive applications, integrating transaction processing, application logic, state access, and deployment into a single database runtime.
MuduDB
Bring Applications Into the Database Runtime
Mudu Package
WASM BytecodeSchemaProceduresAssets
MuduDB Runtime
WASM HostProcedure EngineSyscall Layer
MuduDB Kernel
TransactionQueryKVStorageScheduler
Local / Cloud / Edge Nodes
DeploymentDistributionExecution Locality
Problem
Data-intensive applications are slowed down by system boundaries
In traditional architectures, application logic runs outside the database. A single operation often crosses application services, network protocols, drivers, connection pools, SQL executors, and transaction managers.
Split Transaction and Business Logic
Transaction semantics remain inside the database while business procedures live in application services, forcing developers to manually maintain consistency.
Complex Deployment and Operations
Applications, databases, dependencies, scripts, and configurations are deployed separately, and integration cost grows with system scale.
Solution
MuduDB brings application procedures into the database runtime
Developers can write data-intensive business procedures in familiar programming languages, then compile, package, and deploy them directly inside the database. The database becomes a unified platform for data management, transaction processing, application execution, and deployment distribution.
Get Started
Deploy applications inside the database in minutes
Package your schema, procedures, and assets, then deploy them directly into the MuduDB runtime. No separate application servers needed.
1
$ mpm-install your-application.mpk
Architecture
A unified execution and data management architecture
MuduDB adopts a Kernel-Runtime separation architecture. The database kernel provides storage, transaction, query, and scheduling capabilities, while the runtime hosts application procedures and accesses kernel capabilities through lightweight syscalls.
Mudu Package
WASM BytecodeSchemaProceduresAssets
MuduDB Runtime
WASM HostProcedure EngineSyscall Layer
MuduDB Kernel
TransactionQueryKVStorageScheduler
Local / Cloud / Edge Nodes
DeploymentDistributionExecution Locality
Video Overview
Capabilities
Core capabilities for database-native applications
In-Database Application Execution
Deploy data-intensive procedures into the database runtime to reduce cross-process, cross-network, and cross-service overhead.
Portable WASM Runtime
Use a WebAssembly-based runtime model for cross-platform and cross-language procedure execution.
Unified Syscall Interface
Access database kernel capabilities through lightweight, stable syscalls instead of heavy driver and connection objects.
Transaction-Procedure Coordination
Coordinate transaction processing, state access, and business logic within the same execution path.
Data-Local Execution
Use partitioning and data locality to move computation close to data for low-latency and high-concurrency services.
Application Package Distribution
Package schema, procedures, dependencies, and initialization scripts so database applications can be installed and upgraded like software.
Scenarios
Where MuduDB fits
Enterprise Transaction Processing
Orders, inventory, accounts, approvals, and settlement procedures execute close to transactional state.
Cloud Platform Services
Build multi-tenant, high-concurrency, low-latency data services that unify data access and business procedures.
Intelligent Data Applications
Provide a unified execution, state, and deployment substrate for AI-generated and data-heavy applications.
Massively Multiplayer Online Games
Serve high-frequency state updates, transactional operations, and locality-intensive backend workloads.
Research
Research and White Papers
MuduDB explores a new boundary between database systems, application runtimes, and data service architectures.
System Architecture Soon Technical White Paper Soon Paper Draft Soon Benchmark & Evaluation Soon
Open Source
Open Source First
MuduDB is evolving as an open-source system. We welcome stars, trials, feedback, and contributions.
Roadmap
From kernel prototype to application marketplace
Phase 1
Kernel Prototype
Phase 2
WASM Procedure Runtime
Phase 3
Package & Deployment
Phase 4
Distributed / Local-first Execution
Phase 5
Marketplace