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

new illustration

Browse Source
This commit is contained in:
Philip Sargent 2024-03-05 16:57:21 +00:00
parent e1eb0ad413
commit 7051fc8273
2 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
handbook/troggle/legacy-replace.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 44 KiB

13
handbook/troggle/trog2030.html
View File

@ -7,6 +7,7 @@
</head>
<body>
<style>body { background: #fff url(/images/style/bg-system.png) repeat-x 0 0 }</style>
<style>figure {font-weight: bold; font-size: small; font-family: sans-serif;font-variant-caps: small-caps;}</style>
<h2 id="tophead">CUCC Expedition Handbook</h2>
<h1>Troggle in 2025-2030</h1>
@ -24,6 +25,18 @@ there is such a lot going on we would create a large volume of software even if
<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>.
<div class="onright">
<figure >
<a href="https://martinfowler.com/articles/patterns-legacy-displacement/">
<img width=350 src="legacy-replace.jpg"></a>
<br><figcaption>Legacy Replacement underway</figcaption>
</figure>
</div>
</a>
<h3>Option 2</h2>
<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().