Autocomplete demo broken about redis-io

[blainsmith]

Any chance this demo could make a comeback?

[djanowski]

@badboy Should we link to your http://redis-complete.herokuapp.com/?

[badboy]

Sure, it's running on free heroku, so it hasn't the most resources, but it should be fine.

[djanowski]

Two concerns:

1. It's on free Heroku, so if it gets traffic, they may force you to pay (or put the app into "recharge" mode).
2. The example with ~1500 items is less compelling than the one with 8MM items. On the other hand, 8MM lines of Linux kernel source code is not very interesting for an autocomplete; you have to know what to look for in advance.

If we got a bigger Redis instance for this example, would you adapt it so that it uses a bigger data set, but something known by everyone? Maybe a list of cities or something like that. Also it would be cool to show in the demo how much memory Redis is consuming for that data set. What do you think?

[badboy]

Fine with me. Maybe @itamarhaber can set me up with a bigger instance. Hosting the application on my server would be fine, just not Redis itself. :)

[itamarhaber]

Sure thing - 100MB or bigger?

Since I can't manipulate Heroku's billing (yet 😈), you'll need to use a Redis Cloud direct account instead of the add-on. Sign up, create a free instance and lmk the account id.

[djanowski]

Where is Redis Labs Cloud hosted? It would be great not to have a big latency between the app and Redis.

[itamarhaber]

@djanowski all over AWS and the rest of the public IaaSs, but if the app's running on Heroku US then AWS us-east-1 is the region (choose-able when creating the database).

[badboy]

Well, I could run the application on my own server, so EU based would be great.
Will do the signup tomorrow or friday.

[itamarhaber]

@badboy that's there too 🌎 + 🌍 + 🌏

[djanowski]

Anybody want to make progress on this, or should we unlink the example?

[itamarhaber]

The offer for free storage still stands and I can probably secure sponsorship for the compute resources if needed.

[PowerKiKi]

By now, I believe the link should be removed from the documentation page. If it was not solved in the past 3 years, I don't think it would be anytime soon. And as is, it doesn't have much value. Better spend 5 minutes removing the link, and closing this issue.