Skip to content
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

Add a 'Migrating Transports' section under 'Transports' #6867

Open
jpalac opened this issue Oct 18, 2024 · 0 comments
Open

Add a 'Migrating Transports' section under 'Transports' #6867

jpalac opened this issue Oct 18, 2024 · 0 comments

Comments

@jpalac
Copy link
Contributor

jpalac commented Oct 18, 2024

There is no overall guidance on what needs to be taken into account when migrating transports, and this is something that a significant number of customers do, especially those moving from on premise to the cloud.

We have a few tools that can help customers when migrating from one transport to another:

It is unlikely that a user will find this information unless they know that the bridge is what they are looking for.

Having a page under the Transports section explaining where to start, what the options are, what to consider, would be a good start.

Consider that when migrating transports, the persistence may also be moving, and what that means in terms of sagas, outbox and subscriptions.

Consider adding any known transport specific "gotchas" or difficulties.

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

No branches or pull requests

1 participant