Hecate : integrated db infrastructure project

• Statistics Agent (MySQL) - collects CPU, RAM, Load, MySQL statistics and ships this to Pool Registry service via SOAP call (see attached src.rpm);
• Pool Registry service - keeps track of database pools (stats per node), provides load balancing and data transfer capabilities via exposed SOAP interface;
  • Pool Manager - keeps track of database pools;
  • Pool Registry Web UI - displays currently available pool list, node status, works as monitoring UI for collaboration;
  • Fast In-Memory Cache - reduces the Pool Registry <-> Data Source Adapter communications burden;
• Data Source Adapter - announces Pools to Pool Registry, converts "generic" requests for datasets into db-specific commands, sends serialized data back to Pool Registry;
  • (de)serialization Factory - converts dataset requests into DB queries, serializes DB response;
  • DB native cache - provides caching capabilities, native to DB used in Pool;
  • Local Disk Cache - persistent local cache
• Client Application - makes requests for data, using SOAP calls to Pool Registry. Data is fetched from either local or remote pool, transparently.
  • Two-way db access - direct local db access interface + distributed data access interface;
  • Local Load Balancing Interface - direct db access interface requires local load balancing information, retrieved from Pool Registry;
  • Local Disk Cache - persistent local cache, reduces the Client App <-> Pool Registry communications burden;