May Sale! All accounts are 40% off this week.
Is it possible to use filamentphp to create exclusively the administration operations that are carried out for a specific project (CSM, E-commerce, TurnBasedSystem, and more...) and also create in the same project an API-Rest based on just those same models?
Maybe my question is complicated to understand, but I basically mean that filamentphp is intended only for “Monolith” style applications while an API-Rest should be totally unrelated to what is just filamentphp?.
My goal is to see if I can avoid the admin panel design for dedicated operations for administrators, while for users or other functionalities should be developed as an API-Rest to be consumed by another external service. Or should I just design absolutely everything from scratch.
You can use FilamentPHP to handle admin tasks like managing users, products, or orders, which saves you the time of designing an admin panel from scratch. For user-facing features, you can create routes in routes/api.php and use controllers to manage actions like fetching, creating, or updating data. Both the admin panel and the API can share the same database models.
@Rebwar Thank you for your answer, how much performance could the application be affected? I mean, if I create only one API that does absolutely everything it would probably be more efficient than having filament running as a monolith within the application and in turn an API service to manage certain operations on the user side.
Something additional that I would like to ask, is that if my application can have a projection of being deployed as a mobile application, probably filament does not make much sense and it would be better to make an API-Rest in its totality that includes the administrative functions. I mean it would not make sense to create the same administration operations in an api at the same time that exist in filament?
@baltasarortiz Using Filament for the admin panel and a REST API together won’t significantly affect your app’s performance since admin tasks usually handle low traffic, and both can share the same database and logic.
If your app might grow into a mobile or fully API-based system, building a single REST API for both admin and user features is better. It avoids duplication, simplifies management, and scales well.
Choosing Filament depends on your use case and the complexity of your project. use it if you need a quick admin panel, but go for a full REST API if scalability and API-first architecture are priorities.
Please or to participate in this conversation.