People who want a good search engine (for instant search etc.) today either need to go for a cloud hosted proprietary offering or have to learn to set-up Elasticsearch and spend a lot of time tweaking it to support typo tolerance. Trying to change that status quo.
1. Sorting order is dynamic, unlike Algolia where you are forced to define a sort order during index creation and you are forced to duplicate your entire index when you want another sort order, e.g. sort by timestamp vs sort by ratings.
2. Run fast on commodity hardware (e.g. a decent EC2 instance) instead of requiring special dedicated hardware that costs a bomb. This is achieved by using highly optimized in-memory data structures instead of relying on fast SSDs and memory mapped I/O approach that Algolia has taken.
3. Disprove the notion that one cannot host their search themselves and need to rely on a cloud service provider. We want to make it really easy to run Typesense and manage it. We have some things to do on this front, but this is definitely the goal.
There is so much more to say about it. So if you are interested you could visit our website here: https://zenkit.com
The goal of our startup is to solve all of the pain points where the framework stops and make the best version of operationalizing Airflow on Kubernetes; and authoring, deploying, and running DAGs in a distributed execution environment in production at scale.
It's pretty interesting to learn and see how features like orchestration and dynamic provisioning on a platform actually work all the way down.
I'm working on the search side of things, integrating the rest of the platform with the text search service we're using. Some (or a lot!) of it is busywork, but sometimes things get interesting. Mostly when you're out of options with what functionality is offered out of the box and you have to essentially look under the hood at the internals and write your own custom thing to serve whatever weird requirement client X came up with.
Apologies for the vagueness!
Literally no one doubts this. Dont know why you had to put it so condescendingly.
Its a peer to peer mobile app for mens to share clothes. Feedbacks welcome. (think of it like Airbnb for Men's fashion)
It’s been a fun few months and I am super pleased to have chose Rust for this task.
"that was part of the peculiarity +12 of the game."
see how I've put a random :) value next to a word? Wouldn't be cool if that is assigned by the "game"?
Well from that evolved, what if I write a "system" that can do that anywhere and in any app you use? And then it hit me, that is a mobile keyboard! So, it is an experiment at this point, I'm building it.
