Apache ServiceMix Reviews & Product Details

Apache ServiceMix is built on an open, modular architecture, making it easy for me to integrate with other systems and add new components as needed. It also includes a powerful web-based console for monitoring and managing our applications, allowing us to diagnose and resolve issues quickly. Apache ServiceMix has built-in enterprise service bus (ESB) capabilities, allowing us to orchestrate services and workflows easily. Review collected by and hosted on G2.com.

Apache ServiceMix Documentation can be limited and outdated, making it difficult to troubleshoot issues or find answers to specific questions, particularly when running complex integrations; it requires additional hardware or cloud resources to support. Review collected by and hosted on G2.com.

I enjoy the fact that the apache server, once downloaded, makes it easy to connect to a localhost and test out my website designs when programming or running tests. Review collected by and hosted on G2.com.

I find that setting ports for my servers can be very difficult and at times I cannot even change them from the default value. This makes it difficult when, I use MySQL for example and the apache service is also running its sql service. Review collected by and hosted on G2.com.

It is bundled with reliable messaging using ActiveMQ, routing and integration engine using Camel and great support for web services using CXF Review collected by and hosted on G2.com.

Changing default ports may be difficult at times when using other services such as MySQL, Oracle database and apache service mix is also running it's db service Review collected by and hosted on G2.com.

As you can check, we have a lot of tools contained in a single component. This tool is fantastic because we have the versions we require to work (we can see this as a coupled system) and don't need to worry about the versioning. Review collected by and hosted on G2.com.

Even if we have the documentation, sometimes we require specific cases or scenarios that are not covered. So I need to check external references or tutorials. Review collected by and hosted on G2.com.

Apache ServiceMix is quite the complete package. It's very lightweight and open source, good API connections, good customer support. Routes in Camel and ActiveMQ are very powerful and easy to set up Review collected by and hosted on G2.com.

It's a bit obsolete. Docker and Kubernetes are all the rage now (Rightfully so), and give you a bit more control. Review collected by and hosted on G2.com.

simple to set and begin control. Coordination support is awesome. It very well may be worked either on Java SE or Java EE. Effective customer API given. Review collected by and hosted on G2.com.

I can't find any bugs or any problems when I use Apache ServiceMix. Review collected by and hosted on G2.com.

The best part is that I can test my applications locally after installing it. This gives me a good idea of how my application will look after getting deployed. Review collected by and hosted on G2.com.

The only issue is the lack of proper documentation. Else everything is excellent. Review collected by and hosted on G2.com.

It is open source. It provides version control, which helps a lot. Review collected by and hosted on G2.com.

The documentation doesn't cover all the possible scenarios and cases Review collected by and hosted on G2.com.

Easy to set and start manipulation.

Integration support is the best.

It can be operated either on Java SE and Java EE.

Effective client API provided. Review collected by and hosted on G2.com.

No problem seen on the Apache ServiceMIX to say. The starting was simple taking a very short learning curve to become a Pro on the platform. Review collected by and hosted on G2.com.

In a previous gig, I was able to use ServiceMix to *vastly* simplify the back-end Java architecture of my company by with ServiceMix, with the following benefits:

1) Multiple individual Tomcat and Jboss instances were replaced with a ServiceMix cluster

2) Complex IPC chains that were a mix of SOAP & REST services calling each other could be *mostly* replaced with routes in Camel & ActiveMQ that allowed you to actually understand the workflows.

3) Built applications as OSGi modules & hot-deployed them with limited to no downtime on Karaf instead of the complex 3-legged dance that my peers did with Tomcat & apache.

I was able to do all of the above bc I was a .NET developer moving to Java, with a team & manager that were free of the enterprise-y IBM ideation, and put their faith in me to innovate. We were able to build a quick PoC, and eventually win converts in other parts of the company. Review collected by and hosted on G2.com.

ServiceMix was an awesome stack maybe 4-5 years ago, when there were few ways to do immutable hot deploys, and OSGi leaned towards the simpler end of the Java stack.

However, it's nearly 2020, and this is a Docker & Microservices world now. Since I'd worked with OSGi & ServiceMix, the Java community came out with awesome micro-frameworks like Dropwizard & Spark. After using Kafka, ActiveMQ seems clunky and complicated, and Kafka Streams/KSQL make Camel look "legacy".

As awesome as ServiceMix seemed years ago, I would much rather run microservices in Docker containers on Kubernetes now. Kubernetes gives you way more control over container lifecycles, load balancers, and is much less work to maintain than ServiceMix. Review collected by and hosted on G2.com.