You'll find the less Laravel specific code used in your model implementation the better. Watch some of laracasts.com and you'll find a lot of what he does is abstracting out the Laravel specific parts so it can be replaced with what ever implementation you want.
If using laravel you will want to keep your http layer using laravel. I'm sure there are nice ways to avoid it but why would you.
Sign in to participate in this thread!
We'd like to thank these amazing companies for supporting us