[NOT A ISSUE] - Relations without tight coupling between modules

[moiz-conceptlz]

I'm working on a large modular monolithic project using this package, to build fully decoupled modules (e.g., User, Company, etc.).

In this setup, a User belongs to a Company, and I want to display user listings using Livewire 3 + Rappasoft tables, including company_name with support for search, sort, and filters — without tight coupling between modules.

I'm currently solving this by creating a BelongsToRelationService in the related module, and calling it from the consuming module. However, since Livewire 3 re-creates the component class per request, I can't persist service instances using ??=.

I'd really appreciate your input on:

• Any best practices for decoupling relationships between modules
• Handling dynamic joins cleanly with Livewire + Rappasoft
• Structuring reusable services for relational data access across modules

Thanks in advance if you have time to share any thoughts!

[sjardim]

Quick idea without thinking much: If you want to avoid any change on the User table (such as adding a company_id column), which will couple it to the relation, you could listen to default Laravel model events for the user or company and create a table to link both.