This is significant even in the case of the PIM.
When looking at how to deal with pushing data out to other repositories such as Google, polling data from other repositories such as Google or RSS feeds, and just the general headaches of synchronizing to and from other devices is clear that who gets to touch the database and how is a critical question.
For now, I am assuming that all of the tools that feed to and from other data sinks/sources will do so by operating against the database rather than having the PIM up and running and managing those operations.
1 comment:
I think that's a good assumption, but also implies there should be a "business logic" layer that sits between the both (PIM and sync) and the DB. To do otherwise is to invite inconsistent code creep.
Post a Comment