Persistence must be treated as an integral part of the design effort, and close collaboration between designers and
database designers is essential. Typically the database designer is a 'floating' resource, shared between several teams
as a consulting resource to address persistence issues. The database designer is also typically responsible for the
persistence mechanisms; if the persistence mechanism is built rather than bought, there will typically be a team of
people working on this. Larger projects will typically require a small team of database designers who will need to
coordinate work between both design teams and amongst themselves to ensure that persistence is consistently implemented
across the project.
|