Link Details

This was kind of interesting. Really though I think, at least for the java world, it is simpler than the author makes it out to be, but only if you are using something like JPA/Hibernate. On the handful of projects I've use JPA/Hibernate on I didn't worry about the database until I had the domain model as complete as possible. I run hsqldb as an in memory database to test my relationships. JPA/Hibernate generates my schema for me.

And to say it before someone else does, yes, Grails works the same way. So if the author used something like NHIbernate I wonder if that dismisses his case for an OODB?

I just don't understand why the author insists to say "and for that I bet you think I'm crazy".

Is just another way to leave the real database to the end, whatever is you reason, for example, the comment above. It could be mock DAOs, also, whatever.

He works for Microsoft, so, he's probably not accustomed to developing "the right way".
His sight shows MVC likes it's a big deal (the rest of us have been using mvc for over 10 years, some over 20).