The ready-made environment mechanism (Figure 1) represents a pre-defined, cloud-based platform comprised of a set of already installed IT resources, ready to be used and customized by a cloud consumer. These environments are utilized by cloud consumers to remotely develop and deploy their own services and applications within a cloud. Typical ready-made environments include pre-installed IT resources, such as databases, development tools and governance tools. The ready-made environment mechanism is a defining component of the PaaS cloud delivery model.
Figure 1 - A cloud consumer accesses a ready-made environment hosted on a virtual server.
A ready-made environment will typically include a complete software development kit (SDK) enabling cloud consumers programmatic access to whatever development technologies comprise its programming stack. As commercially available products provided through PaaS environments, ready-made environments can be customized and pre-packaged to support different types of tools, development platforms, and various additional middleware technologies.
Middleware is available for multitenant platforms to support the development and deployment of Web applications. Some cloud providers offer different runtime execution environments for cloud services, based on different runtime performance and billing parameters. For example, a frontend instance of a cloud service can be configured to respond to time-sensitive requests more effectively than a backend instance. The former variation will be billed at a different rate than the latter. As further demonstrated in the upcoming case study example, a solution can be partitioned into groups of logic that can be designated for frontend and backend instance invocation so as to optimize runtime execution and billing.