Show HN: Key/Value Store as-a-Service

  [~] : openssl s_client -connect 54.243.85.55:443                                                             
  CONNECTED(00000003)
  140150585800568:error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error:s23_clnt.c:769:
  ---
  no peer certificate available
  ---
  No client certificate CA names sent
  ---
  SSL handshake has read 7 bytes and written 201 bytes
  ---
  New, (NONE), Cipher is (NONE)
  Secure Renegotiation IS NOT supported
  Compression: NONE
  Expansion: NONE
  No ALPN negotiated
  SSL-Session:
      Protocol  : TLSv1.2
      Cipher    : 0000
      Session-ID:
      Session-ID-ctx:
      Master-Key:
      Key-Arg   : None
      Krb5 Principal: None
      PSK identity: None
      PSK identity hint: None
      Start Time: 1486834426
      Timeout   : 300 (sec)
      Verify return code: 0 (ok)

Re: Show HN: Key/Value Store as-a-Service

#8

Post by ap46 » Sat, Feb 11, 2017, 5:34 PM UTC

>Do you need high available, flexible and dynamic key/value store for coordination, notification, feature flagging and more?

Doesn't exactly evoke confidence. Are they being explicit that the free tier won't have availability. Is there an SLA or even an estimate?

Re: Show HN: Key/Value Store as-a-Service

#9

Post by elastic_church » Sat, Feb 11, 2017, 5:41 PM UTC

Any advantage over firebase?

Re: Show HN: Key/Value Store as-a-Service

#10

Post by jeremyjh » Sat, Feb 11, 2017, 6:06 PM UTC

koolba wrote: post #3

Add SSL. With LetsEncrypt, it's table stakes.

If they don't know this much, what else don't they know? Not to mention they don't disclose anything about the team or company other than it is "Made with Love in Istanbul". No reason not to assume its a kid who has never hosted a production service in their life.