Solved: Migrate proxies from Apigee SaaS to Hybrid and vic...

Neeraja · 11-13-2021 10:53 AM

Hi @dino @Former Community Member

How quickly we can migrate proxies from Apigee SaaS to Hybrid and Hybrid to SaaS?

Do we have any checklist or prior learnings on this topic please?

Do we need to consider any points, any precautions to be taken before doing this migration?

Appreciate your thoughts on this

Thanks,

Neeraja

dchiesa1

SaaS vs hybrid is ... not specific enough.

Really there are three options worth discussing. Apigee Edge, Apigee X, and Apigee hybrid.

Edge and X are both SaaS. Edge is the name of the version of Apigee that was first launched in 2013. Apigee X was launched in November 2020. Apigee hybrid was launched in November 2019.

While Edge and X share the deployment model (SaaS), X and hybrid share the same architecture. X and hybrid share a common code base, and share a common control plane in the google cloud. New features for Apigee accrue to the X/hybrid architecture.

So if your question is, "how can we migrate proxies from X to hybrid, and from hybrid to X?", the answer is: just point your CI/CD to a different organization. The administrative model for interfacing with proxies is exactly the same for X and hybrid. The feature set is the same, approximately. It's not exactly the same at all times , primarily because of differences in release timelines. Sometimes hybrid gets a new release, and it then has a few features X does not have. Then X will get a new release, and it is "ahead" of hybrid. But in general they're on the same code base and the feature set is "eventually consistent"!!

If your question is, "how can we migrate proies from Edge to hybrid and hybrid to Edge?", the answer is more complicated. There are a few things supported in hybrid that are not supported in Edge, and there are a few things in Edge that are not supported in hybrid. The basic model is the same - you still think in terms of API Proxies, and policies, and resources and so on. But there are minor changes you need to manage.

Unfortunately I am not aware of a documentation link that I can point you to, that outlines these differences definitively. Here are some of the main differences:

not available in hybrid (and X), available in Edge: OAuthV1 policies, ConcurrentRateLimit, VirtualHosts, Extensions, Hosted Targets
available in hybrid (and X) but not available in Edge: CORS policy, PropertySets, DialogFlow policies, ExternalCallout, PubSub policy, Data Capture, Trace Capture
KVMs in X and hybrid are always encrypted

View solution in original post

dchiesa1

SaaS vs hybrid is ... not specific enough.

Really there are three options worth discussing. Apigee Edge, Apigee X, and Apigee hybrid.

Edge and X are both SaaS. Edge is the name of the version of Apigee that was first launched in 2013. Apigee X was launched in November 2020. Apigee hybrid was launched in November 2019.

While Edge and X share the deployment model (SaaS), X and hybrid share the same architecture. X and hybrid share a common code base, and share a common control plane in the google cloud. New features for Apigee accrue to the X/hybrid architecture.

So if your question is, "how can we migrate proxies from X to hybrid, and from hybrid to X?", the answer is: just point your CI/CD to a different organization. The administrative model for interfacing with proxies is exactly the same for X and hybrid. The feature set is the same, approximately. It's not exactly the same at all times , primarily because of differences in release timelines. Sometimes hybrid gets a new release, and it then has a few features X does not have. Then X will get a new release, and it is "ahead" of hybrid. But in general they're on the same code base and the feature set is "eventually consistent"!!

If your question is, "how can we migrate proies from Edge to hybrid and hybrid to Edge?", the answer is more complicated. There are a few things supported in hybrid that are not supported in Edge, and there are a few things in Edge that are not supported in hybrid. The basic model is the same - you still think in terms of API Proxies, and policies, and resources and so on. But there are minor changes you need to manage.

Unfortunately I am not aware of a documentation link that I can point you to, that outlines these differences definitively. Here are some of the main differences:

not available in hybrid (and X), available in Edge: OAuthV1 policies, ConcurrentRateLimit, VirtualHosts, Extensions, Hosted Targets
available in hybrid (and X) but not available in Edge: CORS policy, PropertySets, DialogFlow policies, ExternalCallout, PubSub policy, Data Capture, Trace Capture
KVMs in X and hybrid are always encrypted

Migrate proxies from Apigee SaaS to Hybrid and vice versa