Apache Camel vs. Google Cloud Run vs. Portainer

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.

Incentivized

Microservices and RestFul API application as it is fast and reliant. Seamless integration with event triggers such as pubsub or event arc, so you can easily integrate that with usecases with file uploads, database changes, etc. Basically great with short-lived tasks, if however, you have long-running processses, Cloud Run might not be idle for this. For example if you have a long running data processing task, other solutions such as kubeflow pipelines or dataflow are more suited for this kind of tasks. Cloud Run is also stateless, so if you need memory, you will have to connect an external database.

Incentivized

Many developers, especially lesser experienced developers, don't have a really good background in setting up containers from the command line. Portainer is invaluable to them. Giving a UI to them gives them much more confidence and allows them to learn properties and capabilities of containers under far less stress. On the flip side of this, giving then a UI on a production system can lead to chaos...never give junior developers access to production servers.

Incentivized

• 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.

Incentivized

• Auto scaling is the best one
• provide direct VPC connectivity and rigid network
• Cloud SQL and Pub/Sub services
• Handling latency issues

Incentivized

• Separating server maintenance with application development, providing a clear user interface for developers who don't want to worry about the underlying server.
• RBAC for container deployment linked to a SAML IDP, not something particularly easy in a native Docker instance but point and shoot in Portainer, allowing the use of Azure / Okta etc to provide user access.
• Image management with multiple repositories is super clear and reduces incidents

Incentivized

• 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

Incentivized

• The UI can be made simpler. Currently the UI is bloated and it takes time to find out what you want
• More integrations with container registry providers (ECR, dockerhub)
• Better permissions UX. Currently GCP requires service accounts to be used with cloud products, the experience adding/removing permissions is difficult to navigate

Incentivized

• When setting up static IPs for a new container, having the used ones for a specific network at hand would be cool or something like a mini IPAM of some sort...
• Using the developertools to see "oh, it's a 40x or 500" when something doesn't seem to load because the ui just states "Didn't work" is kinda annoying. expandable toasts or something would be nice.

Incentivized

We definitely need to renew it because we dont own our own infrastructure and storage and we are happy with Cloud Run features

Incentivized

It is an excellent tool.

The UI/console is great... the documentation is top-notch for developers, but the CLI itself when you have to script around it is very complex and easy to forget some options... the downside of a generic command line client.

Incentivized

Accessibility for Non-Experts: even with some people having a bit longer on-boarding it is still very simple Quick setup is insanely useful, we can get it running in 10 seconds after installing docker Portainer has once again super clean UI and is very user friendly. Deployment/monitoring and management are super easy. I can tell just from a glance if something is out of date (watching at you Watchtower not doing your job for some reason)

Incentivized

Not seen any major issues when we run applications its good

Incentivized

Initially we felt slow but slowly it picked up and easy to manage

Incentivized

One of their staff members jumped on a video call immediately with me and led me through the problem and solution during a quick session of screen sharing. In this day and age that is above and beyond, especially when it comes to software. It took approximately 5-10 minutes to diagnose and fix, including pleasantries!

I was involved in the initial implementation setup, Its easy with the given documentaiton we can do ourself. Not that critical

Incentivized

It is really easy. Just follow the documentation.

Incentivized

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.

Incentivized

AWS Lambda supports code zip package, enabling lower cold start time. Also, AWS Lambda pricing is much simpler, easier to understand.

Other than that, the 2 products are very similar, including the Docker image support: the image must be built based on proprietary base image.

Obviously, if your other services are running in GCP, then Google Cloud Run is your only choice for tight integration, & private networking.

Incentivized

Portainer takes the cup in terms of usability and features. It is also more useful for smaller deployments, whereas Kubernetes in our opinion and experience, could probably be more suited to certain other use cases. Portainer is also a fresh feel among all the preexisting container management solutions and brings positivity and a new breeze in the industry.

Not part of purchase.

Incentivized

It has good auto scale feature and reliable also

Incentivized

We have very good support when needed

Incentivized

• 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.

Incentivized

• Built in support for auto scaling helps reduce operational overhead
• Any application performance issues can be addressed quickly by allocating more resources while a proper fix can be planned and rolled out later
• Using Google Cloud Run enables development of microservices which provides granular control for scaling critical services in the platform

Incentivized

• Increased productivity: Portainer's user-friendly interface and streamlined container management can help increase the productivity of IT teams.
• Cost savings: By simplifying container management, Portainer can help reduce the time and resources required to manage container environments, potentially leading to cost savings.

Incentivized