Skip to main content

Posts

Container and Container Orchestration

What is container? Container contain application code and dependencies into single Unit. So, what is Container orchestration? Container orchestration is about to managing life cycle of container. Container orchestration to control and automate task: Provisioning and deployment of container Scaling up and removing container as per application load Allocation the resource between Container Health check of container Kubernetes open Source is the example of Container Orchestration
Recent posts

Cloud SQL

Cloud SQL is a hosted MySQL service. It provides: Rich query language Primary and secondary indexes ACID transactions Relational integrity Stored procedures Fully managed MySQL and PostgreSQL databases Fully managed instances Patches and updates automatically applied You still have to administer MySQL users Cloud SQL supports many clients gcloud beta sql App Engine, G Suite scripts Applications and tools    SQL Workbench, Toad    External applications using standard MySQL drivers

Cloud Storage and Cloud IAM or ACLs or Signed URLs

Cloud Storage offers layers of increasingly granular access control. For most purposes, Cloud IAM is sufficient, and roles are inherited from project to bucket to object. Access control lists (ACL) offer finer control. And for detailed control, signed URLs provide a cryptographic key that gives time-limited access to a bucket or object. A signed policy document further refines the control by determining what kind of file can be uploaded by someone with a signed URL Cloud IAM Works with Cloud Storage just as with using Cloud IAM with any other resource. Project Owners are automatically granted Bucket Owner role for all buckets in the project. Note that ACLs and Cloud IAM are independent, so Project-level Cloud IAM permissions will not appear in bucket or object ACLs. Signed URLs A signed URL gives you the ability to grant access to a bucket without Cloud IAM user authentication for a limited period of time. e.g., when you don’t want to require users to have Goog...

Cloud Storage

Cloud Storage stores objects in buckets. There are several differences between Cloud Storage and a file system. 1. A file system has a hierarchical structure. Cloud Storage is unstructured. It is a flat system of buckets (not directories) that cannot be nested. 2. An object name may consist of up to 222 characters. A valid character in an object name include '/' (forward slash). Using this character in object names can simulate some of the hierarchical structure of a file system, even though the slash is not a functionally significant entity. 3. Objects are replicated and distributed for availability. However, there is no distributed equivalent of a file lock. Therefore, the last entity to write to an object "wins." If you use Cloud Storage in a distributed application, the application is responsible for locking and serialization of access. 4. Cloud Storage treats objects as an unstructured series of bytes. Multi-Regional = Data is stored red...

Data storage services

All application need persistent and durable storage to accomplish their purpose. Applications vary in their storage requirements, so Google Cloud Platform offers many persistent storage services. Note: BigQuery is grayed out. BigQuery sits on the edge between data storage and data processing. You can store data in BigQuery, but the usual reason to do this is to use BigQuery's big data analysis and interactive querying capabilities All data in GCP is encrypted while at rest and encrypted in flight. Different applications and workloads require different storage and database solutions. Google offers a full suite of industry-leading storage services that are price performant and meet your needs for structured, unstructured, transnational, and relational data. This decision chart helps you identify the solutions that fit your scenarios.

Compute Engine:

Compute Engine offers managed virtual machine. You can configured high CPU, high memory and standard and shared core machine type like building out a physical servers. Also you can set persistence disk likes Standard, SSD, local SSD and also create Snapshots (global image). We can resized the disks without downtime. You can create a virtual machine instance by using the Google Cloud Platform Console or the gcloud command-line tool. A Compute Engine instance can run Linux and Windows Server images provided by Google or any customized versions of these images. You can also build and run images of other operating systems. Scale up or scale out with Compute Engine: You can make very large VMs in Compute Engine. The maximum number of virtual CPUs in a VM was 96, and the maximum memory size was at 624 These huge VMs are great for workloads like in-memory databases and CPU-intensive analytics. But most GCP customers start off with scaling out, not up. Compute Engine has a fea...

Firewall rules in GCP

When you create a GCP firewall rule, you specify a VPC network and a set of components that define what the rule will do. The components enable you to target certain types of traffic, based on the traffic's protocol, ports, sources, and destinations. In addition to firewall rules that you create, GCP has other rules that can affect incoming and outgoing traffic: ·          GCP doesn't allow certain IP protocols, such as GRE, within a VPC network ·          GCP always allows communication between a VM instance and its corresponding metadata server at 169.254.169.254 ·          Every network has two implied firewall rules which permit outgoing connections and block incoming connections. Firewall rules that you create can override these implied rules. ·          The default network is pre-populated with firewall rules t...