Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Gyrex/Eclipse Gyrex Project"
< Gyrex
(New page: == Eclipse Gyrex Project (gyrex) == ''Old project name: CloudFree Commerce Platform (cloudfree)'' The Eclipse Gyrex Project will develop infrastructure, components, and tools that will su...) |
|||
| Line 1: | Line 1: | ||
| + | We decided to make adjustments to the CloudFree project scope. This page contains the proposed new project scope. In [https://bugs.eclipse.org/bugs/show_bug.cgi?id=262232 this bug] we also decided on a new name for the CloudFree project which will be used in this scope. | ||
| + | |||
== Eclipse Gyrex Project (gyrex) == | == Eclipse Gyrex Project (gyrex) == | ||
''Old project name: CloudFree Commerce Platform (cloudfree)'' | ''Old project name: CloudFree Commerce Platform (cloudfree)'' | ||
| Line 5: | Line 7: | ||
The Eclipse Gyrex Project consists of the following components: | The Eclipse Gyrex Project consists of the following components: | ||
| − | * Contextual Runtime - This is a central model for establishing a notion of a runtime context. The context is intended to be used for building multi-tenant applications offered as software as a service (SaaS). But it may also be useful in a non-SaaS environment. Typically, certain aspects in a SaaS system are not static | + | |
| − | * Clustering & Monitoring Service - With scalability and operational simplicity in mind, the clustering service will enable multiple installations to form an application cluster and provide operators with an intuitive management interface based on the admin service. Monitoring will be built into the platform as an essential concept and will | + | * Contextual Runtime - This is a central model for establishing a notion of a runtime context. The context is intended to be used for building multi-tenant applications offered as software as a service (SaaS). But it may also be useful in a non-SaaS environment. Typically, certain aspects in a SaaS system are not static. For example, some extensions contributed to an extension point should be available to some tenants but not to others. The contextual runtime will allow such filtering based on the current execution context. |
| + | |||
| + | * Clustering & Monitoring Service - With scalability and operational simplicity in mind, the clustering service will enable multiple installations to form an application cluster and provide operators with an intuitive management interface based on the admin service. Monitoring will be built into the platform as an essential concept and will also provide integration and extension points. | ||
| + | |||
* Admin Service - A central administration interface provided by the platform. The service will provide extension points to allow extenders to integrate nicely with the platform. | * Admin Service - A central administration interface provided by the platform. The service will provide extension points to allow extenders to integrate nicely with the platform. | ||
| + | |||
* Exemplary Web Application - An exemplary web application will be created which demonstrates programming, scalability and operational concepts provided by the platform. | * Exemplary Web Application - An exemplary web application will be created which demonstrates programming, scalability and operational concepts provided by the platform. | ||
Although the project's main focus is building a server platform based on Equinox running standalone, it is also anticipated that the platform can run embedded in an existing JavaEE application container and integrated with container specific APIs and tools to implement the features provided by the platform. However, the development of such vendor-specific integrations is out of the project's scope. The Eclipse Gyrex Project will provide frameworks and extension points to allow third parties building such integrations. | Although the project's main focus is building a server platform based on Equinox running standalone, it is also anticipated that the platform can run embedded in an existing JavaEE application container and integrated with container specific APIs and tools to implement the features provided by the platform. However, the development of such vendor-specific integrations is out of the project's scope. The Eclipse Gyrex Project will provide frameworks and extension points to allow third parties building such integrations. | ||
Revision as of 11:39, 13 February 2009
We decided to make adjustments to the CloudFree project scope. This page contains the proposed new project scope. In this bug we also decided on a new name for the CloudFree project which will be used in this scope.
Eclipse Gyrex Project (gyrex)
Old project name: CloudFree Commerce Platform (cloudfree)
The Eclipse Gyrex Project will develop infrastructure, components, and tools that will support development, provisioning and operation of scalable server solutions. Development of a fully-fledged JavaEE application server is out-of-scope of this project. Instead, we will focus on the runtime infrastructure and core components around Equinox which are essential for building server solutions or server application products. Additionally, exemplary services/applications will be provided which demonstrate the extensibility and flexibility of the Eclipse Gyrex Project. Where possible, existing Eclipse technologies will be re-used and integrated.
The Eclipse Gyrex Project consists of the following components:
- Contextual Runtime - This is a central model for establishing a notion of a runtime context. The context is intended to be used for building multi-tenant applications offered as software as a service (SaaS). But it may also be useful in a non-SaaS environment. Typically, certain aspects in a SaaS system are not static. For example, some extensions contributed to an extension point should be available to some tenants but not to others. The contextual runtime will allow such filtering based on the current execution context.
- Clustering & Monitoring Service - With scalability and operational simplicity in mind, the clustering service will enable multiple installations to form an application cluster and provide operators with an intuitive management interface based on the admin service. Monitoring will be built into the platform as an essential concept and will also provide integration and extension points.
- Admin Service - A central administration interface provided by the platform. The service will provide extension points to allow extenders to integrate nicely with the platform.
- Exemplary Web Application - An exemplary web application will be created which demonstrates programming, scalability and operational concepts provided by the platform.
Although the project's main focus is building a server platform based on Equinox running standalone, it is also anticipated that the platform can run embedded in an existing JavaEE application container and integrated with container specific APIs and tools to implement the features provided by the platform. However, the development of such vendor-specific integrations is out of the project's scope. The Eclipse Gyrex Project will provide frameworks and extension points to allow third parties building such integrations.