You recently migrated a monolithic application to Google Cloud by breaking it down into microservices. One of the microservices is deployed using Cloud Functions. As you modernize the application, you

Question

Options

• ALeave the original Cloud Function as-is and deploy a second Cloud Function with the new API.
• BLeave the original Cloud Function as-is and deploy a second Cloud Function that includes only
• CLeave the original Cloud Function as-is and deploy a second Cloud Function with the new API.
• DRe-deploy the Cloud Function after making code changes to support the new API. Requests for

• A
  11% (4)
• B
  5% (2)
• C
  82% (31)
• D
  3% (1)

Explanation

https://cloud.google.com/endpoints/docs/openapi/versioning-an-api#backwards-incompatible When you make changes to your API that breaks your customers' client code, as a best practice, increment the major version number of your API. Endpoints can run more than one major version of an API concurrently. By providing both versions of the API, your customers can pick which version they want to use and control when they migrate to the new version.

No community discussion yet for this question.