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.
n8n is good in terms of usability, functionality, and many different aspects. I am not too sure what needs to be improved in n8n, but regarding the interface, it has a black background, and they could bring in some improvements for user experience. The localized implementation is a bit complex and we definitely need some developers involved within this process. If they make it seamless so anyone who is not technology-savvy can just drag and drop things and do this implementation, that would be very beneficial.
What could possibly be improved in n8n to make this solution better for the next release is still a navigating process for us. I don't think I'm in a position to provide the improvement areas yet because we are still learning and discovering them. Regarding the cost, scalability, and initial setup, I can think that for a bigger enterprise environment, the scalability, based on my observation, could be improved since we haven't fully explored that modular adaptive nature of n8n. There are limitations in scalability.
Integration Platform as a Service (iPaaS) delivers cloud-based solutions, facilitating seamless connectivity across diverse systems and applications. For companies undergoing digital transformation, iPaaS helps streamline integration processes and ensures efficient data flow.Businesses embracing digital innovation leverage iPaaS to improve scalability and maintain agility. The solution supports multiple integration use cases, from cloud to on-premise systems, enhancing operational workflows...
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.
n8n is good in terms of usability, functionality, and many different aspects. I am not too sure what needs to be improved in n8n, but regarding the interface, it has a black background, and they could bring in some improvements for user experience. The localized implementation is a bit complex and we definitely need some developers involved within this process. If they make it seamless so anyone who is not technology-savvy can just drag and drop things and do this implementation, that would be very beneficial.
What could possibly be improved in n8n to make this solution better for the next release is still a navigating process for us. I don't think I'm in a position to provide the improvement areas yet because we are still learning and discovering them. Regarding the cost, scalability, and initial setup, I can think that for a bigger enterprise environment, the scalability, based on my observation, could be improved since we haven't fully explored that modular adaptive nature of n8n. There are limitations in scalability.