3.

Data Blending:
Both Alteryx and KNIME provide great tools for combining data, however the
ease of use varies between them.
KNIME: The join node is easy to understand and can combine datasets off a
shared identifier. We can choose the columns from each data set in the result.
Some of the joins such as left and right joins can be a bit tricky since there are
no options for left or right join in the JOIN node.
Alteryx: The Join tool works similarly to KNIME. Users can simply choose the
identifier to link the datasets together. It allows users to construct SQL queries
without writing a line of code. However, Alteryx has included some higher
level-functionality by combining analysis tools that make sense to work
together. However, this doesn’t always provide the expected user-experience,
which can cause trouble with larger data sets. For example, Alteryx chose a
method for simplifying the analyst effort by using UNION features in SQL with
the JOIN tool (including inner and left/right joins). This means Alteryx performs
all the joins without specifying a join type. This is great for smaller datasets but
for larger data sets this could be time and resource consuming as Alteryx
needs to process all joins to complete the processing. KNIME, on the other
hand, is completely modular and treats each activity as a discrete activity in a
separate node and can be completely managed by the ETL designer This
requires the ETL designer to be more technically proficient in KNIME, but
allows more control and can avoid some of the excessive processing and
resource consumption in large data sets that occur in Alteryx.

Verdict: