Project Info

• Product: BrickStor
• Concept: Non-persistent operating systems
• Date: January 12, 2015

Eric Bednash and Sam Zaydel discuss one of the important features of BrickStor, our non-persistent operating system.

What are non-persistent operating systems?

No matter what happens when the system is on after it goes off and comes back on again, it’s as though nothing has happened. The context of the operating system does not change but data can be changed. The benefit this offers is that the customer doesn’t have to worry about the thing that drives the box – the customer has more time to deal with data and less time to worry about operating systems.

If you have an unchangeable environment how do you deal with patches and other normal everyday problems?

When considering patching, in unchangeable environments consider using a holistic updating approach – similar to firmware updates. It takes a lot of the complexity out of administrating systems.

Aside from preventing errors in the patching processes what are some of the other benefits of non-persistence?

Administrators are concerned about making changes that could make a system unbootable. No matter how wrong something can go – you will have a reliable box that comes back up.

BrickStor offers these key assurances our customers that they have a highly reliable and resilient machine.

Visit our blog for more of Sam’s blog posts on topics like this.