Level 11
If they are two separate projects, then create your own package that both would consume. If they are within the same Laravel project, then create some Service classes that both would consume.
Apr 11, 2020
3
Level 4
Share business logic between web app and api
Hey, I am building a web app with classic Laravel routers views controllers, and also building an API that mobile apps will consume. I am wondering what would be the best approach to share business logic between these two things?
One solution might me calling my own API from views, but it doesn't seem right.
Level 73
One way to do it is to use the same controller and method for both. But that depends on how complex your app is.
If it's just a few methods then you can do something like this.
If it's a bit more complex you can either create service classes or move some of the common logic to the model.
Try to use the KISS way of thinking.
Level 5
I would use a job (Command Bus) which can be used in a controller and also console for instance
UsersController some auth middleware
index() dispatch_now(...new GetUsersJob())
================================
ApiUsersController some other auth middleware
index() dispatch_now(...new GetUsersJob())
================================
Artsisan console handle() dispatch_now(...new GetUsersJob())
https://laravel.com/docs/7.x/queues#creating-jobs
They can be queued to run later on a new thread dispatch() or right away dispatch_now
Very handy and flexible and no need for complex service layers although a repository may work too come to think of it ;)
Please or to participate in this conversation.