And all the transactional challenges that having more than one persistent store brings with it. Either need to have XA orchestration or implement the saga pattern. Either way it's a massive complexity overhead if transactional consistency between the queue and your database is important for your application.
Comments
And all the transactional challenges that having more than one persistent store brings with it. Either need to have XA orchestration or implement the saga pattern. Either way it's a massive complexity overhead if transactional consistency between the queue and your database is important for your application.
it’s usually done using the outbox pattern.
i’m not sure if this pattern can be called a type of saga.
you basically have a tiny queue in you db using a special table that you drain to an external queue server.