thanks for the hint. sounds like an interesting book. i think the rails-as-a-database-wrapper idiom is spread way too far. sounds like you managed to get away from that though :)
i know the idea of being able to model your domain objects without having to worry about persistence and slap on the database afterwards sounds tempting. i would still argue that the database you choose has an impact on your domain models - depending on what your specific database is good at you still have to make sacrifices or do things a certain way - which you have to take into account.
aimee
· 8 months ago
True, you have to take everything together as a whole. Much as we might focus on different layers of the architecture at a time, they come together to form an overall picture. Some projects are fine with Sqlite, some are suited to MySQL, and some would work well with CouchDB.
Thanks for commenting, and i enjoyed reading your article.
Versace Sunglasses
· 4 months ago
Great post.. And I agree with your thoughts especially with your last paragraph... Thanks for information you've given.. I will back for more..
adsl viettel
· 4 months ago
It's hard to find quality information like this, I'm glad i found this, thanks for the valuable information.
massagers
· 4 months ago
You are doing a great job, keep impressing your readers.
Robert
Self Storage
· 2 months ago
Indeed, as a reader to this blog I am truly impressed, have been coming across posts that are so very informative for me, keep impressing us!
Dave
Neuseeland
· 3 months ago
I had far more success with couchrest which is a much closer CouchDB wrapper, enabling CouchDB to be used as it's intended: as a RESTful interface with map/reduce views.
I've made the same experience.
Daniel
· 1 month ago
This is my first time i visit here. I found so many interesting stuff in your blog especially its discussion. From the tons of comments on your articles, I guess I am not the only one having all the enjoyment here! keep up the good work.
ADSL Viettel
· 1 month ago
It's hard to find quality information like this, I'm glad i found this, thanks for the valuable information.
All Comments
i know the idea of being able to model your domain objects without having to worry about persistence and slap on the database afterwards sounds tempting. i would still argue that the database you choose has an impact on your domain models - depending on what your specific database is good at you still have to make sacrifices or do things a certain way - which you have to take into account.
Thanks for commenting, and i enjoyed reading your article.
Thanks for information you've given.. I will back for more..
Robert
Dave
I've made the same experience.