Skip to content

Fix dead link in docs #1274

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.

Sign up for GitHub

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

Merged
jeremydmiller merged 1 commit into from
Feb 13, 2025
Merged

Fix dead link in docs #1274

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/tutorials/modular-monolith.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -415,7 +415,7 @@ in the same database schema and use the same `IDocumentStore` if you want while
later if you choose to sever some modules over into a separate service. With the event sourcing though, all the events for
different aggregate types or stream types all go into the same events table. While it's not impossible to separate the events
through database scripts if you want to move a module into a separate service later, it's probably going to be easier
if you use [Marten's separate document store](/configuration/hostbuilder.html#working-with-multiple-marten-databases) feature.
if you use [Marten's separate document store](https://martendb.io/configuration/hostbuilder.html#working-with-multiple-marten-databases) feature.

Wolverine has [direct support for Marten's separate or "ancillary" stores](/guide/durability/marten/ancillary-stores) that still enables the usage of all Wolverine + Marten
integrations. There is currently a limitation that there is only one physical database that shares the Wolverine message storage for
Expand Down
Loading