Category: Laravel, Laravel, PHP, PHP, api, api

I work with a large enterprise application that's broken down into a few teams, languages and modules. Modularizing an application is still important even though completely breaking it apart might not necessarily be a day-one activity. Recently I've been working on the part of the application that will be receiving data.

However, for the sake of a possible fragmentation of modules in the future, I decided to put each module in it's own isolated domain.

Instead of breaking things down by what they are, the structure focus more on separating things by what they do.
Newsletter

Get the latest Laravel/PHP jobs, events and curated articles straight to your inbox, once a week

Fathom Analytics | Fast, simple and privacy-focused website analytics. Fathom Analytics | Fast, simple and privacy-focused website analytics.
Achieve superior email deliverability with ToastMail! Our AI-driven tool warms up inboxes, monitors reputation, and ensures emails reach their intended destination. Sign up today for a spam-free future. Achieve superior email deliverability with ToastMail! Our AI-driven tool warms up inboxes, monitors reputation, and ensures emails reach their intended destination. Sign up today for a spam-free future.
Community Partners