Object Oriented

During the Data Architecture Design Sprint (or DADS, as I will henceforth call it), we discussed two general models for reaching our vision of "data anywhere, value-add anything". Those models became dubbed "Model 1" and "Model 2", because that's the order in which we happened to write them down.

Barry has already done a good job of explaining Model 1 in an earlier post. Here, I am going to lay out the structure of Model 2. I suspect that the final system, whever it looks like, will draw heavily from both models.

I have been pondering the question of a data API for a while, as have a lot of people. Much of the recent discussion has focused on an Active Record approach to a data API. Now, Active Record is a very powerful architectural pattern. It maps nicely from storage to interface, it can be fairly self-documenting, and it is conceptually simple and approachable.

It is also, I believe, insufficient.

I am in need of as Senior a DRUPAL expert as we can find for a LONG term and ongoing CONTRACT situation. All work is TELECOMMUTE 100% from your home office. A very very robust undertaking that uses Drupal CMS at its core. Contract could literally run well into 09 . This project is REALLY funded and the corporation understands MARKET RATE. I have 2 consultants working on this project now and I have a long and successful relationship with the hiring authorites. They use only me to find talent for these roles and trust me as I do them. This one is a real as they come.