I want such a server 😀 That'd be just awesome!!!

The article was correct but a tad short - it seems like the start of a series. I'd say that it's certainly easier from a developer's point of view to just throw more hardware at the problem for the database and have multiple identical web servers for the presentation layer.

Depending on your application you might be able to get away with some sort of merge replication or bidirectional transactional replication... Merge is probably safest but you'd want to have "sticky sessions" on your web servers so that a user who's working with database A will stick with database A for the duration of their session since their transactions may not have hit database B yet. For "admin" users who wish to see totals, etc they can either be aware of the latency of updates or use views to get bits of data from each database/server.