A clubhouse events search engine

#elasticsearch #javascript #clubhouse #amazon

These last few days I decided to get back to coding (a bit) and eventually ended up with a #clubhouse search engine for events.

Here are the steps I followed.

First, I needed to access the "undocumented" and non public clubhouse API.
I give it a try with this repo:
https://github.com/stypr/clubhouse-py

Although written in python, I ported the few pieces (auth and access to event list) in typescript with axios.

I coded a daemon in nodeJS to fetch the events on a regular basis (with a throttle limit in order to not get banned from calling the API).
I then installed elasticsearch (actually hosted on elastic cloud) with Elastic builder (to be able to craft nice query) https://elastic-builder.js.org/.
This allow me to stored events on the cloud on elastic.

Deployment concerns, I had a lot of choices, I decided to give amazon elastic beanstalk a try (nothing to do with elastic search though). This is super easy to set up and deploy. (more information here: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_nodejs.html)

And then, this is it. A simple express/node server deployed on Amazon Elastic beanstalk + elastic search.

Took me 3 full days (cause I'm a bit rusty).

Https://clubhouse.flint.sh

Hands-on debugging session: instrument, monitor, and fix

Join Lazar for a hands-on session where you’ll build it, break it, debug it, and fix it. You’ll set up Sentry, track errors, use Session Replay and Tracing, and leverage some good ol’ AI to find and fix issues fast.

RSVP here →