与数据源的松散耦合

Question

First of all I am sorry that I am not able to provide you much details and my question might sound to general.

I am working on a small project but the requirement of the project is bit wired. I have to make the data source switchable. So if I am using Database as a data source now in future it might be able to use a web service or files.

I don't have any clue on how to implement my models so that I can switch the data source without making major changes to the application.

Is there a design pattern or any design practices which I can use to deal with this situation?

I am planning on using Zend Framework.

Thanks for your help in advance.

Answer 1

Take a look at DAOs (Data Access Object). Originally it's existing in the j2ee world but is very simple, thin and usefull.

First you define an interface with whatever function you need:

<?php
interface DAOInterface {
    public function insert($object);
    public function remove($object);
    public function create($object);
}

Then create a concrete implementation of it. This implementation is easily exchangeable with Dependecy Injection (DI). You can have several different ways of storing your data now. You'll always use the interface + DI.

One interface ->Multiple differen implementations / ways of stroing data. Typically one DAO = one database object / table.