Not sure I understand the "universal storage" aspect. Is TileDB suitable for real-time workloads — real-time queries, but also real-time updates — as opposed t

Not sure I understand the "universal storage" aspect. Is TileDB suitable for real-time workloads — real-time queries, but also real-time updates — as opposed to batch? Would it be appropriate for storing, say, inverted indexes for text search? Can it be used for secondary indexes, similar to what you'd use B-trees for? Can it store large pieces of data, e.g. large, structured JSON documents? Looks like the open-source version of TileDB is the database engine only, no clustering?