github questdb/questdb 2.1.0
2.1.0 (THOR)

latest releases: 7.4.0, 7.3.10, 7.3.8...
9 years ago

New features

SSL encryption.

Replication can be done over secure channel using industry-standard SSL encryption protocol. Configuring SSL is notoriously complicated, so I tried my best to make it as simple as possible for both JournalServer and JournalClient. I shall let you be the judge though. More...

SSL authentication.

Client Certificate came almost for free after implementing SSL. I did try to make it simple for you though. More...

Shared secret authentication.

It is now possible for client and server to exchange shared secret for authentication and authorization purposes. Shared Secret can be anything you want it to be, there is no limit on amount of data you can send. More...

Kerberos authentication.

Usually Kerberos is a pain, not with NFSdb, not anymore. Kerberos implementation uses Shared Secret exchange mechanism and in addition it handles generation and validation of service tokens, Your application deals with usernames. It is that cool! More...

Kerberos integrated Windows authentication.

If you have JournalClient running on Windows platform you can generate service token for currently logged in user with minimum fuss. User is not prompted for password! More...

JournalClient auto-reconnect

JournalClient can automatically recover after server restarts. If you have multiple clients replicating single server you can restart server without needing to restart clients afterwards. Whats cooler still is that when you shutdown server clients can failover automatically. JournalClient will also maintain transactional consistency during server outages.

Compatibility warning

Replication protocol is incompatible with previous release of NFSdb. I had to change the protocol to accomodate shared secret exchange.

Don't miss a new questdb release

NewReleases is sending notifications on new releases.