[reSIProcate] InMemoryRegistrationDatabase

["Matthias Moetje - TERASENS GmbH" <moetje@xxxxxxxxxxxx>]

Hi,

 

I have a question about the following comment regarding

the InMemoryRegistrationDatabase:

 

/**
Trivial implementation of a persistence manager. This class keeps
all registrations in memory, and has no schemes for disk storage
or replication of any kind. It's good for testing, but probably
inappropriate for any commercially deployable products.
*/

So what is the problem with this? Imagine the server is
restarted. All clients will register every like x s (e.g. 70),
so all clients will be re-registered within x s.

OK, for multiple servers working with the same registration
database it makes sense, to persist that to disk, but for
a single server application that goes down we would have
downtime + x s with InMemoryRegistration and downtime
registration persisted to disk. Is this correct or am I missing
something here?

Matthias Moetje