written by gunther gerlach-2009
This material covers the initial set up of an entire Cloud environment at Amazon Cloud infrastructure to run any web implementation solutions. This is the quickest answer that you may find out there, so let’s stat it!
We will cover all the steps to set up an entire environment in a cloud platform, from creating an user account at Amazon Web Services to creating and customizing Virtual machines (AMI), Virtual Storage Units, Virtual backups, Elastic IP’s, etc.
For all of you that don’t understand some of the acronyms used here, let’s just to look at them before to start:
Gunther Gerlach
Basically, moving to the cloud it shouldn’t impact your architecture with many changes as we believe. If your platform has a well design architecture based on independent layers (UI, Logic, Data, etc), adapting to work in a Cloud environment only mean to add a new layer of virtual environments to your n-tiers environment. Moving to the Cloud only become a problem when solutions don’t have a solid and well designed architecture and basically they are pushed back at the moment to adapt to this new age of technology.
Gunther Gerlach
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.
Gunther Gerlach
