GoMeddo REST API & SDK performance considerations
GoMeddo REST API
API Performance and Best Practices
The GoMeddo APIs are Salesforce Apex REST APIs, identical in behaviour to standard Salesforce APIs. This means they share the same limits, including those related to load and processing times. These limits vary depending on your Salesforce edition (e.g. Enterprise or Unlimited). You can find a detailed breakdown of Salesforce limits here.
In enterprise-scale load testing, the GoMeddo APIs successfully processed 60,000 requests within a short timeframe without errors or performance degradation, demonstrating their ability to handle high-volume workloads.
Impact of Request Type
The type of request directly influences processing time:
Lightweight requests (e.g. adding a person to a class) require minimal processing.
Complex requests (e.g. finding available spaces over a month with filters such as resource type) require more computation, as the system needs to check all possible matches and availability.
To optimize performance in high-demand scenarios, we recommend introducing caching:
Use a middleware layer (e.g. MuleSoft) or a dedicated caching layer in your website or portal.
Cache static data, such as resources, since this information typically changes infrequently. A periodic sync (e.g. daily) is usually sufficient.
For real-time availability, query Salesforce only when a reservation is actually made. This allows you to serve most availability queries from cache, reducing the number of Salesforce calls.
MuleSoft Integration
GoMeddo integrates seamlessly with MuleSoft. Salesforce provides a standard connector that gives you access to all GoMeddo data as well as any Salesforce data. This enables straightforward integrations between GoMeddo and MuleSoft with minimal configuration.
GoMeddo JavaScript SDK
The GoMeddo JavaScript SDK provides a developer-friendly way to access GoMeddo’s REST APIs. It acts as a transparent proxy to Salesforce, without adding extra layers such as processing, caching, or retry mechanisms. As with the REST API itself, usage is subject to Salesforce API limits and performance constraints.
Data Fetching and Performance
The volume of data that can be retrieved through the SDK is determined by Salesforce limits and the applied filtering criteria. Keep in mind:
Complex queries (e.g. calculating availability across many time slots) can be computationally heavy and may result in timeouts.
To improve reliability and response times, apply as much filtering as possible to narrow down results before running calculations.
There are no strict recommendations on the maximum number of time slots to fetch. The optimal approach depends on your criteria and the complexity of your data model, so testing in your specific scenario is essential.