3 ms·

So are you just providing an API and the database will be stored on your server? Or will users install it on their own hardware?

• david927 11y ago
  Initially we're providing an API but the idea of open sourcing it is very much on the table, which of course would allow users to install it on their own hardware.
  • vr3690 11y ago
    Correct me if I am wrong, but won't latency be an issue if connecting to a DB via an API? I would imagine that would be a deal breaker for most (especially for me).
    • david927 11y ago
      Great question! This is where other DaaS's have struggled and this is where we shine. The authorization model is robust enough that you can obviate a lot of the business-logic layer. Building a sports site and only friends of team members or the team members themselves can message each other? Build it in your authorization model. The UI will only see appropriate recipients and only be able to send messages to them. In other words, a lot of your architecture could become UI-DB direct and only a portion going through a business layer.