Archive

Archive for July, 2009

Options for your Virtual Infrastructure

July 20th, 2009

written by gunther gerlach-2009

I have talked about and also about but, what options are available to implement Infrastructure implementations? Well, that is simple!

 tech-2

 

Hardware technologies for ()

has a layer (usually a thin Linux kernel shown here as a or standard OS) that is loaded directly on the bare server. To allocate hardware and resources to the virtual machines (VMs), all hardware on the server must be virtualized. The next layer up shows each chip, board, etc. that must be virtualized so that it can be assigned to the VMs. Once in the VM itself, there is a complete copy of an operating system and finally the application or workload.

Gunther Gerlach

Click here for more details!

July 20th, 2009
Comments Off

Günther Gerlach

EXECUTIVE LEADERSHIP: World-Class Development Organizations, Web-Services, E-Commerce, IT Operations, Scalable , Tier-1 Systems.

Highly accomplished executive with 10+ years of experience directing high performance enterprise web-based solutions. Proven executive leader cultivating relationships at the SVP and C-level plus with the ability to train and lead cross-functional onsite and international teams leading initiatives being developed by up to 230 engineers driving the design and execution of critical components for Amazon global systems architecture and its Enterprise Elastic Computer Cloud (EC2) plus inter-dependent SAP integration solutions for DHL Express. Combines technical skills including proficiency in 12 programming languages with visionary business acumen to create strategic enterprise-wide alignment. Managed Budgets up to $22 MM. Entrepreneur successfully opened and directed a technology retail company. Trilingual: English, Spanish, Italian.

Gunther Gerlach

Architectural Tips for Infrastructure as a Service (IaaS)

July 8th, 2009

box10written by gunther gerlach-2009

Evolving application architectures just as P have shown that is a natural extension of current trends and best practices, the same is true when viewing from an architectural perspective. Again, is nothing new, yet in its implementation, it changes everything that we do.

Changing application designs In the past, applications were built to handle larger workloads through vertical scaling. Put more processors and memory on a mail server to handle a larger volume of traffic. Scale up a database server to increase throughput. Run high-performance computing jobs on a supercomputer.

Gunther Gerlach

Key Features for User Story Implementation

July 8th, 2009

z-stepswritten by gunther gerlach-2009

A user story describes desired functionality from the customer (user) perspective. A good user story describes the desired functionality, who wants it, and how and why the functionality will be used.

The define a User Story as Independent, Negotiable, Valuable, Estimable, Small, Testable. Let’s see what each one means:

Independent - One user story should be independent of another (as much as possible). Dependencies between stories make planning, prioritization, and estimation much more difficult. Often enough, dependencies can be reduced by either combining stories into one or by splitting the stories differently.

Gunther Gerlach

Architectural layers of cloud computing

July 8th, 2009

dat1written by gunther gerlach-2009

can describe services being provided at any of the traditional layers from hardware to application. In practice, cloud service providers tend to offer services that can be grouped into three categories: , , and . These categories group together the various layers, with some overlap.

()

features a complete application offered as a service on demand. A single instance of the software runs on the cloud and services multiple end users or client organizations.

Gunther Gerlach

Cloud Computing Infrastructure Models

July 8th, 2009

tirawritten by gunther gerlach-2009

There are many considerations for architects to make when moving from a standard enterprise application deployment model to one based on . There are public and that offer complementary benefits, there are three basic service models to consider (Public, private, and ), and there is the value of open APIs versus proprietary ones.

models: Public, private, and

Organizations can choose to deploy applications on public, private, or , each of which has its trade-offs. are typically “out there” on the Internet and are typically located on premises, a private cloud might be hosted at a co-location facility as well.

Gunther Gerlach