Re: db vs. db
- Posted by Pete Lomax <petelomax at blueyonder.co.uk> Jun 19, 2003
- 458 views
On Wed, 18 Jun 2003 15:15:02 -0500, "C. K. Lester" <cklester at yahoo.com> wrote: <Disclaimer: I'm only guessing here ;-> > >What makes Tsunami better than EDS? Adding thousands of records and/or having it permanently running on the server (eg linked into Apache/whatever). IIRC, It is also a proper database system (see below re eds) >What makes MySQL or PostgreSQL better than Tsunami or EDS? Openness. Any platform, and very nearly all programming languages can submit an SQL query string. Theoretically the slowest of all interface mechanisms for dumb queries and actually/obviously the fastest of the lot for detailed/intelligent queries. >What makes [your favorite db] better than [any other db]? Because it has a pink [insert you favorite colour here] logo > >What's the best for web serving? I'm hoping to have a EUPHORIA-driven = web >site soon, and it's also going to be database driven. Will EDS suffice = for >one hit per second? a billion hits? eds will almost certainly be the fastest for small data sets, especially if the database engine itself is reloaded for each web hit. SQL would probably take 20 seconds to load on my (slow, ancient) machine, but is definitely bog-standard [available if not always enabled] on almost all web servers. You'd have to check Tsunami support yourself. I don't think very many web servers will cope with a billion hits per second. A bankload of routers in front of a server farm, perhaps. >What's the best (if anything) for small-app, not-web-related, data >management? there is a much shallower learning curve on eds for simple databases; however bear in mind that you cannot specify multiple indexes or any dbms-understood relationships within your data; they all have to be coded by hand. EDS keys and data also are totally unnamed which is initially easier but later on will dump that responsibility right back on the programmer. If you don't know eds, you should learn it anyway. Sadly, E.F. Codd died earlier this year. A lot of his stuff was deeply theoretical, but if you are at all interested in creating and defining databases you really ought at least get a gist of his ideas. I'm sure you will find thousands of references via Google. Pete