How to visualize platform differences
We are in the process of modernising our application stack and have a mix of legacy and modern systems. I'd like to create some visualization to compare systems, but I'm pretty much stuck in the starting blocks.
Let's take an example with four applications. They all have dependencies on either the old or new data layers, API platforms, UI platforms and CSS frameworks.
As an example, let's say the systems have these dependencies. System 1 is the oldest and System 4 is the newest (and the stack we're moving towards):
System 1 System 2 System 3 System 4
Data Layer old old old new
API platform old old new new
UI platform old new new new
CSS framework old old new new
This fairly naive table works, but is limited as you scale to more systems or layers and completely dies when you have more than just two versions of a component or use combinations (for example, a system could use some of the old APIs and some of the new ones).
I'm ready to just brute force it into this table format, but is there a simpler or more intuitive way to represent this kind of data?
visualization
add a comment |
We are in the process of modernising our application stack and have a mix of legacy and modern systems. I'd like to create some visualization to compare systems, but I'm pretty much stuck in the starting blocks.
Let's take an example with four applications. They all have dependencies on either the old or new data layers, API platforms, UI platforms and CSS frameworks.
As an example, let's say the systems have these dependencies. System 1 is the oldest and System 4 is the newest (and the stack we're moving towards):
System 1 System 2 System 3 System 4
Data Layer old old old new
API platform old old new new
UI platform old new new new
CSS framework old old new new
This fairly naive table works, but is limited as you scale to more systems or layers and completely dies when you have more than just two versions of a component or use combinations (for example, a system could use some of the old APIs and some of the new ones).
I'm ready to just brute force it into this table format, but is there a simpler or more intuitive way to represent this kind of data?
visualization
add a comment |
We are in the process of modernising our application stack and have a mix of legacy and modern systems. I'd like to create some visualization to compare systems, but I'm pretty much stuck in the starting blocks.
Let's take an example with four applications. They all have dependencies on either the old or new data layers, API platforms, UI platforms and CSS frameworks.
As an example, let's say the systems have these dependencies. System 1 is the oldest and System 4 is the newest (and the stack we're moving towards):
System 1 System 2 System 3 System 4
Data Layer old old old new
API platform old old new new
UI platform old new new new
CSS framework old old new new
This fairly naive table works, but is limited as you scale to more systems or layers and completely dies when you have more than just two versions of a component or use combinations (for example, a system could use some of the old APIs and some of the new ones).
I'm ready to just brute force it into this table format, but is there a simpler or more intuitive way to represent this kind of data?
visualization
We are in the process of modernising our application stack and have a mix of legacy and modern systems. I'd like to create some visualization to compare systems, but I'm pretty much stuck in the starting blocks.
Let's take an example with four applications. They all have dependencies on either the old or new data layers, API platforms, UI platforms and CSS frameworks.
As an example, let's say the systems have these dependencies. System 1 is the oldest and System 4 is the newest (and the stack we're moving towards):
System 1 System 2 System 3 System 4
Data Layer old old old new
API platform old old new new
UI platform old new new new
CSS framework old old new new
This fairly naive table works, but is limited as you scale to more systems or layers and completely dies when you have more than just two versions of a component or use combinations (for example, a system could use some of the old APIs and some of the new ones).
I'm ready to just brute force it into this table format, but is there a simpler or more intuitive way to represent this kind of data?
visualization
visualization
asked Nov 13 '18 at 13:17
Cobus KrugerCobus Kruger
4,93634281
4,93634281
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53281862%2fhow-to-visualize-platform-differences%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53281862%2fhow-to-visualize-platform-differences%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown