Migrating APIs from Azure to Apigee

[#1]

Hi, I am looking at migrating APIs from existing Azure API manager to Apigee. Any guidance on the implementation approach would help. Thanks.

[vinodbiradar059]

@Dino Could please help us on here !

[dchiesa1]

Sorry, I don't know the answer to that. I . don't think there is a "migration toolset".

If you describe what you use Azure API Management for, in general terms, I can describe how to do it in Apigee Edge, and can provide additional pointers on what you need to do to make it happen.

By "general terms" I mean something like this:

• issue Oauth tokens via client credentials grant type
• verify an OAuth Token presented in the Authorization header
• check that the token has scopes XXX and YYY
• route to a backend https://api.example.com
• ...etc...

[aramkrishna6]

Hi @dchiesa1   

1. Do we have any existing tool / recommendations recently known for such migration ?
2. What type of recommendations/ architecture/leading practices or findings should be covered for such migrations to Apigee from Azure API Manager?
3. Most of current APIs are client credentials and 3 legged OAUTH.
4. All APIs are hosted in Drupal portal.
5. For features, which are already covered in Azure API Manager, should that be also migrated ?

[API-Evangelist]

My guidance is first stop comparing the products 🙂 as each products has pros/cons & with all open mind one  should start exploring the new product (in your case apigee product). There will definitely a learning curve and at times   you feel something isn't working but if we look thru amazing detailed documentation you will get started in few hours/days & a cool community who helps along the journey.

Few suggestions:

1. This is the best time to categorize your existing api's based of audience who will be consuming  (public,private & partner)

2. Choose a good API Design tools (stoplight(preferred) ,Swaggerhub etc )

3. Define good API design guidelines  & a better time to re-structure the path's based of namespace - account,payment etc

4. What are the key API Authentication and Authorization which exists as of existing platform and discuss if there is a opportunity to move to new model(don't think lift shift approach but always think of improving security models when ever there is a opportunity -https://docs.apigee.com/api-platform/reference/policies/reference-overview-policy check security policies)

5. Assess your existing apis & score the api's & improve with better security to avoid any api threats (https://docs.apigee.com/api-platform/faq/owasp-top-api-threats)

0.Document well all your api contracts as per the design guidelines

1.Define your apigee orgs based of your business models so that you can have the proxies maintained & operated easily.

2.Start with basic standards on naming - apis,policies etc & then think about what are the key re-usable components(eg: security,threat protection,logging,error handling) which can be used as part of shared flows (https://docs.apigee.com/api-platform/fundamentals/shared-flows)

3.Once you have defined all the key shared flows now start by designing what is the best template which covers all the base components(based of different polices available https://docs.apigee.com/api-platform/reference/policies/reference-overview-policy)  of a given proxy which can be shared by different developers who can reuse.

4. Masking/encrypting approach all PII/PCI etc data (https://docs.apigee.com/api-platform/security/data-masking)

5.Logging to external tools

6. CI/CD approach on deploying api's from open api

7.Explore Analytics - https://docs.apigee.com/api-platform/analytics/analytics-services-overview

8.Performance tuning exercise

9.Explore Support  section https://cloud.google.com/apigee/docs/support

10. Definitely this will help along the way https://docs.apigee.com/api-platform/troubleshoot/troubleshooting-guide-pdf

Good luck.

[aramkrishna6]

Hi @API-Evangelist  Thanks for detailed reply 

1.If already have  Apigee SaaS and Micro-gateway organizations for Hybrid use cases, understand that  Apigee Microgateway is very well supported, but did not see any difference of Apigee Microgateway with Apigee Hybrid

2. How do we design the Future state model ? when motive is to move to mobile support. One way will be looking @ current state and defining the reference architecture .Do we have any reference on same with respect to such apigee migrations with good details documented for reference ?

3. Any tips on designing the Orgs and Env for such suture state having the Apigee SaaS with Apigee Microgateway ?

4.  Not sure, if “API Monitoring” in Apigee SaaS can support and monitor APIs from Apigee-Microgateway as  well?