Item: IBM Cloud Code Engine
Rating: 9
Author: Pranav Goel

Use Cases and Deployment Scope

Developers across our organization utilize IBM Cloud Code Engine for a number of use cases, including running applications, functions, and batch operations. Instead of spending time managing infrastructure and configuring hosting environments, our engineers can concentrate on writing code. IBM Cloud Code Engine provides an end-user experience for developers that is easy, adaptable, and intuitive. While the documentation is a little weak, but a person with prior knowledge can easily be adapted to the workflow very easily.

Pros and Cons

Server-less platform that is automatically managed
Pay per use - scale to zero results in an extremely cheap total cost of ownership.
There is no need for you to set the size, deploy, or scale container clusters yourself.
Auto scaling is always helpful and easy to use.

For Bigger projects, the Number of jobs and apps can be increased along with maximum memory consumption.
The Documentation can be more extensive for freshers and get more engagements from the newcomers.
Moving around the security changes can be tricky and hard to change.

Return on Investment

Code Engine is completely linked with IBM Cloud, you may make use of the whole catalog of IBM Cloud services.
Autoscaling is really helpful, and can even go to Zero.
Some new people around were a little unfamiliar with the platform, so took longer to have more people on board.
The limitations to only 100 jobs and apps, can be a pain for Massive projects, but hasn't been a problem for us yet.

Usability

As mentioned in previous points, the ability to scale to zero results in an extremely cheap total cost of ownership. As well as added features like auto-scaling and serverless management are a huge plus, can help in quick deployment as well as showcasing new prototypes and solutions. The only thing that was a little buggy was the security, but an experienced engineer can surely work with that.

Time Savings

The auto-scaling, as well as the serverless management services sure, has allowed us to work more towards the designs solutions than to worry about deployment.

Alternatives Considered

Azure Virtual Machines and AWS Lambda

Having only some hands-on with the other services, The cloud engine is considerably simpler to operate, with a very clear interface and management. Each application can be easily configured and altered without needing to know anything about different subscription tiers or the system's inner workings. But in the case of Lambda, Depending on the situation, Code Engine will fetch your source code and generate the container image. Code Engine supports both Dockerfile and the Cloud-Native Build bundle, which is preferable. It is possible to create applications that send messages based on events.

Key Insights

Do you think IBM Cloud Code Engine delivers good value for the price?

Yes

Are you happy with IBM Cloud Code Engine's feature set?

Yes

Did IBM Cloud Code Engine live up to sales and marketing promises?

Yes

Did implementation of IBM Cloud Code Engine go as expected?

Yes

Would you buy IBM Cloud Code Engine again?

Yes

Other Software Used

AWS Auto Scaling, Azure Container Instances, Docker

Likelihood to Recommend

It would be a good solution for running serverless applications. Because infrastructure setup and maintenance expenses can be avoided, the investment will pay for itself. The time to value is short, allowing IT to respond to business demands quickly. It aided us in customizing security as well as operating a personal project using to autoscale up and down approach. Also, because there isn't much hassle, items can be pushed into production as soon as possible. Simply push a container, create an application, and you're ready to go. But, It is less suited when you have a static machine or need to keep data in some way and do not want to utilize network storage or a database.

Easy to Use, Quick to Deploy, and Flexible to Scale!

Overall Satisfaction with IBM Cloud Code Engine