PHP is a very popular language, and when something gets very popular it usually happens that someone come out and just says “that’s not cool”, and it’s ok, it happens. I read lots of articles saying “PHP is not cool for machine learning” or saying “just move to language X to perform this, there will work better” (I’m not gonna flame another language, just talking about random stuff on the internet).

I’m a PHP lover, I won’t negate that, I tried different languages, frameworks, developed native applications, I love to try new things but I also love PHP. …

You’ve spent the latest X hours building a very complex system, with lots of complex interactions and features, you wrote tests and now everything works. But you haven’t a Dashboard where you can monitor details of your system and perform CRUD operations on your system models, and you don’t want to spend much time spinning up a dashboard that you don’t directly need or won’t directly use, so?

This is, in shorts, what happened to me some days ago. I want to give you a background without biasing your view on the entire idea of this blog post.
I had to build a complex system where you can perform just one operation, the system has just one complex feature: the user must upload files, pick a configuration, insert his email (yes, the user has no logins) and then give everything to the server that enqueues a job; this job works in the background performing the stuff it has to do and finally sends an email. It was a beautiful system to code (if you like coding 💻 like me), I had to glue Laravel with some bash scripts, I wrote tests, checked for security faults, but… what about if the managers want to see the current status of the jobs and what users do? And I started looking for the fastest way to build a nice dashboard with CRUD operations, with the fewer code to write and the best possible result, and here it is InfyOmLabs Laravel Generator! …

Nowadays building a big system composed of multiple API endpoints is becoming more and more a common practice, even thanks to the diffusion of the microservice pattern.

Adopting this kind of architecture you often have multiple APIs offering different services for the same user, accessible through a single frontend, like a SPA, a mobile app, a desktop solution, etc…
In this way, you can have for example:

• an API for Authentication and user profile management.
• multiple API for each service.
• a frontend that talks to each API (or even multiple frontend).

In this article we’ll build two simple APIs powered by Laravel and JWT. …