Review

Loading...

来自 Google Cloud 的课程

Google Cloud Platform Fundamentals: Core Infrastructure

6186 个评分

Google Cloud

Google Cloud Platform Fundamentals: Core Infrastructure

6186 个评分

课程 1（共 3 门，Specialization Networking in Google Cloud Platform）

<<< ATTENTION >>> Learners interested in Google Cloud Platform can continue to learn in either of our latest GCP infrastructure specializations. Option 1: The Developing Applications with Google Cloud Platform Specialization is available on Coursera. This brand-new Specialization teaches you to build secure, scalable, and intelligent cloud-native applications. Visit https://www.coursera.org/specializations/developing-apps-gcp for more details. Option 2: The Architecting with Google Cloud Platform Specialization is also available. This Specialization has updated, improved content that will help you if you are preparing for the Google Certified Professional - Cloud Architect exam. Head to https://www.coursera.org/specializations/gcp-architecture to explore the updated content. Google Cloud Platform Fundamentals: Core Infrastructure covers the fundamentals of Google Cloud Platform and is the first course in both specializations. This course introduces you to important concepts and terminology for working with Google Cloud Platform (GCP). You learn about, and compare, many of the computing and storage services available in Google Cloud Platform, including Google App Engine, Google Compute Engine, and Google Container Engine. Note: •Google services are currently unavailable in China.

从本节课中

Summary and Review

This module reviews the GCP services covered in this course and reminds learners of the differences among them. The module compares GCP compute services, GCP storage services, and important Google VPC networking capabilities.

与讲师见面

Google Cloud Training

In this short module, I look back on what we covered in this course.

Remember the continuum that this course discussed at the very beginning.

The continuum between managed infrastructure and dynamic infrastructure.

GCP's compute services are arranged along this continuum,

and you can choose where you want to be on it.

Choose Compute Engine if you want to deploy your application

in virtual machines that run on Google's infrastructure.

Choose Kubernetes Engine if you want instead to deploy

your application in containers that run on Google's infrastructure.

In a Kubernetes cluster you're defining control.

Choose App Engine instead if you just want to focus on your code,

leaving most infrastructure and provisioning to Google.

App Engine flexible environment lets you use any run time you want,

and gives you full control of the environment in which your application runs.

App Engine standard environment lets you choose from a set of standard

run times and offers finer grain scaling and scaled Azira.

To completely relieve yourself from the chore of managing infrastructure,

build or extend your application using Cloud Functions.

You supply chunks of code for business logic,

and your code get spun up on demand in response to events.

GCP offers a variety of ways to load balance in bound traffic.

Use Global HTTPS load balancing to put

your Web application behind a single anycast IP to the entire Internet.

It load balances traffic among all your back-end instances in regions around the world.

And it's integrated with GCP's Content Delivery Network.

If your traffic isn't HTTP or HTTPS,

you can use the global TCP or SSL Proxy for traffic on many ports.

For other ports or for UDP traffic,

use the regional load balancer.

Finally, to load balance the internal tiers of multi-tier application,

use the internal load balancer.

GCP also offers a variety of ways for you to interconnect

your On-premises or other cloud networks with your Google VPC.

It's simple to set up a VPN and you can use cloud router to make it dynamic.

You can also peer with Google,

edits many worldwide points of presence either directly or through a carrier partner.

Or if you need a service level agreement and can adopt one of

their required network typologies, use Dedicated Interconnect.

Consider using Cloud datastore if you need to store structured objects,

or if you require support for transactions and SQL-like queries.

Consider using Cloud Bigtable if you need to store

a large amount a single key data, especially structured objects.

Consider using Cloud Storage if you need to store immutable binary objects.

Consider using Cloud SQL or Cloud Spanner if you need

full SQL support for an online transaction processing system.

Cloud SQL provides terabytes of capacity while

Cloud Spanner provides petabytes and horizontal scalability.

Consider BigQuery if you need interactive querying in

an online analytical processing system with petabytes of scale.

I'd like to zoom into one of those services we just discussed,

Cloud Storage and remind you of its four storage classes.

Multi-regional and regional are the classes for warm and hot data.

Use Multi-regional especially for content that's being served to a global Web audience.

And use Regional for working storage for compute operations.

Nearline and Coldline are the classes for,

as you'd guess cooler data.

Use Nearline for backups and for infrequently accessed content.

And use Codeline for archiving and disaster recovery.

探索我们的目录

免费加入并获得个性化推荐、更新和优惠。

Coursera 致力于普及全世界最好的教育，它与全球一流大学和机构合作提供在线课程。

© 2018 Coursera Inc. 保留所有权利。

通过 App Store 下载

通过 Google Play 获取