Have you ever lost a project, or had it badly damaged? If so, then you should definitely read on. The classic idiom that is today’s title identifies a basic principle with broad applicability. Spreading things around reduces risk, particularly of losing them all (at once). For investments it may speak to diversification. For IT, it may speak to backups. But for analytics it may speak to the project environment itself.
Analytics projects often become quite large, and when they do this represents a significant amount of content, and with it, value. Depending on your vendor this valuable content may all be stored in a single project. This is certainly the case with our three-letter competitor. The risk (of a catastrophic failure) is probably the same regardless of project size (and fortunately, low), but when you get these large projects then the consequences are increased significantly. No program is perfect (and I would never make such a claim about Arbutus), so all it takes is one small hiccup in the program to wipe out the entire project; perhaps hours, days or weeks of work. Even if you’ve implemented rigorous backups, you’ll still lose everything since the last backup, and more often than not that can involve a significant amount of wasted time.
Well, what can you do about this situation? The obvious answer is to not use just one basket. The problem with the previous example is that they store everything in a single file. If anything happens to that file then you’ve perhaps lost it all. Instead, why not change the model, to reduce your risk? That’s exactly what Arbutus does!
An Arbutus Analyzer project isn’t a single file, but a whole directory tree of files. Each table definition, script, workspace, index, view, … is a separate file. Even better, each folder is a separate Windows folder of the same name. What this does is dramatically reduce your risk, by spreading the project’s contents across many separate files and folders. If something goes wrong, your total exposure is the recent edits you’ve made to that one object only. In the unlikely event of a serious problem you don’t lose your entire project, just that one item.
But it can get even better. While in separate files, your project is still on the same desktop. Arbutus’ shared folders allow you to spread your content across multiple servers. Shared folders appear just like they were a part of your project, but they aren’t. Instead, they are automatically added in from other locations. Your shared folders may be on another drive or another machine on your network; they may even be on a server in another city or country. When the shared folders are on a server then it is also much more likely that you have frequent and automatic backups. Instead of one basket, there are now many.
Analysts no longer need to accept the risk of storing their entire project in a single “basket”. Arbutus technology not only provides powerful technologies that enable sharing within teams or enterprises, but a valuable by-product is that it also minimizes the risk of losing it all.