HN user

searchfaster

119 karma

https://searchera.io

deepak(at)searchera.io

Posts0
Comments66
View on HN
No posts found.

Ours is a custom index written mostly in 'C' and bit of x86 assembly. It is very lightweight and extremely fast even without the use of replica indexes for every sort order.

Thanks for signing up.. Will get you started as soon as we have our additional servers up.

Yes, we are currently hosted only in NY. Can you please ping beta.searchera.net and check the latency from your location ?

Once we are out of beta we will be offering distributed datacenters. West coast USA and Europe to start with. The option to install in your own servers / cloud provider is another option.

If you would like to try it out, I can always bring up a host quickly next to your location on digitalocean or aws. Please send me an email on hello@searchera.io

Thanks ! Actually 40% of our current beta users are existing Algolia customers. Maintaining separate indexes for every sorting / ranking option and intentionally restricting the application to stay under limit is a drawback that many complain about.

Our On-Premises option is something which a few potential customers have been interested in.

Yes.. this is something our startup is working on fixing. How you sort and how you prioritize your fields to be searched are all configurable at query time.

If you pay for a million records, you should be able to store a million records.

https://searchera.io

We are currently in beta and our website is not fully up but the demos give an idea of what is possible.

I did a test of 'Bare metal Linux' vs 'Containers on bare metal linux' for our product. In this case it is just 2 processes a 'search component' and an 'analytics and logging component'. Under heavy load the 'search' uses a lot of disk reads, CPU and network, while the logging module uses a lot of disk writes.

The comparison was done on

1) Ubuntu server 16.04 with both processes running as they usually do (Search with higher priority)

2) Core OS - Both processes running each in a separate rkt container (search with higher priority).

I saw no change in CPU / Network / Disk access metrics and my throughput remained the same.

Please note though, in my case I do not have way too many microservices as the general usage is. Also I use host networking. I also had no need for orchestration services like Kubernetes / swarm etc.,

TLDR:; No change between running product in container vs no-container mode with host networking, minimal containers and no orchestration.

As a developer who just spent the last night building a visualization tool analyzing reddit data, totally appreciate the value of a good designer.

It is very hard to balance 'simplicity', 'usability' and 'features'.

I had to cut short many features and options because the interface was getting too complex.

Yes.. Its left to the API provider.

Try https://learngraphql.com gives a very good idea of what graphql is. Way better than reading the official documentation or spec.

Once I went through it, made up my mind that our API as a service product should support Graphql.

Note: I am in no way related to the site.. It is free and I finally actually understood what graphql is in 15 mins.

Why Use Postgres? 9 years ago

Hyperloglog is a pretty straightforward, simple and awesome algorithm.. probably that is the reason.. Take a look at redis implementation.. it is very easily readable.

Thanks.. just tried it out with my service, beats nginx for simple http proxying pretty easily by a nice margin. Envoy supports way more features than nginx too !

Nicely put... wish I had tried Emacs sometime. I can relate to what you are saying as I use Vim commands/shortuts everywhere from my Window manager, browser to custom key mapping of lkjh for arrow keys on my ergodox keyboards..