Engine Yard vs. Google Cloud Functions vs. Oracle Application Container Cloud (discontinued)

It is best for rapidly getting your application to the cloud without worrying about standing up cloud infrastructure

Incentivized

It is easy to use, in 15 minutes you just have to follow a few steps, do some easy configurations and you have the project ready to run, once it is connected to the codebase, the execution is automatic. For anyone coming into the google environment, Functions make code execution easy and transparent. CI/CD is perfect

Incentivized

For how it is used within the organization it is perfectly fine. We use it for benefits, salary, and vacation tracking. It does make it easy to find your information within the system and make changes.

Incentivized

• Quick deployments
• Easily integrate your code from GitHub
• Ability to recover site quickly to different zone when AWS has a widespread outage

Incentivized

• integration with oAuth
• integration with Firebase
• integration with React Frontend

Incentivized

• Ease of use.
• User-friendly.
• Sleek layout.

Incentivized

• Embracing new Amazon Web Servicess(AWS) features
• Security groups need more granularity
• Audit trails of what happens by who in environment, especially when VM is deleted

Incentivized

• Needing a zip file is problematic (when wanting to automate deployment for example).
• Requires another solution to execute automatically (ex. cloud scheduler).

Incentivized

• Fewer tabs.
• More direct access to information.
• More insight into where approvals are within the system.

Incentivized

Ease of use

Incentivized

I am not a part of the team that would make this decision but as far as I know they are happy with the platform and how it performs.

Incentivized

Overall Google Cloud Functions is losing a lot of benefits to other GCP services, making it less attractive to users. A simple example would be the need to zip application files and push them to Google Storage which makes it a bit complicated to automate via a CI/CD pipeline. Another "similar" solution would be using Cloud Run although the need for a docker image is there, with the recent evolutions to Cloud Run (ability to downscale to 0) it makes a lot more interesting.

Incentivized

Incredibly easy to use and learn how to use. The interface is extremely easy to use.

Incentivized

Documentation is provided and clear for this service. Although GCP support is included in the current contract we didn't get to use it since the process is pretty straightforward.

Incentivized

The team who helps with the issue is very helpful when resolving the issue and usually can handle it in a very timely manner.

Incentivized

The system is very easy to use.

Incentivized

More closely aligns to native AWS

Incentivized

It is easier to keep everything in house when we are using GCP or AWS. To mix Lambda with google cloud is not a best practice and will cause problems ahead. The segmentation is clear, if you are using google, you use Google Cloud Functions. if you are on Amazon, you use all AWS tools. You can't mix them. The price is set.

Incentivized

• Positive in the sense that we can deploy new applications quickly for MVP

Incentivized

• For training purposes, it is free
• Budgeting makes it cap the use
• monitoring makes it predictable

Incentivized

• Employee Empowerment
• Reduced lagtime
• Connects correct people to correct situations

Incentivized