server offline error

  • I like the idea and the company seems legitimately concerned about protecting privacy (yes I read the entire EULA). Their servers wouldn’t respond when trying to link my site with their app, however, so the process failed.

    That’s a critical element you need to be aware of when using a setup like this: you are inviting increased complexity and dependencies. The client device, the cell or wifi coverage for the device, the LaunchKey servers, etc. If a customer chooses to use this approach on my website and runs into problems (even due to their own making), it reflects poorly on my company. The complexity may be beyond the average user out there.

    For in-house or personal use it may be fine, but I would be cautious about using it for the public. I would certainly keep it only as a voluntary option.

    • This topic was modified 7 years, 9 months ago by joefoe.
Viewing 1 replies (of 1 total)
  • Plugin Author aenglander

    (@aenglander)

    I apologize for your comment falling through the cracks. It is our policy to respond to user input as quickly as possible.

    With regards to availability, this issue has been priority one since LaunchKey was acquired by iovation last November. As such, we have spend the last four months designing and engineering what will be as close to a zero down time system as possible. We released the first iteration of that process on February 13th of this year. With this release, we migrated the core LaunchKey systems to iovation data centers with an active/active failover between centers. We also released a new version of the LaunchKey API, v3, to the public. This API currently supports our White Label product which is used by our largest customers. The remainder of the services and products will be migrated to the v3 API over the coming months. If you have used LaunchKey since the migration on February 13th, you may have noticed that it is considerably faster and more reliable. Due to infrastructure and networking changes, average response times have dropped to sub 100ms, push notifications are near instantaneous, and we have not had an outage since the transition.

    An additional benefit to moving to the iovation infrastructure will be that we can now begin to integrate between products within iovation’s suite to provided device and contextual based information that will allow us to provide risk based factor step-up in the near future.

    As always, we appreciate your comments. There is no greater resource than user feedback. Please feel free to reply if you have further questions or comments.

Viewing 1 replies (of 1 total)
  • The topic ‘server offline error’ is closed to new replies.