GrowERP Update
```GrowERP Update | Hello ,
We’ve just released to staging one of the most important architectural upgrades in GrowERP to date. This update is not just about performance—it fundamentally changes how the system is structured, updated, and maintained.
Here’s what’s new and why it matters. | "Virtual Inclusion": A Lighter, Smarter Backend | Previously, the entire Moqui backend engine—thousands of files—was embedded directly inside the GrowERP codebase. This made the system heavier and harder to keep aligned with upstream updates and security patches.
We’ve now moved to a Virtual Inclusion architecture using Git submodules. | -
Instant upstream updates: Sync with Moqui patches immediately for improved security and performance.
-
Smaller footprint: Faster cloning and deployment by tracking only ERP-specific components.
-
Separation of concerns: Custom business logic remains isolated from the core framework.
| Next-Generation Performance with Moqui 4.0 | | GrowERP now connects seamlessly to Moqui 4.0, bringing major performance and infrastructure improvements. | Java 21 Improved performance and scalability through Virtual Threads, enabling more concurrent requests without increasing memory usage.
Upgraded Infrastructure PostgreSQL 18.1, MySQL 9.5, and OpenSearch 3.4 replace older components.
Note: Database upgrades require migration and reindexing.
Modern Core Now running on Jakarta EE 11 and Jetty 12.1, improving security and real-time capabilities. | For Developers: Breaking Changes | -
Entity API: Use
.resolveEntityName() instead of .getEntityName() -
Sequencing: Replace
getNextSeqId() with sequencedIdPrimary() -
Logging: Use
ec.logger.* instead of logger.*
| Migration guide: View documentation
Moqui 4.0 release: View release notes | This new architecture positions GrowERP for the next decade of enterprise software.
We recommend testing this release in your staging environment. If you need help with migration, simply reply to this email—we’re here to help.
Best regards, The GrowERP Team |
|
|
|