The universe is change; our life is what our thoughts make it.
(Marcus Aurelius)

If you have a job in IT (and who among my readers hasn't?), then it is going to fundamentally change soon.

Why?

In my own job, I see the full spectrum from where IT innovation is created to the very last laggards who are still depending a lot on mainframes and other ancient technology. Some things in IT are new (like, every week there's a new startup/technology/trend that is shaking up the industry), and some things are just repetitions of stuff that has happened before, albeit in slightly different colors.

So now, the world of IT as we know it is changing (again) and this time, change will impact organizations, roles and jobs.

Let's dive a little bit into what's happening. Don't worry, change is good, but only if you prepare for it.

While most customers immediately understand how the magic of Oracle's Hybrid Columnar Compression, intelligent storage servers and flash memory make Exadata uniquely powerful against home-grown database systems, some people think that Exalogic is nothing more than a bunch of x86 servers, a storage appliance and an InfiniBand (IB) network, built into a single rack.

After all, isn't this exactly what the High Performance Computing (HPC) world has been doing for decades?

On the surface, this may be true. And some people tried exactly that: They tried to put together their own version of Exalogic, but then they discover there's a lot more to building a system than buying hardware and assembling it together. IT is not Ikea.

Why is that so? Could it be there's more going on behind the scenes than merely putting together a bunch of servers, a storage array and an InfiniBand network into a rack? Let's explore some of the special sauce that makes Exalogic unique and un-copyable, so you can save yourself from your next 6- to 12-month science project that distracts you from doing real work that adds value to your company.

If I had to formulate in one sentence what my job and that of my teammates is, I'd say something like:

"To show our customers the business value of Oracle's Engineered Systems"

Because at the end of the day, customers pay real money only if there's some real value they see in a solution.

And that is the problem most people in IT struggle with: How is what you do in IT related to your company's total value chain?

Most of the time, people, both those working in IT and those selling and supporting into IT departments are consumed with functions and features, tech specs, standards and other tech stuff. Worse yet: Some people look at Oracle's Engineered Systems like Exadata and Exalogic and they only see a bunch of servers in a rack, because all they know is components, servers, tech stuff.

This is dangerous terrain: Because if you can't show the business value of your IT to your company, you're going to be put on the list of cost centers to be squeezed, and budget cuts are never a good motivator for your job.

So what is the value of IT to the business? Or more specifically, what is the value of Engineered Systems for our customers' businesses?

Ever since I've been using a Mac, I enjoy using Sparse Encrypted Disk Images for a variety of tasks, for instance securely storing data that can be backed up somewhere else, say on a hosting server.

In fact, most of my project/personal data on my Mac sits on sparse encrypted disk images that are regularly rsynced to an external storage service, Strato's in particular.

The beauty of this solution lies in it simplicity:

Sparse encrypted disk images show up just like any other hard drive. But on the back end, they translate into a bunch of flat files that store all the data in an encrypted manner. By rsyncing the backing store, sparse encrypted disk images can be easily backed up across the net, while ensuring privacy and convenience.

Here's how to do similar things with Solaris and ZFS, including some extra data integrity magic:

After having gone through TOGAF training and certification, I've now caught the Enterprise Architecture bug, as you can probably tell by this article. It is a really neat way to add structure to the IT development process and to better understand what it really means to solve business problems with IT.

One of the first things TOGAF recommends architects do when establishing an Enterprise Architecture practice within a company is to formulate Architecture Principles that guide the development of solutions. During the last few workshops and during some discussions with other architects, three principles in particular struck me as being key to successfully developing a Cloud solution:

Recently, I attended a customer workshop where the customer declared that they standardized on x86, VMware and Linux.

That got me and my colleague thinking about what standardization really means and whether that actually makes sense.

The workshop was actually about defining a PaaS platform for the customer, and early in the process they just said: Fine, but it's gonna be x86, VMware and Linux, because that's our standard. WTF?

In Summer 2010 I learned about a cool new geeky movie called Iron Sky that was crowd-funded. I decided to help finance it with a small sum.

Then the second Iron Sky teaser came out and I thought: Wow, this is looking really good! And I invested some more.

In December 2010, I was invited to attend the Iron Sky shootings in Frankfurt together with my brother. This is where we got to meet the crew, the actors, the people behind the movie and other investors. And I thought: Wow, this is not only cool, this is for real! Everybody was 100% determined to make this the coolest movie ever, and everybody put in so much attention to detail, love and true craftmanship that I thought: "Yep, this is going to be a true movie milestone!" And I also got to shoot an interview with the director and the inventor of Iron Sky. This time, my brother and I together invested a bit more to help this baby fly.