Explain cloud architecture(PAAS) with detailed diagram.

-

CLOUD ARCHITECTURE-PAAS

 Many apps are built on top of infrastructure services and operate on software platforms. These platforms, which might include environments like Oracle or ASP.NET, allow organizations to construct bespoke apps without having to worry about the complexities that lie behind the platforms. Many platforms such as Java EE and Google AppEngine can be used to build architecture frameworks and enterprise applications.


Platform as a Service (PaaS) is a cloud computing architecture in which a specific development and deployment platform is used as the foundation for deployments, such as Java EE, IBM WebSphere, Oracle, Google Apps, .NET, and BizTalk. Only applications designed for the respective platform may be installed in the cloud, making these clouds exclusive.

PaaS is a type of framework computing in which the platform offered serves as the foundation upon which applications are built. These programs are platform-specific and incorporate platform-specific extensions or services, such as Amazon's SimpleDB, that cannot be migrated to other settings. Framework computing is derived from architectures that provide a layer of capabilities and services that shield developers from the underlying specifics. As seen in Figure 1.14, this strategy allows for faster application development and deployment.

1. Development environment:

 All platforms necessitate a development environment where applications are created, created, tested, and validated away from the production environment. Traditional integrated development environments (IDES) can be set to deploy to resources inside a PaaS environment, or they may be integrated directly into the PaaS offering. Microsoft Visual Studio-derived environments may connect to both internal and external instances of Microsoft-specific platforms, allowing for offline development of PaaS-deployed apps. Less standard and more proprietary options, such as Salesforce.com's Force.com, are increasingly providing a PaaS-hosted development environment through which developers can build, test, and deploy their solutions.

 2. Deployment environment: 

Once the program is ready to be consumed by end-users, the next step is to deploy it into production. The run-time environment in which the applications are deployed is essentially this capability. The expectation of on-demand scalability associated with PaaS that does not present in earlier incarnations is the distinction between the PaaS run-time environment and that of hosted or even classic enterprise installed systems. This on-demand scalability may be achieved by putting the environment on a general laaS or by constructing and linking the development, deployment, and dynamic control planes explicitly. The latter creates a platform-specific laaS, with the needed components structured specially to provide and decommission resources based on the deployment environment's particular demands.

Comments

Post a Comment

Popular posts from this blog

Suppose that a data warehouse for Big-University consists of the following four dimensions: student, course, semester, and instructor, and two measures count and avg_grade. When at the lowest conceptual level (e.g., for a given student, course, semester, and instructor combination), the avg_grade measure stores the actual course grade of the student. At higher conceptual levels, avg_grade stores the average grade for the given combination. a) Draw a snowflake schema diagram for the data warehouse. b) Starting with the base cuboid [student, course, semester, instructor], what specific OLAP operations (e.g., roll-up from semester to year) should one perform in order to list the average grade of CS courses for each BigUniversity student. c) If each dimension has five levels (including all), such as “student < major < status < university < all”, how many cuboids will this cube contain (including the base and apex cuboids)?

-
Image
a) A Snowflake Shema is shown in figure below: b) The specific OLAP operations to be performed: 1. Roll-up on course from course_id to department. 2. Roll-up on a student from student_id to university. 3. Dice on course, student with department ="CS" and university = "biguniversity" 4. Drill-down on a student from the university to student_name. c) N = 4 dimensions The cube will contain 54 = 625 cuboids.
Read more

Suppose that a data warehouse consists of the four dimensions; date, spectator, location, and game, and the two measures, count and charge, where charge is the fee that a spectator pays when watching a game on a given date. Spectators may be students, adults, or seniors, with each category having its own charge rate. a) Draw a star schema diagram for the data b) Starting with the base cuboid [date; spectator; location; game], what specific OLAP operations should perform in order to list the total charge paid by student spectators at GM Place in 2004?

-
Image
  b) The specific OLAP operations to be performed are: 1. Roll-up on date from date id to year. 2. Roll-up on spectator from spectator id to status. 3. Roll-up on location from location id to location name. 4. Roll-up on the game from game id to all. 5. Dice with status= “students”, location name= “GM Place”, and year=2004
Read more

Explain market-Oriented Cloud computing architecture.

-
Image
  Market Oriented Cloud Computing (Mocc) As customers rely on Cloud providers to cover all of their computing needs, they will expect certain Qe from their providers to fulfill their objectives and continue their operations. Cloud providers must examine and satisfy the various QoS standards of each unique consumer as stipulated in unique SLAs. To do this, cloud providers cannot continue to install traditional system-centric resource management architectures that do not give incentives for them to share their resources while still treating all service requests as equal insignificance. Instead, market-oriented resource management is required to maintain the supply and demand for Cloud resources at market equilibrium, provide feedback in the form of economic incentives for both Cloud consumers and providers, and promote QoS-based resource allocation mechanisms that differentiate service requests based on their utility. The diagram depicts a high-level architecture for enabling market-orie
Read more