Last week we took a look at the types of Openmix applications that are currently in use to inform some development priorities. It turns out that the vast majority of the applications, at 82%, are coded to return the platform with the best response time.
When we drilled into these response time-optimized applications we saw that over half of them, at 64%, perform no adjustments based on cost, time, or geography. However, nearly a third of the applications do some type of adjustment based on these factors.
It is great to see a clear pattern of Openmix application types emerging.
Term Definitions – Openmix Application Types
Availability – Choose a platform based on availability. In some cases a primary platform is used unless it is not available.
Best Response Time – Optimize for response time, sometimes taking other factors into consideration.
Complex – Complex logic based on multiple criteria.
Geographic – Direct traffic based on user’s location.
Static – Route to the same platform always.
Weighted Round Robin – Direct traffic across a set of platforms in some proportion per platform.
Term Definitions – Response Time Sub-types
Cost-weighted – Adjust the response time by some amount proportional to platform cost.
Cost-handicapped – Handicap the response time based on cost. (Handicapping is adding some fixed amount to values whereas weighting is multiplying by some factor.)
Geo-adjusted – Adjust the response time by geography.
Standard – No adjustment for cost, geography, or time.
Static – Coded to optimize response time but only returning a single platform since only one platform is available.
Time-adjusted – Alter the platforms to return based on the time of day.