List of specifications for your API Management project (Part 2/2)

This blog post continues the previous blog post: “List of specifications for your API Management project (Part 1/2)” and provides you with another series of questions to add to your specification document.

#6 Integration Extensibility – Don’t underestimate the complexity of your company

  • “Complexity is something we try to avoid, but if we need to extend the capabilities of your solution to accommodate our architecture and integration requirements, how flexible is your solution to allow for this?”
  • “Our company has an “API First” strategy and IT mandate. Which means, if we need to leverage our partners’ solutions as an ecosystem of capabilities – are there APIs exposed for your solution to allow us integration into existing software solutions and business processes?”

#7 Monitoring report & Analytics – You can’t control what you can’t measure

  • “The solution should support near real-time anomaly analysis to determine sudden changes in behavior (e.g. sudden increasing or decreasing error counts, load, response times).”
  • “What tools are available out of the box to do various kinds of trend analysis and inspection of anomalies?”
  • “What level of operational visibility can the solution provide based on API traffic flowing through the system?”
  • “Is there auditing of administrator activity?”

#8 Development – You will need customization sooner than expected

  • “Does your product provide the ability to create custom processes that can be packaged and re-used within the policy creation?”
  • “Does your solution support Software Developers authenticating with their CUSTOMER username and password to perform the deployment?”
  • “Can your solution very quickly rollback a deployment when incidents are encountered with API Endpoint due to the deployment of a badly-coded API Endpoint?”
  • “Explain how your solution supports a full lifecycle for API including deprecation of APIs without impacting production.”

#9 Mobile – Build for now and the future

  • “Our Mobile emphasis on user experience and good client design and development is paramount. How does your mobile API development tool support this?”
  • “An architecture for elastic scalability: mobility guarantees anywhere, anytime demand for data and services. How does your solution support this methodology?”
  • “The MBaaS solution should also provide a collection of out-of-the-box integrations for some of the most popular systems, both enterprise (Salesforce, Microsoft, Box, etc.) and public (Twitter, Facebook, PayPal, DropBox, etc.), as well as mobile-specific services such as push notification. How does your MbaaS solution support these?”

#10 Deployment scalability – Prepare for growth

  • “What deployment options are available?”
  • “Describe how the product scales for on-premises or cloud implementation.”
  • “The solution must support active/active clustering across multiple  geographically-separated locations.”
  • “Can the product be integrated into an existing Continuous Delivery / Continuous Integration Pipeline process?”

#11 Ease of Administration

  • “Does your solution provide a single console for managing gateways (multiple clusters) residing in different environments?”
  • “Describe how the administration can be centralized.”
  • “Do you have a graphical UI for developing policies and orchestration policy flows?”
  • “Do you have the ability to integrate 3rd-party solutions without coding? How this is accomplished?”


Please enter your comment!
Please enter your name here