Azure Container Apps vs. IBM Cloud Foundry

Azure Container Apps is a welcome addition for sure. Based on my experience, this has enabled us to move fully to the cloud and managed everywhere in one spot and on the go. We can scale it to our end as much as we would like. It can be assess anywhere and it is fully secure

Incentivized

IBM Cloud Foundry is a solid service from the IBM Cloud platform. It is easy to learn, and does not usually require you to make drastic changes to your existing applications. It is especially good for new applications that are cloud native, or micro-services, that can be easily updated and deployed. With its blue/green deployment, you can achieve 0 downtime for your customers.

Incentivized

• Cloud-native where it can be assess anywhere
• Enhance security
• Open source

Incentivized

• Intuitive user interface makes it easy for anyone to use, regardless of their professional background.
• A lot of the services integrate well with external platforms, APIs, and programs, not just IBM services. A lot of the competitors in this space lack this ability.
• Maybe it is just our contract in particular, but support and help is always made available.

Incentivized

• The deployment process is complicated
• Learning of Azure cli (command-line interface) for deployment is required
• Not compatible with other standard CI/CD tools

Incentivized

• Sometimes the API Connect GUIs don't cleanly disengage after attaching models or updating schema and it is hard to know what has been written successfully and which (if any) models or tables were missed. I shouldn't have to manually check through a list of 377 models to find the ones in and out of a list on either models, folder or database tables. Printing a summary even in logs which did a "diff" sort of thing between 'task-set' and 'task-completed' (referring to attaching models or updating schema as tasks here as 'tasks').
• Provide access to Postgres Database in Sydney datacentre for Australia.
• Clearer documentation around setting up a secure (referring to SSL and certificate setup here) server on eg, chubby1.au-sydney.mybluemix.net.
• Allow a ramp in pricing onto the Blockchains. We will not be able to afford it until quite a few years into production, even if we launch successfully.

Incentivized

I would rather use AKS for my critical applications. The fact that the deployment process is dependent on as cli makes it hard for us to integrate with our standard CI/CD tools

Incentivized

Azure Container Apps are fantastic and it is a game changer. I would recommend it to anyone considering it. As you can scale it to what you would like and it is fully cloud native with better security. It is a no brainier not to consider it. I do believe that with further improve it will become even more attractive

Incentivized

Each one has the benefits and drawback. While it is not easy to compare apple for apple. I definitely like that it can be integrated with our system to ensure that we are running at 100% capacity. It is a vision to be 100% cloud base and we have been able to achieve this through Azure Container Apps

Incentivized

IBM Cloud Foundry is our first choice industry-standard platform as a service (PaaS) which has always provided us with quicker, simpler, and more consistent ways for the deployment of the cloud-native applications which in result saved us lots of time and money.

Incentivized

• As it is cloud native, we no longer required to have onsite prem
• Reducing both from an energy and security perspective
• It is worth the investment as we have saved about 10% of our ICT cost

Incentivized

• This was the founding solution used to allow us to move in to and test out a cloud pipeline. This is what paved the way for a full production cloud solution to be possible.
• Having Cloud Foundry at the base of our development and sandpit environment, segregated away from our standard on premise solution has moved away red tape and ensured an agile way forward.

Incentivized