Imported Google Group message.
Date:Tuesday, 1 September 2015 22:15:51 UTC+1.
1.8 has quite a few features to help you manage failover:
- Use the circuit breaker to detect failures and take a service offline until fixed (can kick off a web hook that reconfigures your Tyk config if you need to - maybe push a. Backup API definition into the cluster?)
- Use the circuit breaker in conjunction with the service discovery module to dynamically set a failover when the breaker trips (integrates nicely with etcd, eureka or consul)
- You can further minimise the failure rate if you have multiple upstream targets by using the round-robin load balancing feature
- Use enforced timeouts, these also integrate with the SD feature
These are described best in the plugins section of the dashboard:
And raw Tyk config here in the API management section:
There’s also enforced timeouts, which can be handy if you don’t want something as complex as a CB.
Ultimately Tyk can handle pretty complex failover scenarios, how you handle the failover with Tyk is up to you, but there’s plenty of ways to handle it and we have some patterns in place to make it easier…
Hope that answers things
From: S. Alexander Zaman [email protected]
Sent: Tuesday, September 1, 2015 22:02
Subject: failover target url
To: Tyk Community Support [email protected]
Cc: [email protected]
You received this message because you are subscribed to the Google Groups “Tyk Community Support” group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web, visit https://groups.google.com/d/msgid/tyk-community-support/629f4aee-0ab1-4237-bc65-7ca9b524674d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.