As a blogger, I am interested in how Google finds and indexes my blog.
Google's web search found my blog very quickly, even if no external incoming link was available. I would assume Google uses domain registration information to find new domains. Besides, since I have an AdSense account, it can be a plus.
Google Blog Search is an RSS-based. It extracts some basic entities like "update time" and "blogger name" from the RSS feed. Google's blog search might get feeds from its web search database. With some kind of filtering, these feeds are sent to a special RSS crawler. Google also uses ping service to track newly published blog posts.
As you can see from the figure below, my post was indexed within 7 minutes after it was on the web! But when I searched "answersy," this result did not show up. Only when I click on the "Last hour" link, was I able to see it.

Since wordpress ping tells Google when a blog was updated, Google blog search sends crawler right away to fetch the RSS. I looked at my access log, and confirmed that Google bot crawled my RSS in less than a minute. The mysterious part is Google's indexing turn -around time. To be able to serve the results in less than 10 minutes, Google must be keeping a relatively small database. As we know, a database can be optimized either for data manipulation or for query. Only when it is small, can it achieve good performance for both.
Another thing I noticed was Google did not fetch the post page itself. It only indexes the description in RSS.
I then do the query again and click the "Last hour" link, this time I got the following no result page!

My guess was that the previous result got pushed out from that small super-fast database, and it will take a while before it can be re-indexed by the main cluster :−)
Then I added THIS post and searched again. This time I saw THIS post itself while the previous one was still missing.

By any means, I have to say Google's crawler and indexer work really hard. In the meanwhile, I also found Google blog search is still not as good as I expected. It has some inconsistent behaviors from the view point of end users.