Last Tuesday our warehouse robot forgot what a red box looked like.
Not metaphorically. It had the force curve, the timestamp, the GPS pose — everything except the one thing that mattered: the visual embedding that let it recognize the same box three minutes later. The data was there. It just couldn't be queried the way the task needed.
That's the bug class moteDB exists to kill. And 0.5.1, released this week, is the version where I finally feel like we got the architecture right.
If you've been following since the v0.1 / v0.2 days, this release is the one where a lot of the awkward scaffolding comes down. Here's what actually changed — and what I'd tell past-me if I could.
The short version
motedb 0.5.1 is on . The test suite now runs 1,200+ cases under concurrency in about 4 minutes with zero hangs.
If you're building anything that needs to remember in the physical world — robots, drones, edge agents — I'd genuinely like to hear what your memory layer looks like today. What's the one query you wish your stack could answer that it can't?
SOCIAL SHARE CARD GENERATOR