119 karma · joined November 4, 2015
deepak(at)searchera.io
Finally, it is the customers call. They are going to choose what works best for them :)
Thanks for signing up.. Will get you started as soon as we have our additional servers up.
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
Our On-Premises option is something which a few potential customers have been interested in.
If you pay for a million records, you should be able to store a million records.
We are currently in beta and our website is not fully up but the demos give an idea of what is possible.
Here it is.. https://github.com/yahoo/mdbm
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.
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.
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.
Manigandham's post below confirms it though with all the necessary information.
I was wondering if this will be any helpful for a product I am working on, but as I use mmap for reading our data, don't really see a benefit after the initial read.