expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2024-11-22 07:11:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

Legacy Displacement - online edit of handbook/troggle/trog2030.html

Browse Source
This commit is contained in:
Expo on server 2024-03-05 16:45:25 +00:00
parent 1aa35b274a
commit e1eb0ad413
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
handbook/troggle/trog2030.html
View File

@ -21,6 +21,9 @@
there is such a lot going on we would create a large volume of software even if we stick close to the metal. there is such a lot going on we would create a large volume of software even if we stick close to the metal.
[I could well be wrong. That is Option 1.] [I could well be wrong. That is Option 1.]
<h3>[ Update March 2024 ]</h3>
"Legacy displacement" is now a fairly mature part of software engineering, though most computer science graduates won't have heard of it. There are standard ways of partially and incrementally retiring old systems and replacing them, while maintaining a live service to users throughout. See <a href="https://martinfowler.com/articles/patterns-legacy-displacement/">Legacy Displacement</a>.
<h3>Option 2</h2> <h3>Option 2</h2>
<p> <p>
We keep the same architecture as now, and incrementally replace modules that use django/SQL with direct object storage of collections using pickle(), shelve() and json(). We keep the same architecture as now, and incrementally replace modules that use django/SQL with direct object storage of collections using pickle(), shelve() and json().