Cloud Code: a tool for developing applications in the cloud

Google Cloud

Google just introduced Cloud Code, which is a new set of add-ins for IntelliJ and Visual Studio Code that automates and supports all phases of the software development cycle, using existing tools.

The core tool of software development is the integrated development environment (IDE). EDIs, such as IntelliJ and Visual Studio Code help developers stay productive when editing, compiling and debugging code, but Google thinks they work better with local apps.

This can cause problems when developing applications for the cloud, as the cloud and on-premises environments are different, which can lead to bugs later in the development cycle.

With the release of Cloud Code, Google argues in its ad:

With this first version of Cloud Code, nWe focus on facilitating the development of applications that run on Kubernetes, including Google Kubernetes Engine (GKE).

Cloud Code extends Visual Studio Code and IntelliJ to bring power and the convenience of EDI to application development Kubernetes in the cloud.

Using Google's command-line container tools such as Skaffold, Jib, and Kubectl, Cloud Code provides you with ongoing information about your project as it is built, extending the local build, debug, and compile cycle to any local Kubernetes environment. or remote.

Deployment profile support allows you to define different deployment goals, such as local development, shared development, test, or production.

About Cloud Code

Cloud Code for IntelliJ permanently deploy an application to Kubernetes via a runtime configuration.

Deployment support profiles they can be run locally or through Cloud Build. Log file transmission is supported, as shown in the results window.

For example, in IntelliJ, Google offers a built-in library manager that adds the necessary dependencies to your application, it automatically activates the API for your project and handles all the required secrets.

Cloud Code for IntelliJ Library Manager makes it easy to find libraries, related samples, and documentation, and integrate them into your existing code base.

For an application to be operational on Kubernetes, you need to understand many concepts.

For example, Cloud Code also helps the user when starting to work with an updated set of preconfigured Kubernetes samples for debugging, authoring, and deployment.

This allows you to focus on developing your application rather than the initial setup. Cloud Code for Visual Studio Code has the debugger attached to a running Kubernetes cluster.

While some aspects of the plugins favor Google Cloud services, such as automatic management of libraries and dependencies.

Cloud Code features

Cloud Code is specifically designed to work with Kubernetesregardless of your provider.

Google has even pprovided tools to easily create new Kubernetes clusters on competitor services like AWS and Azure.

This has been a recurring theme at Cloud Next this year, as other services like Cloud Run have also been designed to be easily ported over to another provider.

We designed Cloud Code to easily integrate with existing DevOps tools and services, including Cloud Build and Stackdriver.

For example, once your code is ready to deploy, you can simply request a checkout or validation, prompting Cloud Build to automatically build, test, and deploy your application.

Esto makes environments reproducible and helps detect errors more quickly. Cloud Code and Cloud Build make it easy and simple to edit, review, test, and apply changes to your Kubernetes configuration.

CloudCode provides templates and error highlighting for the Kubernetes yaml files. Of course, Cloud Code also supports logging so you can view application logs from any environment right in your IDE.

If you are interested in trying Cloud Code, you can visit the following link where you can try it for free, in addition to that you can receive a credit of approximately 15 dollars to use in this tool.

The link is this.


Leave a Comment

Your email address will not be published. Required fields are marked with *

*

*

  1. Responsible for the data: Miguel Ángel Gatón
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.