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.

Required fields*

5
  • What kind of storage system is there for the existing application, and which one for the new application? Are you talking about a (central, transactional) database, or something else? Commented Jun 18, 2018 at 18:03
  • 1
    agile favoring working software doesn't preclude a switch-over, you could still have the old one be primary until the new one is ready to be primary, and the old one can be replaced or phased out; I would want to limit the amount of time both are running side-by-side. Commented Jun 18, 2018 at 18:40
  • @doc-brown updated the question with current setup information. Commented Jun 18, 2018 at 18:59
  • @esoterik that surely is an option. Though we'd probably end up making a sync from production to beta so we can see real data in the new application. Maybe post your comment as answer so it can be voted and discussed? Commented Jun 18, 2018 at 19:02
  • If you use a database that supports insert, update and delete operations on views (in conjunction with triggers on those views) you could turn the old schema into views that feed the new tables, thus providing backwards compatibility while letting the database handle the syncing. But then you have 2 problems. Or stored proc's to feed both? Commented Jun 19, 2018 at 0:33