Likelihood to Recommend Message brokering across different systems, with transactionality and the ability to have fine tuned control over what happens using Java (or other languages), instead of a heavy, proprietary languages. One situation that it doesn't fit very well (as far as I have experienced) is when your workflow requires significant data mapping. While possible when using Java tooling, some other visual data mapping tools in other integration frameworks are easier to work with.
Read full review If you want to sell online and need a platform, you should select Nexternal. If it is within your budget and you want to have success, Nexternal is the way to go. Since switching to Nexternal from Kreck, our online sales have more than tripled!
Read full review Pros Camel has an easy learning curve. It is fairly well documented and there are about 5-6 books on Camel. There is a large user group and blogs devoted to all things Camel and the developers of Camel provide quick answers and have also been very quick to patch Camel, when bugs are reported. Camel integrates well with well known frameworks like Spring, and other middleware products like Apache Karaf and Servicemix. There are over 150 components for the Camel framework that help integrate with diverse software platforms. Camel is also good for creating microservices. Read full review Page layout. Processing purchases. Ease of creation. Read full review Cons didn't work well when our developers tried to transform heavy data sets Apache Camel's whole logic is based on java so team needs to have a great skill set in java if there are a handful of workflows then Apache Camel's full potential can't be realized Read full review Nexternal is hosted solution which means much of the source code is protected and inaccessible. For clients looking to fully customize the user experience, there are some limitations, with any hosted solution, that must be considered. Nexternal doesn't have a built in wish list feature. They did partner with a 3rd party vendor, and now offer the base functionality; however, for clients whose needs center on the capabilities of a wish list, this feature must be closely considered. Nexternal's monthly fees are structured in such a way that they scale based on sales. This can be an affordable set up for a majority, but a deterrent for others. That said, the phrase 'you get what you pay for' rings true for ecommerce platforms as well. As I've mentioned perhaps too many times already, the level of reliable support combined with the user-friendly, secure platform are worth it. Read full review Likelihood to Renew I no longer work in a company that would utilize it.
Read full review Usability I love the control and attention to detail that this system has. Don't be intimidated by it. Keep playing with it, ask questions, and get to know the program. You will grow to absolutely love and understand it.
Read full review Support Rating We've worked with ecommerce providers for over 12 years, and we have yet to find another solution that provides the same level of responsiveness and accessibility as Nexternal's account representatives.
Read full review Implementation Rating I had help from start to finish. Doreen, my rep, was very patient, concise, clear, and she has always had the answers I need. Setting up your store is time consuming at first, but with the support system that Nexternal offers, it is painless.
Read full review Alternatives Considered If you are looking for a Java-based open source low cost equivalent to webMethods or
Azure Logic Apps , Apache Camel is an excellent choice as it is mature and widely deployed, and included in many vendored Java application servers too such as Redhat JBoss EAP. Apache Camel is lacking on the GUI tooling side compared to commercial products such as webMethods or
Azure Logic Apps .
Read full review When we started with Nexternal, there were not as many options as there are today. We felt the platform was one that we could work with and had a great customer support contact that helped us during the creation of our site.
Read full review Return on Investment Very fast time to market in that so many components are available to use immediately. Error handling mechanisms and patterns of practice are robust and easy to use which in turn has made our application more robust from the start, so fewer bugs. However, testing and debugging routes is more challenging than working is standard Java so that takes more time (less time than writing the components from scratch). Most people don't know Camel coming in and many junior developers find it overwhelming and are not enthusiastic to learn it. So finding people that want to develop/maintain it is a challenge. Read full review Decreased efficiency in terms of how long it takes to enter order. Very quick with reporting which was great for meetings and customer service calls. Inefficient in terms of shipping abilities. Read full review ScreenShots