You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Started as "Ancillary Marten stores don't necessarily use the correct message database in inbox/outbox operations"
This is really becoming a "make Wolverine awesome for modular monoliths" by making it possible to more readily mix and match different message stores and durability agents within the same application. So:
Readily use separate Marten stores, but "know" how many unique message store databases there are and make sure you're always using the right one
Mix & match Marten & EF Core against the same postgresql database
Use completely separate Marten stores or EF Core DbContext in the same app pointed at different logical databases
Mix & match RavenDb & Postgresql & Sql Server in the same app
Accomodate multi-tenancy too
The envelopes are going to the correct database schema, but the DurableReceiver and durable sending agents aren't using the correct databases.
Only really an issue for local queues where messages are sent as part of a message using the ancillary store
The text was updated successfully, but these errors were encountered:
Basic issue is that the ancillary store is being more or less ignored and still using the main postgres message store. No big deal if you're all on the same database, but still.
jeremydmiller
changed the title
Ancillary Marten stores don't necessarily use the correct message database in inbox/outbox operations
More flexible mix & match options for message stores in the same application
Jan 10, 2025
Started as "Ancillary Marten stores don't necessarily use the correct message database in inbox/outbox operations"
This is really becoming a "make Wolverine awesome for modular monoliths" by making it possible to more readily mix and match different message stores and durability agents within the same application. So:
The envelopes are going to the correct database schema, but the DurableReceiver and durable sending agents aren't using the correct databases.
Only really an issue for local queues where messages are sent as part of a message using the ancillary store
The text was updated successfully, but these errors were encountered: