Scalable websites

1. Building Scalable and Resilient Web Applications on Google Cloud Platform
Name
Student Number
Date
Area: Building resilient and scalable applications on the cloud
Building applications that are both scalable and resilient is a very vital part of any
architecture of applications. Having an application that is well-designed needs to have
the ability to seamlessly scale as the demand decreases and increases and also have
enough resilience to bear the loss of any computer resources. The Google Could
platform helps developers to create and run web applications in an easy and cost-
effective way. Some services like Autoscaler and Google Compute Engine help in
making it easy to adjust the developer’s applications’ resources as required by the
demands. In this paper, there will be details on how to use the Google Could Platform
in building application architectures that are both resilient and scalable.
1. Question
Among the several available ways of building web applications through various platforms, which
is the best way of developing web applications that are both resilient and scalable over the Google
Cloud platform?
2. Value
The research topic is very valuable to anyone who has an interest in cloud computing as it
will provide a viable solution to the creation of resilient and scalable applications. The internet is

2. fast evolving, and people are warming up to the prospect of working and saving their documents
in the cloud. The creation of resilient and scalable applications is a vital part of any architecture of
applications. Having a well-designed application needs to seamlessly scale with the available trend
in demand. A web application that is scalable is one which operates well with one or several users
and can handle all the traffic and stress brought by large numbers of users. Through the addition
as well as the removal of virtual machines only when the need arises, all scalable applications just
utilize the necessary resources in meeting the demand (Zhu et al., 2014).
On the other hand, a resilient web application is one which operates continuously even if
there might be unexpected or expected failures of the system’s components. Even if a certain
instance or a whole section develops a bug or other issue, an application that is resilient will operate
and remain tolerant to all faults and the repair itself over time (Zhu et al., 2014).
Many conventional architectures which support resilience and scalability mainly need a lot
of investment and resources pumped in. However, with solutions that are on-premises, scalability
majorly means that a decision has to be made between spending too much on the capacity of a
server to handle traffic and peak stress or just making purchases on average need, risking poor
performance by applications or even the experience of the users whenever the traffic is at its peak.
Building resilient applications over Google cloud will mean more than the capacity, but the
location is vital in this case (Zhu et al., 2014).
Justification
According to Wei et al., (2012), for any application to go on with successful operations in
its lifecycle, it needs to be scalable at all its architectural levels. As more system users get to
interact with the given application, the demands for resources for every tier will gradually increase.

3. Nevertheless, the failure or success of several applications mainly depends on a database system
that is well-conceptualized, implemented as well as architecture.
Despite the fact that the major aim of database design is allowing automated database tier
is scaling horizontally, implementing a solution like that is a goal that is quite elusive at the
moment in the world of computing. Nevertheless, there are several concepts of design that one
needs to follow in allowing the scaling of database scaling to different levels that include both the
horizontal and vertical database tier scaling (Wei et al., 2012).
Sharma et al., (2012) state that in an application’s early stages, whenever the load for
database happens to be light, there is a small instance size which can be utilized effectively for
both the slave and master databases. With an increase in the load, the master database can be
moved to a larger size of the instance, enabling it to take advantage of the extra power for
processing, throughput for input/output and the existing memory in the given system.
According to Krintz (2013), it is highly recommended that there is an implementation of
one or more slave databases on top of the master database, without regard to the phase of the
lifecycle of an application. The existence of several slave databases boosts the total availability as
well as the reliability of the given application and also enabling horizontal scaling of the database
through the use of a proxy database for the reads in the database.
The question is quite feasible because the mechanisms that will be used in the development
of the resilient and scalable web applications are already in existence. The idea is very clear and
with the use of proper systems and tools, it is very simple and possible to create the application
through the Google Could Platform (Krintz, 2013). The cloud in this case sis very accessible and
cheap to use as compared to the other available platforms of app development.

4. The project is feasible because sits success or failure can be measured in the end through a
successful prototype or project. The ability of the application to continue operating under severe
conditions and a lot of traffic is a good parameter son which the success can be measured. Failure
will be the other way round of the results.
The project is ethical because it does not interfere with the normal operations of other
applications. It does not also interfere with the normal lives of other people or jeopardize the
security of their data in any manner, qualifying it to be ethical.
Platform as a service basically do not have the direct support for management of app state.
At the same time, the conventional state management styles such as clustering cannot be applied
since the platforms of PaaS provide minimal support for the changing configuration for the
underlying platform. In this research paper, the research has been built on ReLoC implementation
mechanisms. The technique utilizes services that are loosely-coupled as well as messaging
technology that is platform agnostic scalable in the propagation as well as saving states for
sessions.
In this case, there is a presentation for the actual implementation of the ReLoC onto a
platform of PaaS as well as a practical evaluation of the scalability hypotheses that are original as
well as the proposed application architecture’s. At the same time, there is a presentation of the
challenges facing the ReLoC implementation (Krintz, 2013). It is clear that ReLoC enables
various applications to do proper scaling and also reduces the failures experienced in individual
app instances in the process of maintaining the available state as well as hiding the system’s
failures from its end-users.

5. References
Krintz, C. (2013). The appscale cloud platform: Enabling portable, scalable web application
deployment. IEEE internet computing, 17(2), 72-75.
Sharma, V. S., Sengupta, S., & Annervaz, K. M. (2012, June). Reloc: A resilient loosely coupled
application architecture for state management in the cloud. In Cloud Computing
(CLOUD), 2012 IEEE 5th International Conference on (pp. 906-913). IEEE.
Wei, Z., Pierre, G., & Chi, C. H. (2012). CloudTPS: Scalable transactions for Web applications in
the cloud. IEEE Transactions on Services Computing, 5(4), 525-539.
Zhu, J., He, P., Zheng, Z., & Lyu, M. R. (2014, June). Towards online, accurate, and scalable qos
prediction for runtime service adaptation. In Distributed Computing Systems
(ICDCS), 2014 IEEE 34th International Conference on (pp. 318-327). IEEE.