Recently I was looking into options to add rate limiting to a specific endpoint
in an application at work. Most endpoints are only exposed internally, and we
are careful to not make more requests than the system can handle. However, in one
case, the endpoint is open to our customers, and it runs some pretty intensive
database operations, so we wanted to limit the rate at which clients can make
requests. This functionality is available in pretty much every API gateway out
there as well as in a lot of reverse proxies.
In our case, application updates are easier to make than config updates, so we
opted for a simple solution that we could deploy as part of our Node.js app.
For years, my dream project has been to build a database from scratch. For
most of my career, the most challenging questions have revolved around how to
ingest, store, and query data in a performant way, and while I have found a
number of really great solutions, there usually has not been a single product
that can meet all of the requirements.
For the past few days, I have been playing around with Elixir to build
an API gateway for WP-Pulsar. While I am far from an Elixir expert (I’d
barely even consider myself and Elixir novice yet), I have really started
to fall in love with the language!
This tutorial has moved to the book site for Learn ClojureScript:
and utterly terrifying. There are so many options for every aspect of
development and tooling that
choices can be paralyzing. The
glut of options for, well, everything has caused me to focus more on deciding
which technologies I really want to learn and for which ones I can be content in