Is Google Cloud Platform able to use QUIC protocol or it is only limited to HTTP/2? If not, any Cloud Platform is supporting QUIC protocol today?
It is now possible, you can see their blog post or documentation.
Related
How do they differ? and what is the use case for each?
Is it possible for me to use one exclusively, such as if I'm more familiar with .NET I could do everything using the Client Library (for .NET) that I could with python and the SDK?
Google Cloud SDK https://cloud.google.com/sdk/docs/
Google Cloud Client Libraries https://cloud.google.com/apis/docs/cloud-client-libraries
The Cloud SDK is a set of command line tools (gcloud, gsutil, and bq). The use of the term 'SDK' here seems to be misleading and they should probably be called Google Cloud Tools or Google Cloud CLI.
The Cloud Client Libraries are the latest set of libraries available in various languages that you can program against.
There's also an older set of client libraries called the Google API Client Libraries. They're autogenerated from Google service interfaces and are simple wrappers to REST calls. You should probably use the newer Cloud Client Libraries if you can as they are more idiomatic and provide better abstraction.
Jarmod's answer is excellent.
Could I do everything using the Client Library (for .NET) that I could
with python and the SDK?
Almost everything. Exceptions I know:
.NET code can't run on good ole Google App Engine Standard. You can still run your .NET code in Google Compute Engine (on Windows) or Google App Engine Flexible Environment (.NET core code on Linux.)
Tensorflow only has a Python API.
Bigtable doesn't have a .NET API.
https://github.com/GoogleCloudPlatform/dotnet-docs-samples shows how to call many, but not all of the Google Cloud APIs.
Recently (2nd Dec 2014) Google announced that Google Cloud Platform is now PCI-DSS compliant.
Since then there have been no updates on the same. I have checked the public forums, stackoverflow, google developers site to no avail.
I am looking to develop my app on the cloud platform, but require all the necessary steps that should be followed in order to be compliant. Does anyone has any ideas regarding the same?
Google have certified their platform is compliant.
If you are building an application, you will need to follow the guidelines to ensure that the software you are writing is compliant.
Also, you will need to follow the guidelines when configuring Google's platform (for example, if you open up all firewall ports and set the root password on a bunch of GCE instances to "password" then your application will NOT be compliant).
I expect that if you have a premier account you could request a copy of the PCI-DSS certificate from Google - but it's only part of the picture.
Does Google AppEngine support OAuth 2.0? And, if so, can you suggest a good tutorial?
The short answer is yes, and they are moving access to their APIs to use 2.0. I have not come across any great tutorials out there but Google is building on their documentation for this. They do have code samples for non App Engine stuff out there.
https://developers.google.com/accounts/docs/OAuth2
For Google APIs there are libraries in:
Python
Java
Go
that you can use on App Engine to access Google APIs using OAuth 2.0. The Python and Java libraries are built on top of a generic library that enables OAuth 2.0 functionality, so if you're accessing non-Google APIs that may be helpful. There may be libraries for other API platforms as well, but your mileage may vary.
I have read a few articles that say in order to have a PCI compliant cloud solution you need to have a private cloud environment and cannot use google app engine. Is it possible to create a PCI compliant website that specifically stores credit card information and personal user data in a google app engine application. Please list factual, non esoteric reasons why this may not be possible or a list of high level tasks directives that would need to and can be done by an app engine developer.
"No matter what you do however, your hosting provider has to claim support of PCI compliance."... per #maple_shaft
Doing PCI compliance all by yourself is woefully difficult. The details are available here.
The most common pattern for payments on App Engine is to utilize a payment gateway which bears the onus of PCI compliance.
Typically, these services provide you with an authorization token to correlate with users that you can use in order to create payments.
Popular Python Gateways
Here are some links to payment gateways to get you started.
Braintree, I have used this in production on app engine and it works great
Stripe, a new-comer to the field which looks really promising.
It might be interesting to know that Google Cloud Platform has recently became PCI DSS certification. Since Google App Engine is build on it I assume it should be "safe" to use it as well.
I was using GAE with Gapps on my domain, however it seems that ghs.google.com is unavailable in China.
How can I use GAE on my domain without Gapps?
Edit: A solution I'm considering is using something like a proxy. This way the firewall doesnt see google. By the way, my site is not banned because of its content, it can be acessed normally using appspot. The problem comes from google apps redirections.
Any ideas how I can setup something like this?
According to this answer you cannot.
Petition your government for redress of grievance? Yes, I know that's not such a hot idea in 中華人民共和國.
Google is quote interested in access to their services generally, but isn't (yet) in a position to tell governments what to do directly.
AppScale is an open-source implementation of the Google App Engine cloud computing interface. It is being developed by researchers in the UC Santa Barbara RACELab.
AppScale enables execution of Google App Engine (GAE) applications on virtualized cluster systems. In particular, AppScale enables users to execute GAE applications using their own clusters with greater scalability and reliability than the GAE SDK provides.
Moreover, AppScale executes automatically and transparently over cloud infrastructures such as the Amazon Web Services (AWS) Elastic Compute Cloud (EC2) and Eucalyptus, the open-source implementation of the AWS interfaces.