A persistent key-value server in 40 lines and a sad fact (2014)

Re:A persistent key-value server in 40 lines and a sad fact ... by javaispoo on Monday June 22, 2015 @04:21AM (#9756895)

Yeah, and memory is infinite, and all disks are free, and the computing fairies make all the processors super fast. But back in the real world, startup time is a valid concern.

[ Parent | on HN ]

Re:A persistent key-value server in 40 lines and a sad fact ... by sarnowski on Monday June 22, 2015 @04:27AM (#9756918)

Don't know your "real" world. In my real world, the AWS instance takes several minutes to come up - I can spare some milliseconds on thr JVM startup.

[ Parent | on HN ]

Re:A persistent key-value server in 40 lines and a sad fact ... by vidarh on Monday June 22, 2015 @06:48AM (#9757404)

In my real world the containers we spin up come up in seconds, but container restart is far more rare than restarting services.

[ Parent | on HN ]

Re:A persistent key-value server in 40 lines and a sad fact ... by thescrewdriver on Monday June 22, 2015 @10:17AM (#9758451)

If the time to restart your process or host affects the overall operation and performance of your service you're doing it wrong.

[ Parent | on HN ]

Re:A persistent key-value server in 40 lines and a sad fact ... by vidarh on Tuesday June 23, 2015 @07:02AM (#9763821)

If your services consistently restart quickly, it gives you the freedom to design things differently.

E.g. doing a rolling update across a large number of instances by restarting a service at a time can become a quick enough process to be viable in instances where you'd otherwise need lots of excess capacity to be able to cycle larger proportions of instances at the same time. Making full rolling updates "cheaper" both in time and resources also translates to making rapid updates a safer choice (e.g. if I can roll back a broken release in 5 minutes, it's far safer to push out a new release than if a rollback takes hours).

[ Parent | on HN ]

Re:A persistent key-value server in 40 lines and a sad fact ... by astrange on Monday June 22, 2015 @07:50PM (#9761884)

That just means you expect restarting to be slow and have excluded it from your system design.

There is no problem with restarting nginx to update its config once a second, and it's even encouraged that you do so. Besides, crash-only software recovery is really the only morally sound development technique.

[ Parent | on HN ]

Re:A persistent key-value server in 40 lines and a sad fact ... by Twirrim on Monday June 22, 2015 @10:40AM (#9758616)

What are you doing that you frequently starts / shuts down an application to the order where 70ms is a problem?

[ Parent | on HN ]

Re:A persistent key-value server in 40 lines and a sad fact ... by eterm on Monday June 22, 2015 @11:44AM (#9759103)

Not just frequently starting/stopping applications but a persistence engine at that.

[ Parent | on HN ]

Re:A persistent key-value server in 40 lines and a sad fact ... by astrodust on Monday June 22, 2015 @12:28PM (#9759407)

How many reboots per second are you having to endure? Maybe you should make your server process crash less often.

[ Parent | on HN ]