[Schevo-devel] scalability of schevo

[Matthew Scott]

These two go hand-in-hand, I think...

By appropriately restricting read and write access to a database exposed
via HTTP, one could build other Schevo apps that reference one or more
remote databases to augment a local database.


Matthew Scott wrote:
> Process:Database ratio scalability
> ==================================
> 
> ...
>
> Ideally, a client written in any language should be able to connect to a
> Schevo server using commonly-accepted lightweight protocol combos, such
> as HTTP+REST+POX, and then expose an API to the database not unlike
> using Schevo directly.  The server would be responsible for limiting
> read/write access to the database based on context such as a user's
> credentials, location, whatever.
>
> ...
> 
> 
> Transactional scalability
> =========================
> 
> ...
> 
> That is, a database could be designed so that a new "external entity"
> field could reference an instance in another database that was opened
> and associated with the referring database.
> 
> Transactions would be able to cross database boundaries, but would only
> result in a write-lock being obtained on databases that the transaction
> is actively attempting to change.
>
> ...