Social media has become a popular topic in current times. People have shifted the way in which they are connected to each other, from direct interaction to virtual communication. Web technology has evolved and transformed into a social Web, which enables people to collaborate in the virtual space. Building a social Web is not as simple as developing and choosing appropriate programming languages to implement. High volumes of people interacting through virtual social space drove the social Web to adopting the capabilities to give realtime experiences, efficient collaboration, and consistently reliable services. Conversely, data keeps increasing to form loads of data that can impact the performance of the social Web itself in retrieving, storing, and deleting information. Designing robust social Web architecture that has its own service level agreement is major and critical. Web technology commonly has two separate layers, which are frontend tiers (presentation layer) and backend tiers (processing layer). Frontend tiers are used to build and present the information into an adaptable format for touch point access. The backend tiers or processing layers are responsible for processing business logic, including retrieving, storing, deleting, and composing data into structured raw information to the frontend tiers. Both layers commonly use the same processing engine platform or language. Social collaboration trends and technology are discussed in the first section of the article. The following sections will discuss technical details on how to customize frontend tiers to be adaptable to the hybrid backend...
Governments and organizations worldwide are researching greener technologies, techniques, and tips in order to reduce rising energy costs and achieve environmental sustainability. With IT positioned as an effective business enabler, organizations have to allocate higher budgets to meet the rising capital and operational costs of IT centers to support and sustain business operations, outputs, and offerings. However, data centers were found to require enormous amounts of energy. Green IT products, processes, platforms, and practices are being developed to significantly reduce data center power consumption. Global entrepreneurs and executives are enthusiastic that global warming and environmental degradation can be remedied through a host of greener and cleaner technology solutions and services. Serious endeavours are being initiated by green-centric professionals to develop robust energy conservation and harvesting processes. Powerful potential IT infrastructural, architectural, and technological innovations that can enable greener environments are discussed in this article. IT is being positioned as the leading business automation and augmentation enabler, as IT processes, technologies, architectures, and infrastructures collectively play a very pivotal role in business optimization: The Technology Space - Many transformative and innovative technologies are implemented to various disciplines to address and resolve a variety of business challenges and concerns. The Process Space – The design and development of integrated process artifacts are the core activities for exemplary business optimization. If processes are adaptive, lean, and green, then the resulting IT solutions are extensible and sustainable. In order to facilitate these strategic needs, techniques are being employed in order to improve process modeling, orchestration, innovation, reengineering, governance and management...
Tuning service runtime performance will improve the utilization of individual services as well as the performance of service compositions that aggregate these services. Even though it is important to optimize every service architecture, agnostic services in particular, need to be carefully tuned to maximize their potential for reuse and recomposition.the logic within a service is comprised of the collective logic of service capabilities, we need to begin by focusing on performance optimization on the service capability level. In this article we will explore several approaches for reducing the duration of service capability processing. The upcoming techniques specifically focus on avoiding redundant processing, minimizing idle time, minimizing concurrent access to shared resources, and optimizing the data transfer between service capabilities and service consumers. Let's first look at the elimination of unnecessary processing inside a service capability. Specifically what we’ll be focusing on is: avoidance of repeating calculations if the result doesn’t change; avoidance of costly database access if the data doesn’t change; developing a better performing implementation of capability logic; delegating costly capability logic to specialized hardware solutions; avoidance of costly XML transformations by designing service contracts with canonical schemas. A common means of reducing the quantity of processing is to avoid duplication of redundant capabilities through caching. Instead of executing the same capability twice, you simply store the results of the capability the first time and return the stored results the next time...
In this section, the ECSA is evaluated based on the model and framework we presented in this paper and it is analyzed using several typical enterprise cloud service architectures as our case studies.
ECSA style is defined as a combination of ESOA and ECC in Section 3. Here, we show how to analyze the ECSA style based on and the framework defined in Section 2.
Based on, we should show that the two styles ESOA and ECC are conflict-free, that is, semantically no contradictions should occur. Let us assume that
ESOAl and ECCl
are interpretations of ESOA and ECC, respectively. Then, it is necessary to show that
ESOAl ∩ ECCl ≠ ø. Obviously, this is true because:Both share the Service concept and the ECC style extends some of the concepts from ESOA. We have shown this in Section 3.2.
SClESOA ∩ SClECC ≠ ø,
SIlESOA ∩ SIlECC ≠ ø,
SMlESOA ∩ SMlECC ≠ ø,
SPlESOA ∩ SPlECC ≠ ø,
SQlESOA ∩ SQlECC ≠ ø
Both styles are complementary with each other and can coexist in an enterprise architecture. Most enterprises are moving to a hybrid cloud architecture in which two styles are applied for designing the next generation enterprise architectures. The style consistency can be checked by another criterion – "A style is consistent if there exists at least one architectural configuration that conforms to the style". This means that a style is consistent if there is at least one instance of the style. We will show that Amazon.com is an instance of the ECSA style in...
CloudPatterns.org is a community site dedicated to documenting a master patterns catalog comprised of design patterns that capture and modularize technology-centric solutions distinct or relevant to modern-day cloud computing platforms and business-centric cloud technology architectures. Part of this catalog is comprised of compound patterns that tackle contemporary cloud delivery and deployment models (such as public cloud, IaaS, etc.) and decompose them into sets of co-existent patterns that establish core and optional feature sets provided by these environments. Cloud computing patterns are applied via the implementation of individual or combinations of different technology mechanisms. Together, the documentation of patterns and mechanisms provides an extremely concrete view of cloud architecture layers and the individual building blocks that represent the moving parts that can be assembled in creative ways to leverage cloud environments for business automation. Each design pattern in the cloud computing catalog is associated with one or more mechanisms.