Google Cloud Run vs. Superblocks

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

Superblocks is great for building internal tools for your company. We have our finances running on Superblocks, our client services running on it, as well as a lot of internal tooling for our product. You can build full-apps using their API builder, Workflow builder, Scheduled Jobs, and UI builder. All without having to handle your own infrastructure. It's meant to be one extra abstraction layer on top of other developer infrastructure tools like AWS, Vercel, etc.

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

Incentivized

• Easy to use User Interface builder for building internal apps
• Scheduled Jobs and Workflow builder in multiple languages
• API builder for support your User Interface for your internal apps

• 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

• More flexibility on UI component designs

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

Incentivized

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

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

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

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

Not part of purchase.

Incentivized

It has good auto scale feature and reliable also

Incentivized

We have very good support when needed

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

• We've saved thousands of developer hours that would have otherwise spent on maintaining infrastructure