Performance implication due to use of Schema Validation

Vijay Akula 66 Reputation points
2022-06-07T23:08:43.857+00:00

We are considering enabling schema validation for our REST API to validate the incoming JSON requests against the schema in the Open API YAML. Plan is to use validate-content policy, but we were wondering there would be any performance impact as such, also wondering if it would potentially increase the licensing costs due the increased use of processing power due to enabling schema validation.

Azure API Management
Azure API Management
An Azure service that provides a hybrid, multi-cloud management platform for APIs.
2,453 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. JananiRamesh-MSFT 29,266 Reputation points
    2022-06-09T18:14:34.303+00:00

    @Vijay Akula Thanks for reaching out. From the description I understand that you wanted to enable schema validation for your Rest API to validate the incoming JSON request using validate-content policy. There will not be any licensing cost but they will be a performance impact.

    Every policy would have a performance impact and in this case it all depends on number of policies you write and size of your schema. It wouldn't be possible to say how much the impact would exactly be but you can monitor the CPU usage in metrics and you can always scale out whenever its required.

    To benefit the community find the right answers, please do mark the post which was helpful by clicking on Accept Answer’ & ‘Up-Vote’.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.