If you have spent any time writing Object Oriented PHP or Drupal PHP you will know that there are many instances where it can be handy to know exactly what you are dealing with at a specific point in your code. For example, possibly you are troubleshooting an issue and cannot figure out why a variable is not acting as it should, or maybe you are writing logging routines to make sure all of your exceptions are logged for future troubleshooting. Whatever your needs may be it can be very helpful to use PHP Magic constants to assist you in your troubleshooting.
In the last couple of years I have been involved with a lot projects all with the same type of scenario, there is a server housing a content management system or a database, a remote mobile application that reads data from the server, and usually a web application for anonymous and authenticated web traffic. Projects like this are extremely interesting, but can get very complicated in a hurry as the project evolves and features are added on either the web side or the mobile application side.
In part one of this post I explained the need to have a content management system detached from the web service. In part two of this post I explained how to sync the data from Drupal to MongoDB and sync it in a way that left Node.js to just read the data and serve it. So now in part three of this post the only thing left to do is build the web service to serve the read-only data on.
In part one of this post I explained the need to have a content management system that was detached from the web service. In explaining this need I also described how I am going to use Drupal for the CMS, MongoDB for the secondary data store, and Node.js as the web service platform. Now it is time time for the fun part, setting up our integration! In this post I will demonstrate how to take your existing Drupal CMS and integrate it with MongoDB to take the first step in building out data for your web service.