User Review
( votes)
The search engine giant made its first notable entry into the public cloud market with App Engine, a PaaS sandbox environment that developers could use to build applications without worrying about server maintenance. Google then added its cloud infrastructure offering and solidified itself as the third so-called hyperscale provider, behind AWS and Microsoft Azure.
Still, most of the Google Cloud developer tools didn’t hit the market until after the push into infrastructure. Google continues to add tools in a bid to improve the scaffolding developers desire in their environments and to keep pace with AWS and Azure in their bids to become all-encompassing cloud platforms.
Here is a brief synopsis of the major Google Cloud developer tools.
Artifact Registry. This registry service can be used to store and manage container images and language packages to support CI/CD pipelines. Artifact Registry is still in preview, but it supports Docker images, as well as Maven and npm packages. Code can be committed to Cloud Source Repositories, GitHub or Bitbucket. Developers can deploy that code through Cloud Build, Google Kubernetes Engine, App Engine and Cloud Functions.
Artifact Registry supports roles and permissions to enforce access controls. Google plans to add tooling for vulnerability scans and deployment policy rules.
Cloud Build. Google added this managed CI/CD platform in 2018 to capitalize on the growing popularity of DevOps. With Code Build, developers can build, test and deploy custom workflows in any programming language. Code commits work for container- or non-container-based artifacts, which can be pushed to GitHub, Google Cloud Source Repositories or Bitbucket.
