I suspect this is because Google+ presents a fundamentally different type of server load than Google's other services. While others are definitely read-mostly to a large extent, the social network is very transactional - people write things all the time. This cannot be handled by map-reduce :)
While other Google's services are also user-modifiable - Mail, Docs, even Buzz, it looks kind of like they were not ready for the torrent of small transactions coming in. This is not search. This is more like Twitter processing than bulk read-only queries.
Of course, Google being what it is, it will no doubt be fixed soon.
Post your comment here!
Comments are subject to moderation and will be deleted if deemed inappropriate. All content is © Ivan Voras. Comments are owned by their authors... who agree to basically surrender all rights by publishing them here :)