Ayende @ Rahien

Hi!
My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:

ayende@ayende.com

+972 52-548-6969

, @ Q c

Posts: 5,971 | Comments: 44,508

filter by tags archive

Comments

Matt

Hmmm ... starting simply (and assuming your contending resource is a DB table):

BEGIN TRANSACTION

Ayende Rahien

Matt,

I need to avoid doing a database - wide lock, which is what would happen when those monsters are running.

I also need to touch more than a single DB / resource, and a distributed transaction is not an option here.

Mats Helander

Your situation warrants re-inventing distributed transactions, but not using them ?

/Mats

Ayende Rahien

Mats,

Absolutely not!

I just need to ensure a serial execution of packages, nothing more. Transaction semantics are need to be more fine grained than a transaction per the entire package.

I wanted to know if there was a builtin way to provide the: "when package A runs, wait to run B, and vice versa"

Ayende Rahien

Perhaps a better term is:

Do not run packages A,B,C in parallel

Rémy

You can create a third package that runs those two packages in serial. For the one, you only want to run once a hour, you use some variable or if-statement,

Comment preview

Comments have been closed on this topic.

FUTURE POSTS

  1. Paying the rent online - 3 days from now

There are posts all the way to Aug 03, 2015

RECENT SERIES

  1. Production postmortem (5):
    29 Jul 2015 - The evil licensing code
  2. Career planning (6):
    24 Jul 2015 - The immortal choices aren't
  3. API Design (7):
    20 Jul 2015 - We’ll let the users sort it out
  4. What is new in RavenDB 3.5 (3):
    15 Jul 2015 - Exploring data in the dark
  5. The RavenDB Comic Strip (3):
    28 May 2015 - Part III – High availability & sleeping soundly
View all series

Syndication

Main feed Feed Stats
Comments feed   Comments Feed Stats