However, "In conventional RethinkDB deployments, users typically run their application server within the same closed network as their database servers. In that specific kind of environment, where the database isn’t exposed to the public internet, there’s typically little need for encryption."
I would push for more companies to actually encourage encryption locally too. Perimeter security is no longer sufficient.
That's delivery. User accounts, network encryption and Windows support.
I did a couple of interviews with this people; and I can ensure this features have a few thoughts behind them.
Happy to see RethinkDB going on, and very sad I didn't make 100% my best at the interviews by personal issues at the time.
It's a pity that many people here in my country do not know still about RethinkDB. Other mainstream databases are more common knowledge.
I wish the best for you, and I keep a very good impression of each and every one of the people with whom I could talk at the process.
Very curious about the windows port. Has been hard? do you use any kind of framework that did ease the porting of the RethinkDB code?
Network encryption is undervalued in this times. A funny and serious feature. I would like to see the dashboards, thoughts and meetings around this one.
I've heard about RethinkDB for the first time in 2013[1] and at the time it was described as "MongoDB with joins and auto-sharding".
I also heard that one of the initial "killer-features" of RethinkDB was supposed to be a stored history, just like a big persistent data structure (in my understanding, similar to Datomic). In the video[2] a lot of time was spent describing the benefits of an append-only structure.
I don't think it was ever supposed to be a history-saving data structure -- that log-structured stuff is (I haven't watched the video, I'm assuming) about talking nice to SSD's. It was at one point, after that video, a single-machine memcache-compatible persistent key/value store, before the pivot to being clustered and having its own query API.
What exactly what their previous goal? I thought they've always been for real-time search, at least that was the moniker when I looked at it 1 year previous.
You need to pass the ssl certification to `connect` for the driver to successfully connect to an encrypted port. Check out the docs here: http://rethinkdb.com/api/python/connect/
Hey hey, I work on the community team at Rethink and I'm happy to send you a mini version which is a little stress doll Thinker.. The plushies were an Etsy order and we only have a few left. I think we'll do more down the line :) christina [at] rethinkdb [dot] com. Also, thank you for the kind words!
Currently migrating from a users-as-a-service startup to rethinkdb. So far query language has been intuitive (need to query via the length of a nested array? Got it) and rethink community on StackOverflow etc has been solid. Another thumbs up.
> Network encryption: built-in TLS support encrypts database connections
> RethinkDB 2.3 includes TLS support, contributed by Josh Hawn. Josh integrated OpenSSL, enabling encryption on the wire for both the client driver protocol and communication between database servers in a cluster. This update also brings encryption to RethinkDB’s web-based administrative user interface, which you can now access with an HTTPS URL.
Yay! WAN Replication over TLS is built in now.
I'm not sure how I feel about the web interface, might be better to stick with SSH tunneling for that.
Asher , yes . this is our prototype : http://phwa.be , a real time multimedia chatroom , with full markdown support but with radically different approach. It uses eventsource + rethinkdb change feeds and now i am looking at fold command. We are also building a realtime mobile marketplace which is going to be our main startup product.
Not yet :( Document-level TTL is a surprisingly challenging feature to implement correctly in a distributed system. We'll try to get it in as soon as we can; sorry we haven't been able to do this sooner.
AGPL is used by a number of DBs such as MongoDB and Neo4j. I'm sure there are others, but these two are top of mind.
RethinkDB's drivers are Apache or MIT (I can't remember which).
Licensing the server as GPL/AGPL while making drivers Apache/MIT is an accepted practice in the database world as it provides the DB vendor with opportunities to protect revenue while the driver licenses protect developers from the GPL/AGPL.
In spite of drivers being non AGPL, companies with 'absolutely no AGPL' policy cannot try the open source version of these DBs which puts these products behind others. I don't think AGPL provides any real benefit for the vendor. Most small organizations will want their patches (if any) to be upstreamed so they don't have the maintenance burden. Most big organizations will want commercial support anyway. All AGPL does is discourage adoption.
There are plenty of non-AGPL DBs out there doing pretty well. Here are some examples of GPL/MIT/BSD style licensed DBs: Riak, Cassandra, Redis, MySQL, PostgreSQL, ArangoDB, CouchDB.
However, "In conventional RethinkDB deployments, users typically run their application server within the same closed network as their database servers. In that specific kind of environment, where the database isn’t exposed to the public internet, there’s typically little need for encryption."
I would push for more companies to actually encourage encryption locally too. Perimeter security is no longer sufficient.
EDIT: Adding Google BeyondCorp reference: http://www.theregister.co.uk/2016/04/06/googles_beyondcorp_s...