Downtime earlier this morning (4/13/2014)

LimeLM had some downtime earlier this morning. There was a power outage at the datacenter where some of our servers are located, and crucially where our primary load-balancer was located.

We're back up now. We're also working on a solution to have multiple fail-over load balancers so that a power outage doesn't cause so much trouble.

I truly apologize.

- Wyatt O'DayFounder & CEO of wyDay

I know you have APIs so that developers can integrate LimeLM into their dashboards, etc.....but I have one particular use case where I show the license keys associated to a customer grouped by some of the license fields and that is a lookup to LimeLM. I display the license key and the number of used activations and max activations.....when the site went down, a portion of my dashboard went down as well (a big portion).

Have you considered building any callback mechanism where a customer (me) could give you a URL to post data to when it changes (maybe a new license key is generated, # of activations change, etc) , this URL would get called and I could choose to cache the data and use that on my dashboard instead of a live call to LimeLM???

Thanks,Todd

Any caching you do should be done on your side. So, for example, let's say you're using the LimeLM.php files to access our web API. In that file you should use a cache like Memcached to store any results that you don't care if they're absolutely fresh (or if you know they don't change often enough to warrant constant communication with our servers).

So, the pseudo-code for such caching would look something like this:

$data = GetFromMemcached('request-parameters-as-unique-id');


// if the data exists in the cacheif ($data !== null){    return $data;}else // cache-miss{    $data = QueryLimeLM($request, $parameters);    StoreInMemcached($data, 'request-parameters-as-unique-id');    return $data;}

Does that make sense?

Reply
Discard post