Engineering

Why Move To Google Cloud Platform

Allan Porras

22 Jun 2014 — 1 min read

Google Cloud Platform (GCP) is a set of services hosted in the same infrastructure where Gmailand YouTube are located.

A lot of companies around the world are choosing GCP to build their apps because low lateency, easy APIs, pricing, one-dashboard. For example, the Angry Birds game run over GCP.

GCP includes:

App Engine
Compute Engine: Linux and Windows Virtual Machines.
Cloud Storage: Unlimited space for storage files, pictures, programs, or whatever kind of extension.
Cloud Datastore: it’s a non-relational database, like MongoDB.
Cloud SQL: relational databases instances with auto backups.
BigQuery.
Cloud Endpoints

We are experts building on Google Cloud, please feel free to contact us for receiving more information.

How to Build Your Own Internal Developer Platform (IDP) Using Crossplane

In the modern cloud-native landscape, the friction between operation stability and developer velocity remains a critical bottleneck. As organizations scale, the manual ticketing systems traditionally used to provision infrastructure become unsustainable. The solution lies in platform engineering: building an Internal Developer Platform (IDP) that enables self-service capabilities without sacrificing governance

Orchestrating State: Building and Deploying Stateful Applications on Kubernetes with Operators

While Kubernetes excels at managing stateless microservices via standard Deployments and ReplicaSets, managing stateful applications—such as databases, message queues, and distributed caches—introduces significant complexity. These applications require stable network identities, persistent storage, and ordered deployment and termination. To solve this in an automated, scalable manner, high-performing engineering teams

Automating Cloud Security Remediation with Policy-as-Code: A Blueprint for CTOs

In the modern cloud-native era, manual security reviews are a bottleneck that stifles velocity. As infrastructure scales, the "click-ops" approach to security management becomes untenable. For Chief Technology Officers and Senior Engineers, the transition to Policy-as-Code (PaC) is not merely a compliance exercise; it is an architectural imperative.

Deconstructing the Monolith: Implementing the Strangler Fig Pattern for High-Availability Migrations

Modernizing legacy systems is rarely a "rip-and-replace" operation. For Chief Technology Officers and Senior Architects, the risk of downtime, data inconsistency, and operational paralysis makes big-bang rewrites a non-starter. The Strangler Fig Pattern, named after the biological behavior of fig trees that grow around a host tree until

GCP includes:

Read more

How to Build Your Own Internal Developer Platform (IDP) Using Crossplane

Orchestrating State: Building and Deploying Stateful Applications on Kubernetes with Operators

Automating Cloud Security Remediation with Policy-as-Code: A Blueprint for CTOs

Deconstructing the Monolith: Implementing the Strangler Fig Pattern for High-Availability Migrations