Blog from March, 2019

Enterprise architecture has deemed that you need to use Apigee for some or all of your connections - here is your conclusive guide to ensuring your service onboarding is seemless!

Step 1 - Determine what Apigee is delivering

Step 2 - Gather the API requirements into your deliverables here

If you are publishing a service that services an enterprise capability the requirements will be more stringent than if you need a proxy connection secured. Since your Apigee requirements are dependent on your overall solution blueprint - its critical to ensure your project’s Architect has validated the specific use cases.