Well, I have to admit that "Document Oriented Distributed Databases" is an interesting idea. Why don't you try RDDB? After all, it is written in ruby and it is only a gem away. http://rddb.rubyforge.org/
On 4月22日, 上午6時09分, justindz <[EMAIL PROTECTED]> wrote: > Actually, here's a much better answer to your question: > > http://highscalability.com/search-source-data-how-simpledb-differs-rdbms > > Just found that on Hacker News. It's a great overview on how doc- > based differs from RDBMS. It's based on SimpleDB, which of course you > could use today on Heroku but albeit with direct cost from Amazon and > without the nice Data tab as I mentioned above. The main reason I'm > so hung up on Couch is that the view language is javascript and REST- > based, which is conceptually compatible with half of my app. > > On Apr 21, 9:46 am, justindz <[EMAIL PROTECTED]> wrote: > > > XML, no, but in principle you're probably about right. XML would just > > balloon the size of the database without benefit in this case--I'm > > sure it's more like just key/value pairs as usual. The key > > differences that I see are the lack of a schema and the lack of a SQL > > language and joins, all of which adds up to better scalability. > > > The reason it's a Heroku issue is that Rails supports whatever you > > happen to do (it's just easy to use ActiveRecord), ActiveRecord > > supports some RDBMSs and Heroku supports Postgres. Therefore, to use > > something like CouchDB down the road, you would not need Rails to do > > anything (they could, but some 3rd party could write an interface for > > Rails instead) but you *would* need Heroku to include Couch in their > > image and support a connection to Couch in their DB config strategy. > > I suppose you could load a custom image to support it and make some > > kind of outside connection, but then there's the awesome Data view > > which wouldn't work, etc. So it would make most sense as a feature of > > Heroku and it would very much be a non-trivial feature. > > > Hope that was cogent :-) > > > On Apr 19, 11:46 am, mega <[EMAIL PROTECTED]> wrote: > > > > Hi, justindz > > > Is Document-driven databases are something like storing XML in the > > > database instead of columns? > > > I think that is not something related to heroku. It is more like an > > > issue about rails, I think. > > > After all, the ORM of rails isn't built that way. Maybe rails 3.0? > > > > Mega > > > > On Apr 19, 7:49 pm, justindz <[EMAIL PROTECTED]> wrote: > > > > > Document-driven databases are the talk of the town now. Look up > > > > something like CouchDB or read about what Google offers for Google App > > > > Engine via BigTable. They are non-SQL-based databases which claim to > > > > be better suited to high-end scaling and which are schema-less > > > > (meaning, you can change your data structure without having to change > > > > the table definition). > > > > > On Apr 19, 6:12 am, thufir <[EMAIL PROTECTED]> wrote: > > > > > > On Sun, 13 Apr 2008 18:11:16 -0700, justindz wrote: > > > > > > I'm increasingly learning that the battle is not > > > > > > MySQL vs. Postgres but RDBMS vs. the next decade. > > > > > > Huh? RDBMS versus _____? > > > > > > -Thufir --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
