Oracle headquarters buildings: http://en.wikipedia.org/wiki/Oracle_Corporation#mediaviewer/...
The typical symbolic representation of a database in a diagram: https://openclipart.org/detail/181674/database-symbol-by-ete...
Sounds similar to:
> Bad programmers worry about the code. Good programmers worry about data structures and their relationships. -- Linus Torvalds
And I totally share the hopes for the current eventual consistency monopoly to perish. Some use cases should use strong consistency. You see people build stuff like this https://github.com/Netflix/s3mper to "fix" eventual consistency...awkward
You can, of course, handle the concurrency on the application level, but the question is, why bother? The database can help with managing that.
Nobody wants to throw data away on concurrent writes, and CRDTs or application specific merge functions are complicated.
I don't really see much of a relationship to unix text stream processing. Maybe in something like a Kafka -> Samza -> Kafka style system -- but even then, it feels like a stretch. There's much more of a focus on the ordering of messages rather than the concept of log here, process there.