DivineTraube

15 ms·

91.
Real-Time Stream Processors: A Survey and Decision Guidance(medium.baqend.com)
10 points by DivineTraube 10y ago|0 comments
92.
by DivineTraube 10y ago
We have not seen any serious DDoS attacks, apart from the ones we created through our own heavy load testing. UDP attacks are not really a problem, since the servers are only accessible by Fastly over TCP using a combination of SSL authenti
93.
by DivineTraube 10y ago
It's pronounced "Backend" ;-) And since we are in the Backend-as-a-Service market, the name is not all that unfitting. Although it cannot be denied that from time to time some people think we are French an spelled "Baque
94.
by DivineTraube 10y ago
We (Baqend) use an approach that is somewhat different from what has been proposed here so far: - Every one of our servers rate limits critical resources, i.e. the ones that cannot be cached. The servers autoscale when neccessary. - As rate
95.
by DivineTraube 10y ago
Felix, author of the article and founder of Baqend [1] here. I'm happy to answer any questions. If you have suggestions for the next version of the article, we're eager to hear them. [1] http://www.baqend.com
96.
by DivineTraube 10y ago
I'm also very curious about CouchDB 2.0 and whether CouchDB will be able to make a comeback. When I talked to Adam Kocoloski about a year ago, I got the impression that it takes a very good technical approach (consistent hashing, causa
97.
by DivineTraube 10y ago
I was oversimplifying of course, Redis Cluster definitely deserves a place in the comparison. We are actually very satisfied with using Redis in production but had to work around the PubSub limitations using keyspace notifications, which is
98.
by DivineTraube 10y ago
I agree, Redis Cluster has been available for a while. From a practical perspective we did not deem it production-ready yet, due to various shortcomings, e.g.: -Redis Cluter being neither AP nor CP with rather unsatisfying justifications [1
99.
by DivineTraube 10y ago
We tried our best to incorporate these results in the cases where they reflect fundamental shortcomings not bugs (of which Aphyr found quite a few). But you are right, we could include a list of popular examples, where description and exper
100.
NoSQL Databases: A Survey and Decision Guidance(medium.com)
297 points by DivineTraube 10y ago|73 comments
101.
Angular2 by Example(medium.com)
6 points by DivineTraube 10y ago|0 comments
102.
Announcing availability of Baqend's unique client caching technology(blog.baqend.com)
5 points by DivineTraube 10y ago|0 comments
103.
by DivineTraube 10y ago
The central message of the tutorial - the NoSQL decision tree - is available as a PDF cheat sheet too: http://www.baqend.com/files/nosqltree.pdf There also is a paper on the NoSQL classification scheme used in the slid
104.
NoSQL Data Stores in Research and Practice [slides](de.slideshare.net)
50 points by DivineTraube 10y ago|3 comments
105.
Tutorial: Deploying Apache Storm on Docker Swarm(blog.baqend.com)
4 points by DivineTraube 10y ago|0 comments
106.
by DivineTraube 11y ago
CEO from Baqend here. This announcement will have a huge impact for the mobile dev community that relies on Backend-as-a-Service systems. I personally think that Facebook had several reasons to shut down Parse: 1) The technology stack was r
107.
by DivineTraube 11y ago
This is the transaction protocol from Google Percolator - with slightly different wording. I don't know if that's a well known fact but I was surprised they did not even mention it. OSDI Paper on Percolator: https://www
108.
by DivineTraube 11y ago
If you have any other crash snippets, I'll be happy to include them.
109.
Ask HN: Why Is It Still So Simple to Crash a Browser?(codepen.io)
10 points by DivineTraube 11y ago|2 comments
110.
by DivineTraube 11y ago
While this looks promising, why not make Disque part of Redis by introducing the "message queue" data structure? This would allow to build more powerful, application-specific messaging abstractions, for instance a compare-and-swap