By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,213 Members | 1,086 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,213 IT Pros & Developers. It's quick & easy.

Need Expert Advice with decision making

P: 1
G'day Y'all,

I was hoping to get some expert feedback on a proposal I am considering regarding a new internal application to help fill some gaps in our IT department. I have some configuration data that would work well (very well in fact) defined as XML documents and I want to enrich that data with additional User defined information (child and/or attribute) using an XML application.

Document specifics

1. Document size 150k - 300k each
2. Number of documents 30,000 - 40,000
3. Configuration data relatively static < 1000/week element add/mod/del
4. Modification rate/day of enrichment would vary (initial high but eventually low)

Architecture specifics

1. Embedded DB (Oracle Berkeley DB XML)
2. Apache/Perl UI
3. Solaris 10 Sunfire 480R 16G

XML DB Specifics

1. Master DB read/write - used for automation feeds (new configuration data) and UI (forms/updates enrichment data) not performance dependent
2. Sync (not sure if live sync or timed sync)
3. Replicated DB read only - used for high performance XQuery

Application Specifics- Master DB

1. Configuration (raw/un-enriched XML document) accepted - this only happens when config data changes at source or is new
2. Configuration (raw/un-enriched XML document) DB lookup - if exist step 3 else step 4
3. Configuration (raw/un-enriched XML document) compared and differential analysis to create new document add/mod/del
4. If new document add enrichment elements and insert into DB, if modified document delete original in DB and insert replacement document
5. UI to generate enrichment forms across multiple documents using XPath/RegEx/Whatever (not sure yet)
6. UI updates to enrichment elements/attributes

Application Specifics - Replicated DB

1. UI reporter - generate reports with multiple capabilities even across documents based off element/attributes etc... with reports being display using XLS
2. WebSvcs - SOAP interface to extract a single enriched element using Indexed search capabilities in XML database - MUST be fast when queried

What I would like to know does any of the expert XML programmers out there see a problem with my idea for the architecture/DB/application or see any technical difficulties and/or assumptions I am making that probably wouldn't work?

I am looking for real advice from experience as this would be my first attempt going down the XML highway and moving away from a standard RDBMS multi-tiered application...

Any suggestions/recommendations would be greatly appreciated...

Thanks for your attention,
Sep 14 '08 #1
Share this question for a faster answer!
Share on Google+

Post your reply

Sign in to post your reply or Sign up for a free account.