Integrating Medusa into a Monolith Architecture with Custom Components

[thefrana]

Hi Medusa Team,

First of all, thank you for the incredible work you've put into Medusa! The 2.0 release is particularly exciting, and we’re exploring how to adopt it as part of our e-commerce solution.

We are a software company with a monolith architecture, and we want to leverage Medusa’s robust business logic while customizing other components to align with our requirements. Here's an overview of what we're aiming to do:

• Reuse Medusa's Core Business Logic: We’re impressed with the flexibility and power of the commerce logic Medusa provides. We'd like to integrate it into our monolith rather than run it as a standalone service.
• Custom Database: We’d like to connect Medusa’s core logic to our custom SQL database schema instead of the default implementation.
• Custom Admin Components: Our platform already has an admin interface, so we'd like to reuse some components from Medusa’s admin while implementing others to fit into our existing architecture.
• Adapter Layer: To achieve the integration, we anticipate needing some sort of adapter layer between Medusa and our monolithic setup.

Questions:

1. Is it feasible to decouple Medusa’s business logic and integrate it into a monolith application?
2. Can we override or extend Medusa's modules to use a custom SQL database while keeping the core logic intact?
3. Are there best practices or existing tools that would help us adapt Medusa to a custom admin interface?
4. Are there any potential pitfalls or limitations to this approach we should be aware of?

We’re eager to explore how we can make this work while aligning with Medusa's design principles. If this type of integration is possible, any guidance, documentation, or examples you can share would be greatly appreciated.

Looking forward to hearing your thoughts!

Lukas