When you  build a new Cloud Computing Application, it is necessary to think about your Architecture. There are several considerations when building a Cloud Application such as a SaaS Application. In the architectural point of view, it is not necessary to think about a specific Technology at first. Different Platforms offer different techniques. If you build your Application on Google App Engine, you might use Java or Python, for Amazon EC2 it might be either Java or PHP and for Windows Azure you might use Microsoft .NET. The architecture itself however is independent from the technology you use.
To get started with a Software Architecture for your next Cloud Application, you need to define the basics for your Architecture. Each Software Architecture has some requirements. An architecture should be SMART. Each of the letters in “smart” stands for a requirement.
Specific. The architecture should solve a Problem. It doesn‘t need to be the „coolest“ architecture of all. Often, Software architectures try to be solved by adding the coolest solution instead of doing a solution that is tailored to the problem it should solve. So always be specific to what you want to solve now and in the future.
Measurable. Application basics must be measurable at all time. If you build a Service, the definition could be “if 1 Million People access the service, it must respond within 1 second”. Often, this is described as “the service must be fast if a lot of people access it”. The later one is not measurable at all.

Achievable. The goals set by the architecture must be achievable. It makes no sense if the architecture allows everything but can‘t be done by the developers as it is too complex. This is similar to “Specific”.
Realistic. To sucessfully build a Cloud Platform, you should look at your organisation and figure out what potential is within that organisation. Don’t use a technology that your team is not familiar with and don’t try a Software Architecture where no one in your organisation is familiar with it.
Testable. An output must be testable. This means that Software output should be tested for several constraints such as response time.

For further references about Cloud Architectures, refer to the Book “The art of Scalability”.
The Image displayed for this post is Licenced under the Creative Commons and further details about the picture can be found here.

I am happy to announce that my new E-Book is in stores now! The book is 85 pages in lenght and the target for the book is to provide an overview of Amazon Web Services for .NET Developers. The E-Book by “developer.press” is called “Shortcut” and aims at delivering this topic in one or two evenings to read right after work.

Amazon Web Services for .NET Developers

Amazon Web Services for .NET Developers

The book starts with a description of the service categories offered by Amazon with a brief description of available services. Due to the fact that Services are released often and the book authoring timeframe is about 3-6 month, services such as Amazon Glacier are not yet included. The other 6 chapters focus entirely on building an Application with AWS. Amazon Elastic Beanstalk is used with Asp.NET MVC. Next, a focus on S3, SQS, DynamoDB and Amazon EC2 is given.
Subscribe to this channel to get updates about the book.
You can download the Source Code here.
The book is currently available only in German, an English Version is planned.
The E-Book is available in the iTunes Store and in the Kindle Store.

IDC expects that the market for Big Data grows by almost 40% a year, growing from 3.2 billion Dollars a year to 16.9 billion Dollars per year. This is a huge growth and means almost 40% growth per year. IDC also states that the market for Big Data grows 7-times as fast as the rest of the IT market.
There are several opportunities for companies that are already familiar with Big Data technologies, but also challenges for those companies that are not yet into this type of technology. IDC currently sees the following trends in the Big Data market:

  • There are tremendous opportunities for vendors of Big Data technologies on nearly all levels of the Big Data stack. The stack includes the infrastructure Layer (including Storage, Compute Power, Networking, …), the Data Storage and Management Layer (including Databases), the Analysis Layer (Software for Analysation) and the Decision Support and Automation Layer.
  • Companies already familiar with Big Data Technologies can gain competitive advantage over Companies that are not familiar with Big Data. Big Data is not a simple discipline, it is made up of different disciplines.

IDC states that within the Big Data Stack, each market grows at a different pace. Storage grows by more than 60%, whereas Compute only grows by 27%.
End users that are interested in Big Data might join the IDC Big Data and Business Analytics Forum in Vienna on the 28th of October 2012. The conference is held at the Grand Hotel. Industry Leaders, Researchers as well as IDC Analysts will give an overview and insights into the Big Data Technology. Informations can be obtained here.
What do you think? What is your opinion on Big Data? Leave a comment below to join the discussion!