Google Cloud Platfrom
1
Build, test, deploy and scale with ease.
Why Cloud?
• Flexibility and scalability
• Cost effectiveness
• Reliability
• Security
• Quick deployment time
• Low cost
2
Google
8 cloud products with 1 billion users
3
Why Google Cloud?
• High-Performance, scalable VMs
• Measured service & pay-as-you-go pricing model
• Global networks, over 33 geographic locations & multiple availability zones
• Automated container management
• Serverless Applications on Google’s Infrastructure
• Allows developers to focus on development
4
Scale
• On-demand delivery of resources
• Automatically scale to handle demanding load
• Automatic scaling down when resources are no longer being used.
• Use-case: Pokemon go.
5
Focus on product
• Managed services
• Handy developer tools and API’s
• Advanced management tools and console
• Highly secure.
6
Availability regions
7
https://cloud.google.com/about/locations
Networks
8
Google Cloud Platform
9
Compute
Compute
Engine
Container
Engine
App Engine Cloud
Functions
Storage
Bigtable
Cloud
Storage
Cloud SQL Cloud
Datastore
Big Data
Big
Query
Pub/Sub Dataflow Dataproc Datalab
Machine Learning
Natural Lang
API
Vision
API
Machine
Learning
Search
API
Translate
API
Computing
App Engine (PaaS)
PaaS for apps and backends.
Compare to Elastic Beanstalk or Web Apps.
10
Container (Kubernettes) Engine
Run containerized applications.
Compare to ECS or Azure Container Service.
Compute Engine (SaaS)
Scalable, high performance VMS
Compare to EC2 or ARM VMs
Cloud Functions
Event-driven serverless compute platform.
Compare to Lambda or Azure Functions.
Compute Engine (GCE)
• Compute Engine is an Infrastructure-as-a-Service
• Run large-scale workload on virtual machines hosted on Google
infrastructure.
• Configure, customize the VM that fits your need.
• Complete control over VM’s and runtime.
• You have to manually configure your infrastructure to handle scalability by
using Load Balancer, etc.
11
Compute Engine
• Mostly do-it-yourself, which can be challenging
to do adequately for reliability and security.
• More management overhead.
• Autoscaling is based on GCE instances, which
can be slower than App Engine
• Tendency is to install software on snowflake
GCE instances, which can be some effort.
Pros Cons
• Easy to ramp up, no need to learn Google
platform or how container container.
• Complete control. You can leverage many
Compute Engine features directly and install the
latest of all your favorite stuff to stay on the
bleeding edge.
• No need for public IPs.
• You can leverage the Container-Optimized OS
for running Docker containers
12
App Engine (GAE)
• App Engine is a Platform-as-a-Service
• Run you App on fully scalable and fully-managed platform
• Since GAE is fully scalable, it automatically scale up/down to serve the
traffic
• Use engine, when you just want to focus on your code and not worry about
maintenance.
• Currently supports Python, PHP, Java, NodeJS, .NET, Ruby and **Go
languages.
13
App Engine
• Generally more constrained
• Although this is good for rapid autoscaling,
many apps can benefit from larger instances,
such as GCE instance sizes up to 96 cores.
• Networking is not integrated
• Cannot put App Engine behind a Google Cloud
Load Balancer.
• Limited to supported runtimes. Supports Python
2.7, Java 7 and 8, Go 1.6-1.9, and PHP 5.5. In
Java, partial support for Servlets but not the full
J2EE standard.
Pros Cons
• Very economical for low traffic apps.
• Auto-scaling is fast.
• Version management and traffic splitting are fast
and convenient
• Minimal management, developers need to focus
only on their app.
• Access to Datastore is fast.
• Access to Memcache is supported.
• App Engine sandbox is very secure. Compared
with the development on GCE or other virtual
machines.
14
Databases
Cloud Datastore
NoSQL document database service
15
Cloud Bigtable
NoSQL wide column database services
Compare to DynamoDB or Azure Cosmo DB.
Cloud SQL
MySQL and PostgreSQL databases
Compare to RDS or Azure DB
Firebase
Store and sync data realtime
Cloud Datastore
• Fully managed relational mySQL database
• Automatic patch, backup, replication and other db management to ensure
high availability and performance.
16
Storage
Cloud Filestore
High performance file storage
Compare to EFS or Azure files
17
Persistance Disk
Block storage for VM instances
Compare with EBS or Page Blob
Cloud Storage
Object storage with global edge-caching
Compare with S3 and Blob storage
Cloud Memory store
Fully managed in-memory data store
Currently in BETA
Cloud Firestore
NoSQL document database service
Syncing for mobile apps
Cloud storage
• Durable and highly available object storage service
• Global edge caching that allow object access from any locations
18
Networking
Cloud Armor
Protect from DoS and web attacks
19
Cloud Load balancer
Compare to ELB or Azure Load balancer /
Application gateway
Virtual Private Cloud
VPC network for GCP resources
Cloud CDN
Compare to CloudFront, EdgeCast or Akamai
Cloud DNS
Compare to S3 or Azure DNS
Management
Logging
Logging for applications on GCP and AWS
Compare to CloudTrail or Azure Usage API
20
Monitoring
Monitoring for applications on GCP and AWS.
Compare to CloudWatch or Azure Monitor.
Stackdriver
Monitor, logging and diagnostics
Find performance bottlenecks in production.
Investigate code behavior and identify
application errors.
Cloud Deployment manager
Manage cloud resources with simple templates
Compare to CloudFormation & Azure resource
manager.
Developer tools
Container registry
Fast, private image storage.
Compare to CodePipeline.
21
Cloud Shell
Command-line management from any browser.
Compare to CLI.
Cloud SDK
CLI for GCP products and services.
Compare to AWS SDK or Azure SDK.
IntelliJ, PowerShell, VS, Eclipse
plugins
Monitoring for applications on GCP and AWS.
Compare to CloudWatch or Azure Monitor.
Security features
Enterprise grade access control
• Authorize access and visibility to manage cloud resources.
Cloud Key Management Service
• Manage encryption keys on GCP
Cloud Identity-Aware Proxy
• Controls access to your cloud applications running on Google Cloud Platform
Security key enforcement
• 2-step verification with a security key uses cryptography to provide two-way
verification.
22
Security features..
23
Automated Cloud Security Scanner
• Automatic web security scanner for common vulnerabilities.
• Scan and detect common vulnerabilities, including cross-site-scripting (XSS),
Flash injection, mixed content (HTTP in HTTPS), and outdated/insecure libraries.
Cloud Security Command Center
• A comprehensive security and data risk platform that gather data, identify threats,
and act on them before they result in business damage
< Thank you :) />
Nilanchala Panigrahy
twitter.com/@npanigrahy | stacktips.com
24
References
• https://cloud.google.com/docs/
• https://cloud.google.com/pricing/
• https://cloud.google.com/about/locations
• https://cloud.google.com/security/

Introduction to Google Cloud Services / Platforms

  • 1.
    Google Cloud Platfrom 1 Build,test, deploy and scale with ease.
  • 2.
    Why Cloud? • Flexibilityand scalability • Cost effectiveness • Reliability • Security • Quick deployment time • Low cost 2
  • 3.
    Google 8 cloud productswith 1 billion users 3
  • 4.
    Why Google Cloud? •High-Performance, scalable VMs • Measured service & pay-as-you-go pricing model • Global networks, over 33 geographic locations & multiple availability zones • Automated container management • Serverless Applications on Google’s Infrastructure • Allows developers to focus on development 4
  • 5.
    Scale • On-demand deliveryof resources • Automatically scale to handle demanding load • Automatic scaling down when resources are no longer being used. • Use-case: Pokemon go. 5
  • 6.
    Focus on product •Managed services • Handy developer tools and API’s • Advanced management tools and console • Highly secure. 6
  • 7.
  • 8.
  • 9.
    Google Cloud Platform 9 Compute Compute Engine Container Engine AppEngine Cloud Functions Storage Bigtable Cloud Storage Cloud SQL Cloud Datastore Big Data Big Query Pub/Sub Dataflow Dataproc Datalab Machine Learning Natural Lang API Vision API Machine Learning Search API Translate API
  • 10.
    Computing App Engine (PaaS) PaaSfor apps and backends. Compare to Elastic Beanstalk or Web Apps. 10 Container (Kubernettes) Engine Run containerized applications. Compare to ECS or Azure Container Service. Compute Engine (SaaS) Scalable, high performance VMS Compare to EC2 or ARM VMs Cloud Functions Event-driven serverless compute platform. Compare to Lambda or Azure Functions.
  • 11.
    Compute Engine (GCE) •Compute Engine is an Infrastructure-as-a-Service • Run large-scale workload on virtual machines hosted on Google infrastructure. • Configure, customize the VM that fits your need. • Complete control over VM’s and runtime. • You have to manually configure your infrastructure to handle scalability by using Load Balancer, etc. 11
  • 12.
    Compute Engine • Mostlydo-it-yourself, which can be challenging to do adequately for reliability and security. • More management overhead. • Autoscaling is based on GCE instances, which can be slower than App Engine • Tendency is to install software on snowflake GCE instances, which can be some effort. Pros Cons • Easy to ramp up, no need to learn Google platform or how container container. • Complete control. You can leverage many Compute Engine features directly and install the latest of all your favorite stuff to stay on the bleeding edge. • No need for public IPs. • You can leverage the Container-Optimized OS for running Docker containers 12
  • 13.
    App Engine (GAE) •App Engine is a Platform-as-a-Service • Run you App on fully scalable and fully-managed platform • Since GAE is fully scalable, it automatically scale up/down to serve the traffic • Use engine, when you just want to focus on your code and not worry about maintenance. • Currently supports Python, PHP, Java, NodeJS, .NET, Ruby and **Go languages. 13
  • 14.
    App Engine • Generallymore constrained • Although this is good for rapid autoscaling, many apps can benefit from larger instances, such as GCE instance sizes up to 96 cores. • Networking is not integrated • Cannot put App Engine behind a Google Cloud Load Balancer. • Limited to supported runtimes. Supports Python 2.7, Java 7 and 8, Go 1.6-1.9, and PHP 5.5. In Java, partial support for Servlets but not the full J2EE standard. Pros Cons • Very economical for low traffic apps. • Auto-scaling is fast. • Version management and traffic splitting are fast and convenient • Minimal management, developers need to focus only on their app. • Access to Datastore is fast. • Access to Memcache is supported. • App Engine sandbox is very secure. Compared with the development on GCE or other virtual machines. 14
  • 15.
    Databases Cloud Datastore NoSQL documentdatabase service 15 Cloud Bigtable NoSQL wide column database services Compare to DynamoDB or Azure Cosmo DB. Cloud SQL MySQL and PostgreSQL databases Compare to RDS or Azure DB Firebase Store and sync data realtime
  • 16.
    Cloud Datastore • Fullymanaged relational mySQL database • Automatic patch, backup, replication and other db management to ensure high availability and performance. 16
  • 17.
    Storage Cloud Filestore High performancefile storage Compare to EFS or Azure files 17 Persistance Disk Block storage for VM instances Compare with EBS or Page Blob Cloud Storage Object storage with global edge-caching Compare with S3 and Blob storage Cloud Memory store Fully managed in-memory data store Currently in BETA Cloud Firestore NoSQL document database service Syncing for mobile apps
  • 18.
    Cloud storage • Durableand highly available object storage service • Global edge caching that allow object access from any locations 18
  • 19.
    Networking Cloud Armor Protect fromDoS and web attacks 19 Cloud Load balancer Compare to ELB or Azure Load balancer / Application gateway Virtual Private Cloud VPC network for GCP resources Cloud CDN Compare to CloudFront, EdgeCast or Akamai Cloud DNS Compare to S3 or Azure DNS
  • 20.
    Management Logging Logging for applicationson GCP and AWS Compare to CloudTrail or Azure Usage API 20 Monitoring Monitoring for applications on GCP and AWS. Compare to CloudWatch or Azure Monitor. Stackdriver Monitor, logging and diagnostics Find performance bottlenecks in production. Investigate code behavior and identify application errors. Cloud Deployment manager Manage cloud resources with simple templates Compare to CloudFormation & Azure resource manager.
  • 21.
    Developer tools Container registry Fast,private image storage. Compare to CodePipeline. 21 Cloud Shell Command-line management from any browser. Compare to CLI. Cloud SDK CLI for GCP products and services. Compare to AWS SDK or Azure SDK. IntelliJ, PowerShell, VS, Eclipse plugins Monitoring for applications on GCP and AWS. Compare to CloudWatch or Azure Monitor.
  • 22.
    Security features Enterprise gradeaccess control • Authorize access and visibility to manage cloud resources. Cloud Key Management Service • Manage encryption keys on GCP Cloud Identity-Aware Proxy • Controls access to your cloud applications running on Google Cloud Platform Security key enforcement • 2-step verification with a security key uses cryptography to provide two-way verification. 22
  • 23.
    Security features.. 23 Automated CloudSecurity Scanner • Automatic web security scanner for common vulnerabilities. • Scan and detect common vulnerabilities, including cross-site-scripting (XSS), Flash injection, mixed content (HTTP in HTTPS), and outdated/insecure libraries. Cloud Security Command Center • A comprehensive security and data risk platform that gather data, identify threats, and act on them before they result in business damage
  • 24.
    < Thank you:) /> Nilanchala Panigrahy twitter.com/@npanigrahy | stacktips.com 24 References • https://cloud.google.com/docs/ • https://cloud.google.com/pricing/ • https://cloud.google.com/about/locations • https://cloud.google.com/security/