Usecase 2: Schema changes for improved performance
In a customer project comprising of multiple schemas (more than 50), it was observed that the latency for a single request -response was high, that is around few seconds.
The project mainly included multiple REST services as shown in the following image.
Some of the schemas in the project are shown in the following image.
Analysis confirmed that the schema operations were heavy with the current design implementation which contributed to the high latency.
Testing and Measurement
The testing was focused on the aspects listed below:
- With the default settings, a test was run for a single request and the total latency was measured from the logs.
- Few changes were made in the schema definition where the include tags were replaced with import, and the test was repeated and time was measured. For more information, see Performance Improvement Use Case - Schema changes for better performance
- If the schemas in the project consist of include, these can be replaced with imports as shown in the example in the section, Performance Improvement Use Case - Schema changes for better performance. This reduces the time considerably.
- This design implementation reduced the latency by almost 95 %.
Copyright © Cloud Software Group, Inc. All rights reserved.