Chose categories and files from the sidebar!

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 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 private clouds that offer complementary benefits, there are three basic service models to consider (Public, private, and hybrid clouds), and there is the value of open APIs versus proprietary ones.

models: Public, private, and hybrid clouds

Organizations can choose to deploy applications on public, private, or hybrid clouds, each of which has its trade-offs. Public clouds are typically “out there” on the Internet and private clouds 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 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

How does a Project Manager add value to an Agile Scrum team?

July 7th, 2009

z-share written by gunther gerlach-2009

Definition: Agile project management is as radically different from traditional project management as agile processes are different from traditional methodologies. Rather than plan, instruct and direct, the agile facilitates, coaches and leads.

 

Recently I came across of someone posting about the value of a PM in an environment. It’s been a long time from most of the companies realized the important role of PMs But it looks like some Scrum process consultants, after run out of ideas to justify the PM’s role, they just wants to get rid off them… big mistake

Gunther Gerlach

Cloud Computing

June 30th, 2009

db5 written by gunther gerlach-2009

Everyone has an opinion on what is . It can be the ability to rent a server or a thousand servers and run a geophysical modeling application on the most powerful systems available anywhere. It can be the ability to rent a , load on it, turn it on and off at will, or clone it ten times to meet a sudden workload demand. It can be storing and securing immense amounts of data that is accessible only by authorized applications and users. It can be supported by a that sets up a that includes the OS, Apache, a MySQL database, Perl, Python, and PHP with the ability to scale automatically in response to changing workloads.

Gunther Gerlach

Service Mediation and Adaptation

June 22nd, 2009

ledwritten by gunther gerlach-2009

The assimilation of services through presents major integration development and maintenance costs. Service providers need to compose their services effectively in coordination with other services if they are to engage in oncoming market opportunities and situations. Further up the supply and distribution chain, if services are to be brokered and delivered through other intermediaries (e.g., for authentication, payment, device-specific service presentations), they will need to be interfaced with that operate in various ways. Thus, one can expect that services will have to interact with one another in ways not necessarily foreseen during their development or deployment. A key challenge in this setting is : the act of repurposing existing services so that they can interact in unforeseen manners by intercepting, storing, transforming, and routing messages going into and out of these services.

Gunther Gerlach