关于“Google Cloud Fundamentals: Getting Started with App Engine”的评价

Greg M. · 已于 over 4 years前审核

Oleg P. · 已于 over 4 years前审核

Russell D. · 已于 over 4 years前审核

Edwin Eduardo P. · 已于 over 4 years前审核

Enrico A. · 已于 over 4 years前审核

chidozie I. · 已于 over 4 years前审核

David M. · 已于 over 4 years前审核

Siphesihle V. · 已于 over 4 years前审核

Natalia M. · 已于 over 4 years前审核

Lina A. · 已于 over 4 years前审核

Saranraj B. · 已于 over 4 years前审核

Jonathan G. · 已于 over 4 years前审核

Ralph V. · 已于 over 4 years前审核

Jasiel S. · 已于 over 4 years前审核

Luiz E. · 已于 over 4 years前审核

Vinicius M. · 已于 over 4 years前审核

dl-datcourseralicens08@ica.se S. · 已于 over 4 years前审核

Olivier J. · 已于 over 4 years前审核

Samantha B. · 已于 over 4 years前审核

Darek W. · 已于 over 4 years前审核

shinju p. · 已于 over 4 years前审核

Asfetaw A. · 已于 over 4 years前审核

OK

El Hadi M. · 已于 over 4 years前审核

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. · 已于 over 4 years前审核

Juan P. · 已于 over 4 years前审核