Chose categories and files from the sidebar!

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.

(SAAS)

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

Cloud Computing Architecture Breaks Down

July 7th, 2009

z-createwritten by gunther gerlach-2009

increase the velocity with which applications are deployed, and lower costs, but it doesn’t increase systems performance over the traditional architecture. compile different facets, including the server, storage, network, and virtualization technology that drives environments to the software that runs in virtual appliances that can be used to assemble applications in minimal time. definitely transforms the way we design, build, and deliver applications, and the architectural considerations that enterprises must make when adopting and using technology.

Gunther Gerlach