cloud

In the last few articles, I shared a few thoughts on how I think the world of IT is changing, which became the context for my good-bye to the world of physical IT altogether.

As of last week, I started working for Amazon Web Services (AWS) as a Solutions Architect, helping customers architect systems and solve technical problems using the latest cloud computing technologies. I'm very thankful to be able to work here, as it brings me back to the very center of IT innovation and gives me the opportunity to do lots of new and interesting things.

In the last weeks, I've been digging around AWS and its services, playing with stuff and meeting lots of inspiring people. So I thought I'd put together a few links for those interested in exploring the world of the AWS cloud computing platform for you to learn more about AWS:

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.

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:

First of all: Apologies for not posting for a long time. The reason? I was having too much fun with node.js and the Joyent Cloud :).

What started as a small experimental hack turned quickly into an exciting new pet project involving the good old Mandelbrot Set, as a web service, running in the Joyent cloud, programmed in node.js.

But first things first: Let's take a look at node.js as a language and programming model, at the Joyent Cloud and how it relates to Solaris and finally some details on how the picture you see was rendered inside the Joyent Cloud, including an interactive Mandelbrot Set explorer you can play with now, written as a web app.

Whenever you run a professional server, a home server, a hosted virtual server or just a blog on a shared web space, you run a service that provides something useful to your users, readers or whatever consumers your service caters to.

Too bad if things go wrong and you're the last to notice.

Enter Monitis.com*: This service allows you to easily track your servers, websites, blogs or anything else that can be accessed through the internet, or that is able to run a simple agent. Monitoring from the cloud, if you will, at reasonable prices. And if all you need is some basic monitoring, then there's a free version called mon.itor.us, too.

Let's check this out in some detail: