Serialized transaction question

Hi NexusDB team,

I have been monitoring the progress of NexusDb for a few months, and I
am very impressed at what you guys are doing for the Delphi community.
NexusDb combined with Delphi/CBuilder looks like the perfect match for
almost any data related application, from small to large.

Currently we have invested greatly in Pervasive.SQL having written an
application for more than 10 years with over 1 million lines of code. It
is mostly based on the legacy Btrieve API. Performance is great, so is
stability, but NexusDb is so tempting as a future and long term
alternative with its long list of advantages.

My question is on serialized transaction model, which from what I
understand is used by NexusDb.

One typical operation is to modify the price rates of many clients at a
time. Say 500 clients, 200 rates, so grossly put updating 100000 records
obviously in a transaction, because the user requests this as a single
operation, so if a failure occurs, everything must be rollbacked and
restarted.

From what I understand, a transaction on a table in NexubDB will block
others from writing/updating the same table. So if a transaction takes a
few minutes, everyone else is blocked from modifying on the tables part
of the transaction. I am correct on this assumption, and if so, is the
ability to have concurrent transactions on the same tables something
that will be looked at in the future?

With many users, this will be a bottleneck; no matter how fast NexusDb
is, everyone else has to wait. I understand the argument of making
transactions as small as possible, but even transactions in the seconds
range will have a serious impact when there are many users because of
the serialized nature.

Thanks,

Michel