Apache Camel is an open source integration platform.
N/A
Anypoint Platform
Score 7.8 out of 10
N/A
The Anypoint Platform developed by MuleSoft and acquired by Salesforce in early 2018 is designed to
connect apps, data, and devices anywhere, on-premises or in the cloud. This platform was built to
offer out-of-the-box connectors as well as tools that architects and developers can adopt quickly to
design, build and manage the entire lifecycle of their APIs, applications, and products.
N/A
Pricing
Apache Camel
MuleSoft Anypoint Platform
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Apache Camel
Anypoint Platform
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Apache Camel
MuleSoft Anypoint Platform
Considered Both Products
Apache Camel
Verified User
Anonymous
Chose Apache Camel
Easier to use, better routing system, but perhaps too basic dependant on business needs?
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 …
working with Apache's TomCat server, our developer found it most easy given the UI of Camel to perform integration and data processing tasks. when compared to the other two softwares they felt the need to learn new tools outside of Apache family can be avoided and with kafka, …
We did a comparison of the two products with an example application that tested about 10 distinct EIP pattern. We wrote Camel in XML and Java DSL and SI in XML. This was about 3 years ago. At the time, I found the threading model in SI to be more intuitive and Camel's seda. …
Akka or Spring Integration/ XD are alternatives to Apache Camel and very good frameworks on their own (especially Akka which provides a single threaded illusion).
We chose Apache Camel because it was lightweight, easy to get started with and because it had a groovy DSL since we were a grails shop when we started using it.
Apache Camel has been the integration framework of choice, but I was not the person to make the decision to use it. Compared to other competing products like Tibco Business Works, etc., it is free and open source and its licensing policy is acceptable to the management of Cox.
Esper is only similar in that they both are involved in complex even processing, however Esper's aim is a little more complex and specialized. In general however I found Apache Camel to be much easier to understand, implement and debug, whereas Esper's DSL can get very …
AWS is a very good tool but still evolving and offers a small set of API management features. The main reason why we chose MuleSoft Anypoint Platform API Manager is because it is well suited with the APIs developed in Mule ESB.
Once we have moved all of our system integration APIs to the MuleSoft Anypoint Platform, we will need to communicate with a wide variety of external systems. All of our business and service logic is stored in the aforementioned core systems. Anypoint Platform (and all of our …
Overall a better experience in pricing negotiation with the Sales team. The breadth of services offered by Mulesoft was really important and the expertise offered by our consulting partner influenced the decision. The overall deployment was completed well within the timelines. …
Once we use [MuleSoft] Anypoint Platform to host all our system integration APIS, we need to exchange data with a lot of different resources. Those listed systems are our main systems that hold all business and logic behind our service. The integration from Anypoint Platform …
We selected Mulesoft for speed of implementation. We did not have the luxury of time and needed a solution that can be learned and implemented within weeks so we can take advantage of newly formed partnerships. The training that was provided to use during our pre-sales and …
We believe Anypoint Platform is best in breed and has features that match nearly any other iPaaS offering. It also allows for accomplishing much more challenging and complex integrations due to the ability to connect to nearly any system, use custom connectors, and embed …
The main problem with this software is the different connector type that is used for different protocols except for a different SAP connector. There is only one connector called SAP. It will be great if there will have a different connectors like idoc, RFC, proxy, etc.
Anypoint has tons of capabilities baked in one platform, and other competitors like Built.io or Workato may not have all those like Anypoint Exchange. However where these products shine are in usability, as it's ridiculously easy to build integrations using Built.io. I was …
Anypoint Platform is really very easy to adopt for application integration. Simple UI and easy data weave language allows user to focus on business portion only. The API management and deployment of application are hassle free. We have selected Anypoint platform because it is …
Dell Boomi is kind of similar in drag and drop implementation. However, it doesn't have as many connectors (shapes in Dell Boomi). Moreover, it also doesn't have deployment stuff on its own.
Informatica is way behind Dell Boomi and Anypoint Platform, but users are still using it …
Compared to Dell Boomi the API management suite of Mulesoft is much mature, however if its only about the integration , then i would always go for Dell Boomi, as there is no infrastructure setup that needs to be done from the developer's end.
The main reason why we chose Anypoint API Manager is because it is well suited with the APIs developed in Mule ESB. AWS, on the other hand, is a very good tool but still evolving and offers a small set of API management features.
API led architecture focus with a decent API ecosystem for developer collaboration, policy management and declarative implementation. Batch processing, visualization, Anypoint MQ and ObjectStore leave a lot to be explored. Multiple deployment models make it worth considering.
It enables customers to expose their APIs in a very simple and fast way. It can be used by non-expert developers. It is compliant with all major connection and data representation world standard.
We provide options to customers to choose from the best tools. Customers are the decision makers. Personally, because of open-source and large community base, MuleSoft is the repo in the market.
It is a powerful tool with smart intelligence. The drag and drop feature makes my work easy. The tool has great connecting support which is the best reason to use the tool on a daily basis. Powerful functionality with designing and implementing APIs. Hosted on public IP.
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.
MuleSoft Anypoint Platform is best tool in the market for developing APIs with complex structures communicating with various different types of applications including web applications as well as legacy applications. Also applications including database connectivity for fetching and updating data in the DB tables. I cant think of any scenario which MuleSoft Anypoint Platform could not be used for developing the integrations.
Provides wide range of popular connectors like salesforce, netsuite, sftp and many more. A user can easily integrate with those services using specific connector.
Support API development using RAML and desing tool. The platform is very good in data type classification.
Cloud deployment and post deployment monitoring is easy. A user can configure application worker as per need. Alert and notifications are real time.
Some of the documentation is a little sparse. In particular, its TCP-based routes use an underlying Netty server, and the interactions between Netty's decoder capabilities and Apache Camel's routing/handler capabilities can be a little muddy at times. In general it is clear which routes and endpoints are the more frequently used and which haven't been given as much attention.
Has more features than what we really need so we're paying for more than we use. Sort of like paying for an Abrams tank when all we really need is a Toyota Corolla.
Not a value product, tends to be expensive.
Takes a while for developers to learn to use Mulesoft Anypoint.
MuleSoft Anypoint Platform is really very easy to adopt for application integration. Simple UI and easy data weave language allows user to focus on business portion only. The API management and deployment of application are hassle free.
Anypoint Platform support is very responsive. There is also a huge knowledge base and an active online forum where answers to most questions can be found. When needed support engages the engineering group so adequate solutions or workarounds are always provided.
Apache Camel has been the integration framework of choice, but I was not the person to make the decision to use it. Compared to other competing products like Tibco Business Works, etc., it is free and open source and its licensing policy is acceptable to the management of Cox.
Once we have moved all of our system integration APIs to the MuleSoft Anypoint Platform, we will need to communicate with a wide variety of external systems. All of our business and service logic is stored in the aforementioned core systems. Anypoint Platform (and all of our APIs) makes it easy to connect to various other platforms. In order to link to these many other systems, connectors and/or components are utilized, and they are simple to configure and integrate.
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.