>> If (2) can give near-to or similar performances as (3), it will be >> BRILLIANT as it means a lot less re-development time.
>Ya, I would personally would focus on (2) until I had proved that it is >not otherwise feasible as it would be a lot quicker to implement... Contrary to Michael's suggestion, I'd high suggest you bite the bullet and make the transition into a proper pub-sub design. By focusing on (2) you'll end up dragging over both your DB because the nature of your application is a lot a lot of updates, but only limited queries (oops.. am I supposed to say this here) So if you're dumping massive amounts of RSS feeds into the DB, while only processing for the web interface occasionally (when the user request for data), I highly suggest that you create a small replica (possibly with a slightly different schema suitable for the GUI), and get your RSS db to publish changes to the small replica. From there it's your choice on whether to make it an app level thing or a DB "transform"... -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Clark Sent: Wednesday, July 22, 2009 2:13 PM To: [email protected] Cc: slugnet Subject: Re: [Slugnet] Advise Needed on DB Design (PostgreSQL on Debian Lenny) _______________________________________________ Slugnet mailing list [email protected] http://wiki.lugs.org.sg/LugsMailingListFaq http://www.lugs.org.sg/mailman/listinfo/slugnet
