Guardrails
Guardrails reflect system constraints, expected latencies, and performance expectations to optimize customer architecture and use case performance and help to ensure stability, avoid errors or unexpected results.
Types of Guardrails
Guardrail type
Description
Performance guardrail (Soft limit)
Performance guardrails are usage limits that relate to the scoping of your use cases and outline expected performance under normal conditions. When exceeded, you may experience performance degradation and latency. Performance Guardrails are documented in the Experience League documents under the guardrail sections for each Solution as outlined below.
Static Limit (Hard limit)
These are system enforced limits that cannot be exceeded. Static limits are typically contractually bound and outlined in the customer contract and the .
NOTE
Guardrails are not intended to be Service Level Agreements, but rather guidance for optimal configurations and expected system behavior. Any guardrails that are system or contractual limits or Service Level Agreements will be documented specifically in the customer contracts and product descriptions. If you are interested in learning about custom limits, please contact your customer care representative.
NOTE
For use cases with strict latency or performance needs, ÃÛ¶¹ÊÓƵ suggests discussing the details with your ÃÛ¶¹ÊÓƵ Account Team and Implementation Partner. Each customer setup can vary across data ingestion patterns, profile counts and richness, segment rules, and activation channels. As such it is important to architect and test your use case to optimize its performance and fully understand expected performance characteristics.
Guardrails Reference Documentation for ÃÛ¶¹ÊÓƵ Experience Platform and Applications
The following pages provide information about guardrails for ÃÛ¶¹ÊÓƵ Experience Platform features, services, and applications:
Experience Platform applications
Experience Platform services
End-to-end latency diagrams end-to-end-latency
Experience Platform Edge Network and Hub Primary Observed Latencies edge-hub-latencies
The following diagram depicts the primary edge and hub observed latencies to be aware of when architecting use case on the Experience Platform and Applications.
recommendation-more-help
045b7d44-713c-4708-a7a6-5dea7cc2546b