RE: [patterns-discussion] Lightweight data management patterns

[Phillip A. Lindsay]

Title: Lightweight data management patterns

Hello James, You might find some EAI patterns to be partially applicable in “Enterprise Integration Patterns : Designing, Building, and Deploying Messaging Solutions” ”(http://www.amazon.com/gp/reader/0321200683/ref=sib_dp_pt/102-9810758-0815353#reader-link). Alternatively, you might find interesting what systems folks have done in the event correlation world.  Essentially the real time analysis of online systems for application monitoring and management, processing huge volumes of data (beyond 5800 events a second) with very little resource usage. Most of these systems in this category of scale have home grown systems, some use a mix of async messaging and data collection/correlation services with a periodically bulk loaded dbms in the back for OLAP. Cheers, -phil ([EMAIL PROTECTED])   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Siddle, James Sent: Thursday, June 02, 2005 2:29 AM To: patterns-discussion@cs.uiuc.edu Subject: [patterns-discussion] Lightweight data management patterns   Hi, Firstly, let me introduce myself. I work for Siemens Communications in the UK on a VOIP phone development, and have been interested in patterns for a few years now. My colleagues and myself are currently developing a new software architecture, part of which is the identification and selection of appropriate patterns. The reason I'm posting today is to ask a question - if this isn't the right place for such questions, any pointers to forums or mailing lists etc where I might be able to find an answer would be appreciated. I haven't been able to find much on the 'net so far that matches what I'm looking for, so any help would be great. In a nutshell: I'm looking for "Lightweight data management" patterns. By this, I mean patterns that allow for management of data in an resource restricted, real-time environment. The data may be stored in flat files, or alternatively a lightweight database such as SQLite. Additionally, a number of data management requirements have been identified - so any patterns you have in mind should ideally not conflict with the following list :-) - Fast data access - Single point of access (programmatically) - Simple, easy to use interface - Access control - Data profiles - Data Location transparency - Caching - Change notification / Replication So far, I've identified a number of potentially applicable patterns: Proxy (GOF - to control access to data management services) Observer (GOF - for change notification) Strategy (GOF - to provide different data access algorithms) Lookup (POSA 3 - to provide part of location transparency) So if you are able to add to the list of patterns that we should be considering, please get in touch. Kind regards, James Siddle BSc(Hons) CITP Software Designer SIEMENS Communications 1st Floor, K-Block Technology Drive, Beeston, Nottingham, NG9 1LA, England. *  mailto:[EMAIL PROTECTED] ( DDI: +44 115 943 2313 (Internal 780 2313) 2   FAX: +44 115 943 4969 ü  WWW: http://www.siemenscomms.co.uk Siemens Communications - a division of Siemens plc, Registered No: 727817, England. Registered office: Siemens House, Oldbury, Bracknell, Berkshire, RG12 8FZ. This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the addressee. If you are not the addressee please note that any distribution, reproduction, copying, publication or use of this communication or the information is prohibited. If you have received this communication in error, please contact us immediately and also delete the communication from your computer. We accept no liability for any loss or damage suffered by any person arising from use of this e-mail.

_______________________________________________
patterns-discussion mailing list
patterns-discussion@cs.uiuc.edu
http://mail.cs.uiuc.edu/mailman/listinfo/patterns-discussion