n8n is actually used for many workflows, specific to healthcare and the supply chain industry, though I cannot say anything specific and must remain abstract.
I have used n8n to connect diverse applications across different operating systems and different API calls. However, I am yet to see direct access to queues and Kafka queues.
The best features of n8n are its low-code capabilities with everything at your disposal. The connectors are getting enriched, which is beneficial. It's all about these low-code tools. I don't see any difference between this and classical EAI; it's a kind of integration where we are doing extensive integration with different sources and targets, and here we are interacting with different sources and targets to apply the enriched data to the models and everything so that it makes better decisions.
They haven't fully helped tailor solutions for our needs. We need to make adjustments, enhancements, and create custom workflows. I'm not saying it is completely ready at this time, but it solved most of our purposes. You cannot ask for everything as these products are getting to a matured stage, so we have to give some time for them to reach maturity.
Regarding integrations, if they can make it more seamless and beef up their workflow constructs, that would be great.
Another improvement would be in making n8n more popular through a similar approach to Kafka's documentation. Kafka has created ten-minute capsules of every use case, covering basics, foundational concepts, and each construct in detail. If a newbie spends at least a week studying the documentation, they'll be equally proficient. Any experienced person, senior developer, or architect who goes through Kafka's documentation and videos will have a good jumpstart. If n8n applies a similar methodology, that would benefit the entire community and help them grow faster.
I have experience with n8n for approximately one plus years.
The initial setup was not complex; it was straightforward.
I did not get much opportunity to deal with their customer service or technical support for n8n.
I deployed it alone.
As a chief principal architect, I maintain a hands-on approach to implementation.
The documentation in general was adequate, though it could definitely be better. However, it was decent enough for what I needed.
On a scale of 1-10, I rate n8n a seven out of ten.
