My SF Project
I'm currently on a project in San Francisco involving lightweight web services, as described here by IBM. At the moment the app is all about handling HTTP posts for hub connecting data providers and consumers. It's pure perl, running behind apache on Linux, and we plan on stealing lots of p5ee ideas, esp. since the other architect comes from more of a Java background.
The other architect and I started the design assuming we'd use the existing SQL Server 7 infrastructure for storage, but as we went along there seemed less and less reason to do so. We use DTS (Data Transformation Services) which I'm a big fan of, and I had envisioned using OLAP/Analytic Services when a decent amount of data had been collected.
But it seemed to make more and more sense to just ditch SQL Server and go Postgres all the way around. Ironically, I'm a big Pg booster, but I'm pretty conservative when it comes to suggesting that a company change it's db, so this wasn't my idea. I did not broach the idea, and actually played devil's advocate most of the time, but I couldn't come up with anything really compelling.
The other architect and the sysadmin were actually more eager to get away from stupid Frontpage extension vulnerabilities (IIS) and licensing costs (windows advanced server/SQL 7) that aren't too bad, but become onerous quickly in multi-cpu, multi-datacenter setups. It's a small company, and a brand new application without integration requirements, and staff with OSS grounding, so we've got no reason not to go free.
1:15:41 PM 
|
|
