Skip to content

Fix link for CQRS in Legacy Adapter #15

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

Open
thesammiller wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Fix link for CQRS in Legacy Adapter #15

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9bfd199
Fix link for CQRS in Legacy Adapter
thesammiller Jan 22, 2023
0970dbf
Fix typo
thesammiller Jan 22, 2023
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 Microservices/Legacy-Adapter-Microservice.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,6 @@ However, there are cases where this mapping falls down that must also be handled

So in this case you would build a new REST interface whose URL represents the Transfer type, with a POST operation corresponding to performing a transfer, a GET operation that could return information about a transfer, and a DELETE operation that is a (hopefully well-controlled) undo.

Legacy Adapter Microservices are a special type of microservice in that they are often transient solutions, which only last until the underlying existing services can be replaced by a natively implemented microservice. The [Command Query Responsibility Separation](CQRS.md) pattern is often a part of this transformation in that a Legacy Adapter Microservice may only represent one side (usually the write side) of the process.
Legacy Adapter Microservices are a special type of microservice in that they are often transient solutions, which only last until the underlying existing services can be replaced by a natively implemented microservice. The [Command Query Responsibility Separation](../Coexistence-Patterns/Command-Query-Responsibility-Separation.md) pattern is often a part of this transformation in that a Legacy Adapter Microservice may only represent one side (usually the write side) of the process.

Due to their special nature of converting one interface to another, *Legacy Adapter Microservices* often use [Results Caches](../Cloud-Native-Architecture/Results-Cache.md) in order to reduce the number of times they have to invoke the underlying SOA service that they convert.