Inspired by community enthusiasm we initially attempted a MongoDB implementation. Further investigation showed that Mongo was not suitable for a single-server installation, the basic case for Wave in a Box. Mongo doesn't offer suitable durability guarantees.
We decided to make a pure filesystem implementation because it's conceptually very simple (append-only) and demonstrates exactly what is required from a wave store. There's few abstraction layers to get in the way. Note that this is only for the simple wave/account/certificate stores; more complex structures like the upcoming index make less sense to implement directly on disk. On 21 December 2010 23:04, Yuri Z. (a.k.a Vega) <[email protected]> wrote: > By the way, why the current persistence approach is File system based > and not say DB based? Is it easier? I am just curious. > > On Dec 21, 5:00 am, Alex North <[email protected]> wrote: > > Well, we've been saying "any day now" for many weeks, so I can't honestly > > predict it. > > > > Also, even when persistence is implemented, it will probably come with a > big > > red warning sticker that the on-disk representation is not stable and > will > > probably change a couple of times until we're confident it's something we > > can retain backwards compatibility with. > > > > Alex > > > > On 21 December 2010 12:34, bluecobalt <[email protected]> wrote: > > > > > > > > > > > > > > > > > How soon is "soon"? Wave is unusable for us until we can safely store > > > waves. > > > > > On Dec 20, 4:45 pm, Alex North <[email protected]> wrote: > > > > Not yet, but soon! > > > > > > On 21 December 2010 03:32, BuggyB <[email protected]> wrote: > > > > > > > Hi... > > > > > Is it possible by this time to store/save the waves in a database > > > > > system or anywhere? > > > > > > > When I restart my server, the waves will go away ... > > > > > > > -- > > > > > You received this message because you are subscribed to the Google > > > Groups > > > > > "Wave Protocol" group. > > > > > To post to this group, send email to > [email protected]. > > > > > To unsubscribe from this group, send email to > > > > > [email protected]<wave-protocol%[email protected]> > <wave-protocol%2bunsubscr...@goog legroups.com> > > > <wave-protocol%[email protected]<wave-protocol%[email protected]><wave-protocol%252Bunsubscribe > @googlegroups.com> > > > > > > > . > > > > > For more options, visit this group at > > > > >http://groups.google.com/group/wave-protocol?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Wave Protocol" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
