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