I have a monolithic application. It is MVC, PHP, all on one server. It does get copied to another server or replicated. There are also older web pages that connect to databases that aren't related to the MVC app at all, adding to the complexity.
I don't have a large team. I don't need big teams from various sections of a business to produce a microservice. But, I do have a lot of databases I have to query and bring back that information into a single web page, transparent to the user. Not just tables, whole databases.
On my application, the back-end, I have IIS, for example, and the application has various models that get the information from the databases. Over time, these models get bloated, or the controller does. Refactoring has to happen (this is my experience anyway.)
This system is older, and new things need to be added, lots of things. It is enough to justify a new web application.
In this new application, if I want to use JavaScript on the front-end that consumes a REST API, is the combination of thes REST APIs the same as "Microservices"?
Other than a possible mess, what kind of architecture am I explaining? I want to use REST because other than myself using the API, others can as well. I can simply return JSON to them (and my application).
EDIT: Here, http://www.martinfowler.com/articles/microservices.html, one of the statements Martin Fowler makes several times is, "With a monolith any changes require a full build and deployment of the entire application." What does this mean? If I build a web application and change a Title, I don't rebuild anything. I now that's simplistic, but say I have a model, I change my SQL to get a new column. I put a new bit of Javascript and HTML and I'm done. I am not saying that's good, just that it happens, and I'm not sure why what Martin Fowler says here affects me.