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.

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

Jump to bottom

We don't provide any guidance/documentation on how to evolve a legacy system to use messaging #5794

Open
mauroservienti opened this issue Oct 23, 2018 · 1 comment
Open

We don't provide any guidance/documentation on how to evolve a legacy system to use messaging #5794

mauroservienti opened this issue Oct 23, 2018 · 1 comment

Comments

@mauroservienti
Copy link
Member

mauroservienti commented Oct 23, 2018 •
edited by kbaley
Loading

Users that are dealing with legacy systems (or monoliths as we sometimes refer to them) and want to evolve them by gradually moving to messaging find very little, if any, guidance on our doco.

Related to
@mikeminutillo
Copy link
Member

mikeminutillo commented Oct 24, 2018 •
edited by kbaley
Loading

Particular/NServiceBus#6492 is a related idea

@kbaley kbaley transferred this issue from another repository Aug 10, 2021
@kbaley kbaley changed the title We don't provide any guidance/documentation on how to evolve a legacy system to use messagging We don't provide any guidance/documentation on how to evolve a legacy system to use messaging Jul 21, 2022
@kbaley kbaley transferred this issue from another repository Jul 21, 2022
@kbaley kbaley transferred this issue from another repository Jul 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mikeminutillo @kbaley @mauroservienti @helenktsai