Charlie; In terms of transaction management, one way to understand it is
that since a relational back-end is used to store all data, the
transactional guarantees from the relational system hold.  I.e., all
changed are executed as fully or roll-back and retry; however the
relational system performs transactions.

Contention (race conditions) are always a problem and the Teamwork platform
was designed to have a easy process for managing changes.

If there are specific scenarios you would like to explore please let us
know.

-- Scott

On Thu, Feb 26, 2015 at 9:50 AM, Irene Polikoff <ir...@topquadrant.com>
wrote:

> Charlie,
>
> I am not sure I fully understand the question, but I will try to answer in
> somewhat high level terms. If you need more details, maybe Scott could
> answer or we could pass your question on to the development team.
>
> As multiple users make edits, these edits are written into a database.
> More than one write transaction could hit the database at the same time.
> These transactions could be queued as we are using write-trough cache, but,
> depending on the scenario, single-writer strategy slows things down. We are
> using multiple write threads to SDB. Even with 'one at a time'
> transactional writes to TDB, there is no guarantee against locking
> contentions.
>
> Irene
>
>
>
> On Feb 26, 2015, at 10:22 AM, Charles Mead <iloveth...@gmail.com> wrote:
>
> Thanks Irene.  A follow-up question is how the transaction management that
> lives in SDB (and that no one here doubts) is (or is not) manifest in EVN
> per se.  In other words, what is the notion of "transaction management" at
> the graph level independent of its commitment to persistence through SDB?
>
> charlie
>
> On Thu, Feb 26, 2015 at 3:54 PM, Irene Polikoff <ir...@topquadrant.com>
> wrote:
>
>> We recommend SDB in the multi user read/write scenarios because it has
>> better support for transactions. If you have a load and read-only scenario,
>> TDB is a good choice. TopBraid includes a streaming data loader for TDB.
>>
>> Note, however, that there are some known issues with TDB on Windows. They
>> have to do with deleting TDBs.
>>
>> Regards,
>>
>> Irene
>>
>>
>> On Feb 26, 2015, at 9:47 AM, Charles Mead <iloveth...@gmail.com> wrote:
>>
>> Are there performance and size metrics available for why one would choose
>> to use one or the other of these approaches as an export/transfer format?
>>
>> Thanks --
>>
>> charlie
>>
>> --
>> You received this message because you are subscribed to the Google Group
>> "TopBraid Suite Users", the topics of which include Enterprise Vocabulary
>> Network (EVN), Reference Data Manager (RDM), TopBraid Composer, TopBraid
>> Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN.
>> To post to this group, send email to topbraid-users@googlegroups.com
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "TopBraid Suite Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to topbraid-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>  --
>> You received this message because you are subscribed to the Google Group
>> "TopBraid Suite Users", the topics of which include Enterprise Vocabulary
>> Network (EVN), Reference Data Manager (RDM), TopBraid Composer, TopBraid
>> Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN.
>> To post to this group, send email to topbraid-users@googlegroups.com
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "TopBraid Suite Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to topbraid-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> You received this message because you are subscribed to the Google Group
> "TopBraid Suite Users", the topics of which include Enterprise Vocabulary
> Network (EVN), Reference Data Manager (RDM), TopBraid Composer, TopBraid
> Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN.
> To post to this group, send email to topbraid-users@googlegroups.com
> ---
> You received this message because you are subscribed to the Google Groups
> "TopBraid Suite Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to topbraid-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>  --
> You received this message because you are subscribed to the Google Group
> "TopBraid Suite Users", the topics of which include Enterprise Vocabulary
> Network (EVN), Reference Data Manager (RDM), TopBraid Composer, TopBraid
> Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN.
> To post to this group, send email to topbraid-users@googlegroups.com
> ---
> You received this message because you are subscribed to the Google Groups
> "TopBraid Suite Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to topbraid-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Group 
"TopBraid Suite Users", the topics of which include Enterprise Vocabulary 
Network (EVN), Reference Data Manager (RDM), TopBraid Composer, TopBraid Live, 
TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to topbraid-users@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to topbraid-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to