What are the benefits of implementing CI / CD environments at the project / GAE level versus service / module level?

The Google Developer Simulation Environment offers two approaches for implementing different CI / CD environments for GAE applications.

  • based on different services (which were formerly called modules) within the same project / application:

If you decide to create a microservice application using only a few services, you can create one App Engine project for each of your environments and name them accordingly, for example web-app-dev, web-app-qaand web-app-prod.

  • based on different projects / applications:

Alternatively, if you choose to create an application using mikroservisov several projects, you can achieve the same separation between media, but you will need to use more projects, such as web-app-dev, web-app-prod, user-service-devand user-service-prod. You will need to use code templates so that projects devcall only other projects devand prodprojects call only other projects prod.

enter image description here

The phrases in the above snippets of documentation seem to suggest that the two approaches will be roughly equivalent, but there is at least one significant difference between the two approaches: the project / application-based approach provides data isolation, while the service / no module - data storage and memcache are shared by all services.

:

:

enter image description here

: , , - ? -, ?

+6
1

, , IAM.

, , ( , prod , dev ?). , , prod vs dev.

, , . , - VPN , , , .

+5

Source: https://habr.com/ru/post/1016303/


All Articles