Designing a modular ERP with Symfony + MariaDB + Bootstrap – best practices?
05:01 22 May 2026

I’m currently working on an ERP project at Göhltec and I’d like to get some input from the community regarding architecture and best practices.

**Stack we’re using**

Backend: Symfony (API-first approach, service-oriented architecture)
Database: MariaDB
Frontend: Twitter-Bootstrap + JavaScript (partly vanilla, partly component-based)

**Context**

The ERP system is modular (e.g. customers, inventory, invoices) and designed to scale. We currently use a mostly server-rendered approach with some dynamic frontend components.

**Questions**

I’m especially interested in your experience with:

1. Modular architecture in Symfony

Do you prefer a monolithic structure with bundles/modules or splitting into microservices early on?

2. Database choice

Have you faced limitations with MariaDB in ERP-like systems (large datasets, complex queries)?

Would PostgreSQL be a better choice long-term?

3. Frontend approach

At what point does it make sense to move from Bootstrap + vanilla JS to a full SPA (Vue/React)?

4. Permissions & roles

Any recommended patterns or libraries for handling complex role/permission systems cleanly?

I’d really appreciate concrete examples, lessons learned, or links to similar projects.

Thanks in advance

reactjs vue.js twitter-bootstrap symfony mariadb