Overview of ECO Features
ECO promotes the N-Tier approach to ensure that your applications are well structured and easier to maintain, however, in ECO there is no need to develop the data access layer as ECO possesses this ability internally. ECO has numerous persistence abilities, including:
- Load / save to a local XML file.
- Load / save to numerous SQL databases as standard (SQL Server, InterBase, Firebird, MySQL, DB2, and more).
- Automatically generate the DB schema of a SQL database from the model.
- Automatically upgrade (evolve) the DB schema based on changes to the model whilst preventing data loss.
- Load / save objects across multiple persistence stores, including the ability to save to mixed DB servers or to save using distributed transactions (SQL Server).
- Map objects to / from an existing database structure by providing XML mapping information.
- Use a remote ECO persistence server so that no DB server components or database credentials are required on the client, the server may switch to a new persistence storage without having to update the clients.
- Reverse engineer an existing database in order to create a business model.
The aforementioned features are usually provided by a custom data access layer written by the developer, usually the data access layer written does not provide all of these features and may take a considerable amount of time to develop. ECO's persistence abilities will inevitably save many hours of development, in fact a simple business model can be created, the code generated, and a database created to persist the business objects in less than five minutes.
ECO provides the developer with much more than a way to easily persist business objects within a persistence storage. In addition to the data access layer ECO consists of a number of service modules which combine to create an impressive set of tools which aid the developer in creating robust applications in a much shorter timeframe.
Overview Copyright Capable Objects 2007.