Graph for data integration page

[iskerrett]

Related Issue

554

Description

Require a graph for the data integration page. HEre is a rough mockup.

[joepavitt]

Thanks Ian - just an fyi when you put the number of the linked issue or Pull Request in a comment or description on GitHub, if you do:

#554

instead of just

554

GitHub automatically turns that into a link directly to the issue.

[joepavitt]

First pass - still quite word heavy, would be nice to add some more illustration/graphical element to this - any ideas @Yndira-FlowForge? I've added a variant in FlowForge if you want to go play

[joepavitt]

very quick variation:

[iskerrett]

fwiw, I see these types of diagrams are typically better oriented left to right than up and down. I would typically use a layered approach for a platform architecture. This diagram is trying to convey a process.

[joepavitt]

yeah, that was my original plan, and something I'll definitely re-visit.

With the amount of content we had in each section, and how they're split, the layered approach definitely fit the content/space better, but you're absolutely right, it does now read architecture rather than process.

[joepavitt]

horizontal variant:

also halfway through a variant with logos/icons instead of text:

[joepavitt]

full logo example, going to move these over to the horizontal variant and that'll likely finish it off:

[joepavitt]

feedback when you get the chance please @iskerrett

[joepavitt]

lighter palette for the visualisation section:

[iskerrett]

I like the lighter palette one. For the storage, I am not sure where you got the list of databases. From the Node-RED community survey we know the popularity of database with NR use is as follows: InfluxDB MySWL PostgresSQL SQLite Mongodb MS SQL Redis TimeseriesDB DB2 MariaDB Cassandra LevelDB.

FWIW, I would not include the last four since it was minimal usage.

I also think we should include the AWS, MS Azure logos since a lot of people use those cloud platforms.

I would remove the AlaSQL, IBM, Firebase and Claris logos.

[joepavitt]

I am not sure where you got the list of databases

I got the list from here - most popular downloaded database nodes in NodeRED: https://flows.nodered.org/search?term=database&type=node&type=flow&type=collection&sort=downloads&page=1

will add Redis though as I'd missed that one

[joepavitt]

I also think we should include the AWS, MS Azure logos since a lot of people use those cloud platforms.

They're already in there

[joepavitt]

@iskerrett updated storage list to include Redis, SQL Lite, PostgreSQL, and removed AlaSQL and Claris:

[iskerrett]

I would drop Firebase and IBM Cloudant. I can only imagine IBM is there due to the Node-RED legacy.

From a marketing perspective we should be focused on databases that have broad appeal.

[joepavitt]

I'd argue Google Firebase was fairly broad appeal? Happy to remove Cloudant, although may appeal to anyone transitioning away from IBM Cloud for NR Hosting, but doesn't want to lose data, still stored in Cloudant? It also isn't taking up any additional space, would otherwise be empty whitespace, or do you have a preferred replacement?

[joepavitt]

further iteration cleaning up the styling consistency further:

[iskerrett]

Do you have any market share numbers for Firebase. In the IoT world I have never heard it mentioned. How about just include the Google Cloud logo instead of Firebase.

This page is not geared to people already using Node-RED on IBM Cloud so I would drop IBM Cloudant. I think it actually sends the wrong signal that we are looking back at IBM.

[iskerrett]

Here is Stack Overflow DB numbers. Firebase is pretty low down so I don't see it warrants inclusion. https://survey.stackoverflow.co/2022/#most-popular-technologies-database

[joepavitt]

How about just include the Google Cloud logo instead of Firebase.

done

so I would drop IBM Cloudant

done

[joepavitt]

now down to two variants. Think the lighter variant feels a little too "cuddly" and cosy, tried to user the darker tone to make it a bit more professional.

[joepavitt]

a little mix which tries to enforce that the protocol isn't a target in the process, but part of the flow between format and compute/storage

[iskerrett]

I leave it to you to decide which is the best. I agree we should be aiming for professional, industrial, not cuddly. :-)

[joepavitt]

Added in #672