New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sql Server Backed Message Persistence #259

Closed
jeremydmiller opened this Issue Nov 29, 2017 · 3 comments

Comments

Projects
None yet
1 participant
@jeremydmiller
Contributor

jeremydmiller commented Nov 29, 2017

@mike-schenk Just splitting this out. Also includes:

  • Scheduled job support
  • Retry & ScheduleAgent's like the Marten backed version
  • Might wanna split out the outbox as a separate issue
  • Schema management?
  • Outbox support too

I think we'd do the outbox with Dapper for now because that's what we'd likely want to use at work, but look to add an EF Core based outbox later.

@jeremydmiller jeremydmiller added messaging and removed messaging labels Nov 29, 2017

@jeremydmiller jeremydmiller added this to the 0.8 milestone Apr 11, 2018

@jeremydmiller

This comment has been minimized.

Contributor

jeremydmiller commented Apr 17, 2018

Notes:

For the advisory locks, Sql Server supports the sp_getapplock and APPLOCK_TEST functions that seem to be the rough equivalent to what we do w/ Postgres.

@jeremydmiller

This comment has been minimized.

Contributor

jeremydmiller commented Apr 17, 2018

Most of this work is probably going to move to #362 and #363. What is definitely different is the advisory locking inside of the RetryAgent.

@jeremydmiller

This comment has been minimized.

Contributor

jeremydmiller commented Apr 25, 2018

I'm shrinking the story again to calve off the schema mgmt support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment