Support the ongoing development of Laravel.io →
posted 3 months ago
Packages

I'm working on a monolith app which means that there is only one codebase. Now I have to add functionalities for the app for which I have to create certain code XYZ that is added to the app and the app then uses the exposed interface to interact with the system. for instance i had to use NATS for which I created interfaces and stuff. and Manticore DB again for which I had to create a bit of interface.

My quetion is that XYZ code (see above) which is not directly related to the app logic but only makes the interface with the outsode entity possible. it's a candidate for a package. Since this is a monolith app and this code is created only for this app, should I create a package for it?

this code just added "noise" to the existing code. I want to reduce this noise. What do youy recommend? What is the general practice in Laravel community?

mercede liked this thread

1
moderator

I would recommend to keep the code in one repository so not a new package.

But you can (re)structure your code to have multiple modules with separated code parts.

0

Sign in to participate in this thread!

Eventy

Your banner here too?

MERCEDE mercede Joined 22 Apr 2025

Moderators

We'd like to thank these amazing companies for supporting us

Your logo here?

Laravel.io

The Laravel portal for problem solving, knowledge sharing and community building.

© 2025 Laravel.io - All rights reserved.