Architectural Tips for Infrastructure as a Service (IaaS)
written by gunther gerlach-2009
Evolving application architectures just as P have shown that cloud computing is a natural extension of current trends and best practices, the same is true when viewing cloud computing from an architectural perspective. Again, cloud computing 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.
Key Features for User Story Implementation
written 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 INVEST model 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.
Architectural layers of cloud computing
written by gunther gerlach-2009
Cloud computing 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: Software as a Service, Platform as a Service, and Infrastructure as a Service. These categories group together the various layers, with some overlap.
Software as a service (SAAS)
Software as a Service 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.
Cloud Computing Infrastructure Models
written by gunther gerlach-2009
There are many considerations for cloud computing architects to make when moving from a standard enterprise application deployment model to one based on cloud computing. 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.
Cloud Computing Architecture Breaks Down
written by gunther gerlach-2009
Cloud computing increase the velocity with which applications are deployed, and lower costs, but it doesn’t increase systems performance over the traditional architecture. Cloud computing compile different facets, including the server, storage, network, and virtualization technology that drives cloud computing environments to the software that runs in virtual appliances that can be used to assemble applications in minimal time. Cloud Computing definitely transforms the way we design, build, and deliver applications, and the architectural considerations that enterprises must make when adopting and using cloud computing technology.


