DuploCloud GCP Product Demo

View the full DuploCloud GCP Product Demo video.



Now let's take a look at a product demo.

We have decided to deploy a few applications on Google Cloud.

We start by considering a high-level application diagram.

Here, we have a dedicated VPC, two subnets each, with multiple firewall rules located in the US West region, one subnet for internal load balancers, and another for backend apps.

The application is exposed to the internet via an HTTPS load balancer.

The apps are packaged Docker containers to be provisioned on Google GKE.

Now that we've gone through the desired architecture, let's get to work.

We start by logging in to create the base infrastructure that includes the VPC, subnets, all networking configurations, firewall rules, and GKE cluster.

All of this is represented by the DuploCloud construct called Infrastructure.

With the simplified, high-level specification, the platform will generate the low-level details in Google Cloud.

We then move to deploy the back-end application.

The application is called Invoice and we start by creating a logical workspace or Tenant by that name in the finance Infrastructure, which we just created.

Behind the scenes, managed identities, resource groups, and other details are auto generated.

Next, we could switch to the Invoice application.

We will provision cloud storage by creating a bucket. We will now create a cloud function using the storage bucket.

We will next create a PubSub topic and create a cloud scheduler with the target set to that PubSub topic.

The cloud scheduler could also trigger an HTTP endpoint.

With network, compute, and databases in place, we next moved to deploy the first Docker-based microservice.

Here, again, the user provides an application-centric specification while DuploCloud auto-generates configurations that include the deployment or stateful sets, network ports, Ingress controls, and other such infrastructure details.

We then expose the application via a load balancer.

Let's do a quick sanity test.

Our application works.

Logging is implemented via Elasticsearch and Kibana.

Here, one, you could see the logs automatically collected and separated by Tenant and by Service.

Note that all of this is done without any manual effort and comes out of the box.

Next, businesses in highly regulated industries need to implement an exhaustive list of compliance controls.

DuploCloud comes with the SIEM and you could see, all these controls have automatically been met.

There's an audit trail in application-specific context.

Here, we are showing all the changes in the Invoice Tenant.

CI/CD is a layer on top of DuploCloud, and any CI/CD system could be leveraged for scripts would invoke DuploCloud API calls for deployments.

Finally, everything we saw via the UI can also be done via DuploCloud’s Terraform provider with a fraction of the code or expertise that would have otherwise been required.

For further information or more demos, visit the DuploCloud website at duplocloud.com.

There's an audit trail of all actions in an application-specific context.

Here we are showing the audit trail for the Invoice workspace.

Finally, there are various options to configure CI/CD for your daily code releases.

Everything that we've gone through the UI today can also be done via Terraform.

Here is the script for the current setup, deploying a fully secure and compliant infrastructure underneath, with a fraction of the code that would have otherwise had to be written and maintained.

Autonomous DevOps are the future of cloud automation.

To learn more, visit duplocloud.com.

Last updated


© DuploCloud, Inc. All rights reserved. DuploCloud trademarks used herein are registered trademarks of DuploCloud and affiliates