Google Cloud Fundamentals: Getting Started with App Engine Reviews

Greg M. · Reviewed больше 4 лет ago

Oleg P. · Reviewed больше 4 лет ago

Russell D. · Reviewed больше 4 лет ago

Edwin Eduardo P. · Reviewed больше 4 лет ago

Enrico A. · Reviewed больше 4 лет ago

chidozie I. · Reviewed больше 4 лет ago

David M. · Reviewed больше 4 лет ago

Siphesihle V. · Reviewed больше 4 лет ago

Natalia M. · Reviewed больше 4 лет ago

Lina A. · Reviewed больше 4 лет ago

Saranraj B. · Reviewed больше 4 лет ago

Jonathan G. · Reviewed больше 4 лет ago

Ralph V. · Reviewed больше 4 лет ago

Jasiel S. · Reviewed больше 4 лет ago

Luiz E. · Reviewed больше 4 лет ago

Vinicius M. · Reviewed больше 4 лет ago

dl-datcourseralicens08@ica.se S. · Reviewed больше 4 лет ago

Olivier J. · Reviewed больше 4 лет ago

Samantha B. · Reviewed больше 4 лет ago

Darek W. · Reviewed больше 4 лет ago

shinju p. · Reviewed больше 4 лет ago

Asfetaw A. · Reviewed больше 4 лет ago

OK

El Hadi M. · Reviewed больше 4 лет 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 больше 4 лет ago

Juan P. · Reviewed больше 4 лет ago