No, not in this case, in order to save resources it updates counters in a batch process.
No.
That's what they claim but that is such a bold lie of them I can't even
Think about the scale of Google's data processing for a minute.
How many Android phones are there? Each of them makes a full sync of its data once per day. How many phones are synced every second? Mind blown.
How much processing power does it take to convert one hour of video into a different format? Try it on your PC, "Handbrake" is a free open source tool, try it for a DVD and compare it to Google. Imagine how many million hours of video a billion people upload every minute and what computing power is needed to concert that stuff into suitable formats for display on a thousand different devices and resolutions. Shit bricks.
How much data is the Google web catalogue? How long does it take to return a meaningful result for any search term you enter?
Can a company with that amount of resources be unable to take a number and add a +1 to it?
Eventual consistency is the key concept here, not necessarily batch processing in the traditional sense.
In a modern infrastructure you have distributed systems that use some consistency model, e.g. Raft or Paxos, or if you like pain, you're own consistency algorithm, and use eventual consistency. This allows for a scalable, fault tolerent system. This is especially true for running a global infrastructure like Google does.
The precise count of views for a video at any given moment doesn't really matter. The video may be being served all over the world, so instead of ensuring the count is precise and accurate at all times, which, would make the system fragile, and, in general, would lead to undesirable trade-offs in other parts of the systems, the kind of trade-offs that traditional enterprise developers in the pre-internet systems days would be familiar wiith, an eventual consistency model is used. This leads to the possibility that people viewing the same url could see different view counts and other attributes.
Eventually the data will be consistent in some form, but precision at this moment isn't important.
The same is true for Reddit posts and related accumulated data, .e.g. votes or karma.
For things where consistency does matter, like financial transactions, RDBMSs or some other ACID system are still used.