1. -5

  2. 8

    This is total spam. It says nothing of technical value and just pushes the reader to use a “serverless database”. Whatever that is? The post, literally, says “there is no downside”.

    1. -2

      Yes there are risks inherent in new technology and new startups, but from a technical standpoint, I’d argue that Fauna sidesteps most/all of the downsides of the existing solutions people move to when their Postgres / MySQL thing gets exhausting to manage. Strong consistency, elastic scalability, no provisioning trap, hierarchical multi-tenancy, event feeds, etc.

      1. 3

        Oh c'mon, if it’s technology there are trade-offs and downsides. You’re just being dishonest and I don’t think lobste.rs will fall for it.

        1. 2

          Doesn’t look like there’s foreign keys. That alone kinda makes it DoA as a SQL-replacement.

      2. 3

        An unexpected traffic surge is the worst time to mess with your database infrastructure. This is the cloud database trap.

        I think integrating a proprietary db from a startup is a much bigger risk than this. I can almost eliminate this risk with scalability testing and overprovisioning (beefy db servers are still cheap compared to devs). I’m not even sure where to start calculating the risk of a db startup - what’s the cost of having probably 1-3 months of notice to rewrite every line of code that touches the database (assuming its architectural decisions didn’t seep into my app design and of course they did)?

        1. -3

          It’s a balance of trade-offs. Our customers are comfortable with closed source, because they like to see us with a reliable revenue stream. Our ability to run in multi-cloud and on-premises, with reasonably priced per-core licensing, means your cost model isn’t tied to your cloud provider.

          The team has been together for years, and the pace and product we are building feels sustainable, not flashy.

        2. [Comment removed by author]

          1. -1

            Serverless means your unit of deployment / compute / cost is not analogous to a machine. So when it’s not running it’s almost free, and you don’t have to worry about load spikes in advance.

            1. [Comment removed by author]

              1. 2

                I didn’t pick the term. I wish it meant “app that runs on phones and browsers but needs no coordinating component” but we don’t always get what we want. :)

                If you aren’t familiar there is a whole industry that is gathered under this banner, see for example http://serverlessconf.io

                1. 1

                  You’re using it though.

                  The recent white supremacist/racist movement in the USA calls itself “the alt-right” but that doesn’t mean the rest of us don’t know what they really are.

                  Similarly, stop using a ridiculous marketing buzzword. If you need something catchy, call it Functions As A Service (FAAS).