It has been over a year since I last wrote an article on this site, and my god have things changed since then. Well, I'm back with an update on this site, and a look at what the future has in store.
Multitenancy with Laravel is a course and package offering that I've been working on for some time. It covers everything you need to do to get started with multitenancy and Laravel.
In this article, I'm going to go through some of the reasons I stopped using Eloquent, as well as covering the reason for Articulates creation, and the different iterations that I took to make it what it is today.
APIs are, after all, another data source, so why not treat them like one?
Lately I've found myself getting frustrated with Eloquent, needing more than Laravels default ORM offers. I'm a big fan of the DataMapper pattern, but I become disheartened with the overhead and complexity of Doctrine. My time spent with Java has brought out a love for objects, and absolutely everything being objects. With this in mind, I created myself a super basic lightweight ORM named Articulate.