Google Cloud Fundamentals: Getting Started with App Engine Reviews

Greg M. · Reviewed over 4 years ago

Oleg P. · Reviewed over 4 years ago

Russell D. · Reviewed over 4 years ago

Edwin Eduardo P. · Reviewed over 4 years ago

Enrico A. · Reviewed over 4 years ago

chidozie I. · Reviewed over 4 years ago

David M. · Reviewed over 4 years ago

Siphesihle V. · Reviewed over 4 years ago

Natalia M. · Reviewed over 4 years ago

Lina A. · Reviewed over 4 years ago

Saranraj B. · Reviewed over 4 years ago

Jonathan G. · Reviewed over 4 years ago

Ralph V. · Reviewed over 4 years ago

Jasiel S. · Reviewed over 4 years ago

Luiz E. · Reviewed over 4 years ago

Vinicius M. · Reviewed over 4 years ago

dl-datcourseralicens08@ica.se S. · Reviewed over 4 years ago

Olivier J. · Reviewed over 4 years ago

Samantha B. · Reviewed over 4 years ago

Darek W. · Reviewed over 4 years ago

shinju p. · Reviewed over 4 years ago

Asfetaw A. · Reviewed over 4 years ago

OK

El Hadi M. · Reviewed over 4 years ago

Great Lab. App Engine is great since it is PaS and hence it allows to developer to focus only on our code. Obviously the use of App Engine or Kubernetes Container depends of the customer needs. I already deployed a Spring Microservice with Google App Engine thanks to the Google Spring Course. This lab is interesting for me because we used App Engine with Python Application. It know very well this type of application. This is a Flask Python Application, i built an entire Python product with Flask Python. I know very well venv python environment. For the packaging of the application i notice the use of the requirements.txt with the library dependency. In the Python product that i built instead i used a new packaging mechanism based on setup.py (python3 setup.py install) that allows to install the application as a pip library (it appears in the result of the command pip3 list)

CIRIELLO V. · Reviewed over 4 years ago

Juan P. · Reviewed over 4 years ago