TrustRadius Insights for IBM Cloud Foundry are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Simplicity and Quick Setup: Users have appreciated the simplicity of IBM Cloud Foundry, noting that the command line tool provided allowed them to get up and running within minutes. This ease of setup has been crucial for users who value a straightforward onboarding process.
Feature-Rich Platform: Reviewers have found IBM Cloud Foundry to be feature-rich, providing essential cloud-based platform features like auto-scaling and zero downtime deployment. The inclusion of these features has enhanced the overall user experience and functionality of the platform.
High Scalability: The high scalability of IBM Cloud Foundry was highlighted as a positive aspect by users. Being able to easily scale resources based on their needs has proven beneficial for users managing varying workloads efficiently.
Loading Reviews List....
IBM Cloud Foundry Reviews
10 Reviews
Professional, Scientific, and Technical ServicesLegal Services1Information Technology & Services9
IBM Cloud Foundry is one of the most powerful, highly scalable, and widely used platforms that not only offers IaaS and PaaS cloud services, but also helps us in building new apps or migrating old ones. It helps us in on-prem and off-prem deployments as well as bringing all of these elements together in the cloud for our ease and to help us solve real-world, difficult business challenges on this single platform effectively. IBM Cloud Foundry ensures that the build and deploy elements of coding are meticulously coordinated with any attached services, [ensuring] application iteration is swift, consistent, and dependable.
Pros
IBM Cloud Foundry is an easy, efficient, and multi-cloud platform to support users in the management, development, and continuous delivery of other applications.
Linking a custom domain to an IBM Cloud Foundry-hosted PaaS application is simple.
IBM Cloud Foundry offers well-explained and clear picture log errors to help users to figure out what's truly wrong and why the application isn't being pushed to the cloud or isn't working.
Cons
Its online UI can become unresponsive or hang due to heavy usage, but we always have the CLI as a backup.
When attempting to deploy larger Meteor-based applications, it frequently fails.
Likelihood to Recommend
As it is an open-source platform as a service, it is very easy to operate, scale, and deploy regardless of what programming language and framework it's written in. However, it could be improved in terms of scalability. There should be proper documentation for easier and clearer understanding to make the process smooth.
IBM Cloud Foundry is the primary container deployment technology we utilize for our cloud product offerings. All our cloud applications are deployed and running with it. IBM Cloud Foundry simplifies the processes for our development and operations team, by providing a standardized packaging and deployment methodology, as well as integrating into the overall toolchain, from development to final deployment.
Pros
Simplicity - the command line tool provided can get you up and running within minutes.
Resourceful - IBM Cloud Foundry is built on top of the open source Cloud Foundry technology, so any resources you find online about Cloud Foundry generally can be applied.
Feature rich - provides all the necessary features for a cloud based platform, such as auto-scaling, 0 downtime deployment.
Cons
Documentation - most of the time, you will be referring to the open source Cloud Foundry's documentation instead.
Certificate management - this part is custom to IBM Cloud Foundry, and it does not have official APIs for you to manage SSL certificates for the various domains you might have.
Likelihood to Recommend
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.
VU
Verified User
Director in Information Technology (Information Technology & Services company, 1-10 employees)
Recently I've built and run a web-app (trindfl.com) within IBM Cloud Foundry, which is drafting a tax declaration for interactive brokers (IBKR) traders. A user downloads her IBKR yearly activity reports (csv files), and then she uploads them to the web-app (IBM Cloud Foundry). In a few seconds the web-app, first, parses the uploaded reports, second, prepares the tax declaration file (xml), and, last, prepares an explanatory note (xlsx), which shows how IBKR report is aligned with Russian tax law. Brief analysis results are presented to the user so she can make a decision to purchase and download tax declaration and explanatory note files. All the uploaded and created files are deleted after a while.
Pros
The IBM Cloud CLI software doesn't change my laptop environment (whereas AWS CF Python CLI does).
IBM Cloud Foundry allows me to use the most recent versions of Python.
IBM Cloud Foundry easily integrates with other IBM services (e.g., DB2 service, object storage, LogDNA).
Cons
When using IBM Cloud Foundry with LogDNA, I can't filter log events based on their level (i.t. debug, info, error). Thus, LogDNA marks all the web-app log messages as 'OUT,' which is not quite useful for message filtering.
Likelihood to Recommend
When I started with prototyping five months ago, I tried IBM Cloud Foundry and AWS, but finally I preferred IBM Cloud Foundry for the reasons described bellow.
I needed to draft a system architecture, which includes Python web app, database, object storage, and API integration with external services. IBM Cloud Foundry provides me with enterprise-level production-ready solutions, which I could easily integrate and test my prototype before I made a system selection decision. Thus, I chose IBM Cloud Foundry, object storage, DB2 service, and LogDNA to proceed. In addition, many IBM services provide free trials, so I don't need to pay for testing during the stage of system selection and prototyping.
At my work place, most of the in house web solutions and client projects we built is being hosted on IBM Cloud Foundry. Its being used majorly by Engineering team which I co-managed for the firm, and I also assist in tutoring new developer on how to make use of IBM Cloud foundry and other IBM Paas or resources that will make use by the Engineering team. It provide us flexibility in hosting, which there is option for continuous delivery which can be make use when you setup continuous delivery toolchain, which I have make use when I am given role to set up the environment for a new project and a starter content for the project. Secondly, make use of terminal command to push project to IBM Cloud foundry, which I can configure the custom domain which I want to assign to particular project through my terminal. Thirdly, I can allocate max memory which my application should make use of especially when we implement Proof of Concept to pitch our idea, so i reduce it from the default 256mb to 64mb which helps to save cost and waste of cloud resources, which other applications can make use of. Fourthly, there is provision for secure and non secure subdomain url for hosted application which is very good startup at-least when sharing our POC link, investor won't be worried since we would be providing with secure url to access our ideas which in return make them trust us and give us audience.
Pros
Hassle free linking of custom domain to hosted application on IBM Cloud Foundry
Flexibility in hosting application on IBM Cloud with easy terminal command availability for all settings which is required to set up IBM Cloud Foundry instance for that project
Well detailed explainable log errors to guide the user on what is really wrong , why the application was not push to cloud or not live
Properly index error in search engine which often list IBM forums url within the top 5 when you search with keywords from the terminal log errors you copied
Availability of IBM Cloud Foundry SDK on major languages with sample implementation code for the selected language
Cons
Major improvement I think is currently needed is sponsor more seminars in tech related field because I could search and see more content on youtube compare to other IBM resources which I have to rely solely on the IBM documentation to implement it
Properly index documentation on search engine optimization on how to point Cloud Foundry Application to a host on another platform
Partner with Massive Open Online Courses like udacity to create video content on software development track with free tiers to host on the resources during learning
Have issues when the domain doesn't come with ssl certificates and I upload generate Lets encrypt ssl to the custom domain interface after I install it, the domain won't be secure . I will want you to investigate this issue
Likelihood to Recommend
Based on the application I have hosted on the IBM Cloud Foundry Platform as a Service, since I have being using it. It best use case for hosting is NodeJS applications, single page applications for professionals like MERN stack Developer, MEAN Stack Developer, JAMStack Developer, PERN Stack Developer. I am learning Flask Framework now, I will write review on that when I host it on IBM Cloud Foundry.
Cloud Foundry is used for a few of the apps in our projects. Since this is in the cloud, it's reduced the overhead of maintaining a server dedicated for all our server requests.
Pros
Scales well.
Good for deploying small apps.
A variety of commands to choose from to maintain the app well.
Provides clear separation of organizations and spaces.
Cons
It frequently fails when trying to deploy larger applications that involve Meteor.
Mapping and unmapping require a restage, which loses the point of blue-green deployment.
Needs better documentation for all the functionality.
Likelihood to Recommend
When you have a small app with lightweight packages, IBM Cloud Foundry works really well. It gets funky when meteor-like apps are highly dependent on large packages and it constantly throws StagingError or Timeout errors. It is easy to understand but some functionalities are more complex when used. We used blue-green deployment for the apps to avoid prod downtime, but the routes were still ghosting around, and only staging(timeout) fixed the routes.
We use IBM Cloud Foundry to deploy multiple micro services which are a part of our product offering. It the the main deployment model we use right now across our organization.
Pros
Simple deployment model
Multiple language support
Good monitoring and operational support
Cons
Better security model, the current model is coarse grained.
Likelihood to Recommend
Quick turnaround for deploying applications, it provides a language/runtime agnostic environment to deploy applications with a simple interface.
It ran our entire backend functionality. It is used across the entire organization and its impact is seen on every one of our customers. We used it to try to simplify our deployments, as they took a lot of time out of our day.
Pros
Large collection of tools to integrate with.
Growing application support.
Bluemix has the ability to scale easily from very small to very large.
Cons
Applications that were integrated had a feeling like they came from very different companies and organizations.
Logins had to be performed often between different services, once a week the applications would change and we had to learn a different way to do the logins.
Branding is important, but the names, like "Jazz" would get in the way of what the application did for us. So new developers would have to learn 5-6 new special websites just to do a single deployment. And one or two new changes a month to keep up with it.
Likelihood to Recommend
It is suited to large businesses with somebody specifically in charge of deployments. He would be a person specifically paid to take care of all the machines through the Bluemix service. It is not a good situation when the teams are small, such as a three-person development team, because there is considerable maintenance that must be taught between them, and this costs a bit of time and hence money in that situation.
I personally build tech demos to showcase emerging tech and try to encourage others to do so. IBM Bluemix was great for me to bring in APIs like The Weather Channel data and text to speech to create a virtual assistant. I wrote about it online to teach others how to do so too.
Pros
Easy modular access to new functionality like text to speech.
Integrates well with NodeRED.
Cons
Documentation is really hard to search through and follow along with. Needs a lot more examples and guidance.
Pricing isn't clear a lot of the time. As a developer trying new stuff, I've been hit with charges and been unsure where the usage came from. Would be good for this to be easier to follow up. Had asked support staff and got no reply.
The interface can be overwhleming.
Likelihood to Recommend
It's well suited to corporate clients who aren't as concerned by the potential fees (as they'd be much higher developing the functionality in house). It's also very handy to have the services delivered by a company that's got the reputation of IBM as it's easier to show that this is trustworthy and will have good uptime...etc.
It's used across the whole organisation, Bluemix is providing the foundation for our enterprise apps, which we develop as mobile-first developers. The availability of push notifications, the functionality and integrity of the mobile system, as well as the overall security are the keys to its value to us.
Pros
Flexible development environments available, all interoperative, from Docker-based to apiconnect-based. We can use several repo-sites and keep code versions well tracked and reclaimable on any of them. The networked nature of the systems means we can develop from a world wide basis of engineers and programmers, although right now we have one Senior Software Engineer and a couple of coders, in different countries.
Datasources can be connected from anywhere.
Mobile Endpoint Security, and Server Security (meeting or exceeding 27001 and 27002) with IBM, represent resellable value to us.
We are a fledgling company, but as soon as we are able to afford to use the Blockchains offered by IBM, we will do so, because we can eliminate one entire class of financial (or any trust/transaction-based) risk this way.
With the use of Cordova we can code our front ends once and cover the web, Android and iOS platforms together with minimal fuss to tailor the code.
Cons
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.
Likelihood to Recommend
For us as a start-up IT company (offering SaaS) whose entire existence revolves so far around the possibilities offered by the cloud and a PaaS like Bluemix, we are building our image on a "Mobile-First" reputation, and have the necessary skills to write our own financial recording/reporting systems, with master ledgers updated from journals, as well as the other bells and whistles required by modern enterprise apps. Bluemix allows our customers, people in businesses, to connect from the field or office, from anywhere in the world, and complete any (100%) of tasks available on the applications. Where the data to be recorded is largely text and numbers encodable in JSON format, real-time internet can be used very effectively to transmit requests and receive responses from the servers in the cloud. We arrange to save images and/or video recordings "on-device" until the user returns to an office or location where a wi-fi modem or hotspot can be connected to.
IBM Bluemix is being used as my primary cloud computing service, having recently replaced AWS as my preferred service. I work with an IT consulting firm, and specialize in designing IT infrastructure for businesses, usually start-ups. My company has changed over the years as technology changes, originally setting servers up at the clients location, then moving to hosting them myself, and now I utilize cloud services with IBM as my primary source of server environments since software development is the focus of 75% of the start-ups I have been encountering, which is where BlueMix shines. Instead of detailing out how I use these services, I am going to explain the differences between IAAS (AWS/Google/Azure) vs PAAS (BlueMix, Redhat). The main difference is what level of control the system focuses on, when it comes to IAAS, the system is focused on infrastructure, such as building a server with x processors, x amount of ram, a storage system with X Gb of data. PAAS on the other hand, is focused on the whole platform that will run your software rather than just the simulated hardware specifications. AWS (IAAS) lets me build a virtual server with 2 processors, 1 gb of ram, 15 Gb of drive space, and 2 network adapters, which I then need to install an OS on, BlueMix (PAAS) lets me setup a geographically clustered environment that can serve HTML, PHP, and MySQL, while also being able to pull Microsoft SQL, while running a version tracking system, such as GIT. So from the start, I specify what I need my system to do to run my software, rather than what I need my server to have to run my OS, to run my server software that I can add additional functionality to in order to allow my custom software to operate best
Pros
Bluemix is great at providing a custom environment that offers everything I need to develop and run my software, rather than just providing a blank virtual server that I need to configure
Bluemix is very good at getting a "ready to use" environment deployed very quickly
Offers a wide variety of very unique, and cutting edge services. For example, I recently came across a Bluemix service that analyses any documents I want, such as email, and can tell me what emotions I am conveying. Is it a hateful sounding email, or a happy sounding one.
Cons
Documentation is lacking unfortunately, and while the new version of BlueMix is very quick and easy to use, it still requires a heavy development background to get features out of it that would end up rivaling AWS.
Stability isn't where AWS is, and while being a perfect development system, it isn't where you want to run a production site where downtime causes financial losses.
It is very hard to move your app off of BlueMix to another cloud service, as you just can't get the same level of platform customization, and you are going to absolutely be stuck to other PAAS providers.
Likelihood to Recommend
IBM BlueMix is the perfect, and I do mean "PERFECT" environment for any business working with app development, which is becoming a very large industry very quickly, or an IOT (Internet of Things) oriented business. It allows you to very quickly deploy a custom platform to run and develop your software with, rather than quickly deploying a blank server. BlueMix is especially useful in any situation where multiple developers will be working on a development project or where external contractors need to interact with the development process. BlueMix is also invaluable for those who have an existing data source – for example, a company that has a large CRM system that has built up a large customer database and wants to design applications which utilize that data. Since the customization is in the platform, it is not ideal for companies that need to have mobility capabilities to move between different cloud companies, or any company that has software that requires a lot of server hardware or OS customization.
