Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • The biggest constraint here is the fact that one of your systems really can't be changed much. Event Sourcing is the design pattern that databases use to handle transaction logs and data synchronization. It's also how version control systems work. However, the fundamental issue is a potential need to merge events from two systems. The events can be projected into the database. Commented Oct 18, 2022 at 21:24
  • Do you have access to the legacy system's database? Is it a SQL database? If so then you can bolt on change data capture to facilitate synchronizing data to an external store that your API can access. Commented Oct 18, 2022 at 22:21
  • @BerinLoritsch thanks. Event sourcing is not an option here. And it would not solve anything without messaging anyway. Commented Oct 19, 2022 at 7:37
  • @ChrisSchaller sounds cool, I've never used CDC before, looks very promising. Thank you! The DB we use in the legacy is Postgres. Commented Oct 19, 2022 at 7:54
  • Just keep in mind that Event Sourcing != Event Messaging. Think database transaction logs. Not saying it's the solution here, but they are not the same thing. Commented Oct 19, 2022 at 11:11