Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
erikwitt
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
erikwitt
10y ago
That is absolutely right. You can easily write queries that can never be executed efficiently even with great indexing. Especially in MongoDB if you think about what people can do with the $where operator. What would in retrospect be your
2.
▲
by
erikwitt
10y ago
I agree, the parse shutdown was organized extremely well. The open source parse server, one year of migration time and a ton of new vendors that now offer to host your parse app, all made it much easier to handle the shutdown. It's als
3.
▲
by
erikwitt
10y ago
Although MongoDB has its limits regarding consistency, there are things that we do differently from parse to ensure consistency: - The first thing is that we do not read from slaves. Replicas are only used for fault tolerance as it's t
4.
▲
by
erikwitt
10y ago
That's actually exactly what parse did. They used a slow query log to automatically create up to 5 indexes per collection. Unfortunately this did not work that well especially for larger apps. I guess 5 indexes might be a little short
5.
▲
by
erikwitt
10y ago
You're right, NoSQL systems tend to be more complex and especially failure scenarios are hard to comprehend. In most cases, however, this is due to being a distributed datastore where tradeoffs, administration and failure scenarios are
6.
▲
by
erikwitt
10y ago
That is definitely unintended behavior. We'll fix it! Fortunately, only www.baqend.com has this bug, it's not in our framework.
7.
▲
by
erikwitt
10y ago
Considering scalability from the start does not just mean optimizing for millions of concurrent users, but choosing your software stack or your platform with scalability in mind. I get that it's important to take the next step and that
8.
▲
by
erikwitt
10y ago
On the other hand, there are things where "fix it later" just won't work. Especially when it comes to scalability, which has to be considered right from the start to get it right.
9.
▲
by
erikwitt
10y ago
You have a point there. I found jMeter, however, really easy to use. I could simply let it monitor my browser (via a proxy) while i clicked through the website and the checkout process to record the requests of an average user. Then I confi