How to deploy Merp on AWS?

Merp supports AWS as an ASP.NET Core environment, but the README only mentions experimental support; you'll need to configure it manually using the provided multi-environment setup, likely involving cloud-specific adjustments for databases and services.

Merp vs Odoo: which is better for small businesses?

Merp is open-source with event-driven architecture for .NET customization, while Odoo is a more mature, feature-rich ERP with a larger ecosystem; choose Merp for .NET integration and modular control, or Odoo for out-of-the-box functionality and community support.

How to customize bounded contexts in Merp?

Modify the independent service projects for domains like accountancy or registry, but this requires .NET expertise and understanding of event-sourcing patterns, as the README doesn't provide detailed customization guides.

Does Merp support mobile apps?

Merp includes web-based clients (Blazor and Vue.js SPA) that are responsive, but native mobile apps aren't built-in; you can develop them using the public API for integration, though it adds development overhead.

What are the system requirements for running Merp on-premises?

Requirements include .NET Core runtime, databases like MongoDB or SQL Server, and web server capabilities, but the README lacks specifics; plan for adequate resources based on your scale and the modular services deployed.

Is Merp actively maintained?

Last significant updates were in 2021, and it uses ASP.NET Core 3.1, suggesting reduced activity; check the GitHub repository for recent commits or forks to assess current development status.

Open-Awesome

Companion Code for Microsoft .NET Architecting Applications for the Enterprise

AGPL-3.0C#

An open-source, event-based micro ERP system built on ASP.NET Core for small to medium businesses.

GitHub

502 stars152 forks0 contributors

What is Companion Code for Microsoft .NET Architecting Applications for the Enterprise?

Merp is an open-source, event-based micro ERP system built on ASP.NET Core, designed to provide essential enterprise resource planning functionality for small to medium businesses. It uses an event-driven architecture and modular bounded contexts to handle core business domains like accountancy, registry, and task management. The system supports multiple client interfaces, including Blazor and Vue.js, and offers integration capabilities through a public API.

Target Audience

Small to medium businesses, .NET developers, and system integrators looking for a customizable, self-hosted ERP solution with modern architectural patterns like event sourcing and CQRS.

Value Proposition

Merp offers a modular, event-driven alternative to monolithic ERP systems, enabling businesses to adapt and scale specific components without vendor lock-in. Its open-source nature and support for multiple deployment environments (on-premises, Azure, AWS) provide flexibility and control over infrastructure.

Overview

An event based Micro ERP

Use Cases

Best For

Small businesses needing a customizable, self-hosted ERP system
Developers implementing event-sourcing and CQRS patterns in .NET
Integrating ERP functionality with external systems via APIs
Building modular, domain-driven business applications
Deploying ERP solutions across hybrid cloud/on-premises environments
Adding natural language bot interactions to business workflows

Not Ideal For

Businesses requiring a fully-featured, out-of-the-box ERP with minimal configuration and support
Projects that do not benefit from or need event-sourcing and CQRS architectural patterns
Teams lacking .NET development expertise for customization, deployment, and maintenance

Pros & Cons

Pros

Event-Driven Architecture

Uses event sourcing and CQRS patterns for reliable, scalable data handling, as highlighted in the key features and architecture description.

Modular Service Design

Separates business domains into bounded contexts as independent services, enabling targeted customization and scaling without monolithic constraints.

Multi-Client Flexibility

Includes both Blazor WebAssembly and Vue.js SPA clients, offering choice in front-end technology based on project needs.

Integration-Ready API

Public API supports external integrations and automation, allowing seamless connection with third-party systems and workflows.

Cons

Complex Setup Process

README lists multiple manual steps like running MongoDB patches, Entity Framework migrations, and npm builds, which can be error-prone and time-consuming.

Outdated Technology Stack

Based on ASP.NET Core 3.1 with last major updates in 2021, potentially missing newer .NET features, security patches, and long-term support.

Sparse Documentation

Focuses on release notes without comprehensive setup guides or API documentation, making onboarding and troubleshooting difficult for new users.

Frequently Asked Questions

Related Projects

Modular Monolith

Full Modular Monolith application with Domain-Driven Design approach.

Stars13,872

Forks2,172

Last commit2 years ago

eShopOnWeb

Sample ASP.NET Core 8.0 reference application, now community supported: https://github.com/NimblePros/eShopOnWeb

Stars10,693

Forks6,014

Last commit1 year ago

EquinoxProject

Web Application ASP.NET 9 using Clean Architecture, DDD, CQRS, Event Sourcing and a lot of good practices

Stars6,781

Forks1,655

Last commit3 months ago

Event Sourcing .NET

Examples and Tutorials of Event Sourcing in .NET

Stars3,675

Forks545

Last commit2 months ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub