Wiki » History » Version 19
Pierre Marc, 06/16/2011 12:09 PM
| 1 | 12 | Pierre Marc | h1. Nirva application platform |
|---|---|---|---|
| 2 | 5 | Pierre Marc | |
| 3 | 15 | Pierre Marc | h2. Overview |
| 4 | 9 | Pierre Marc | |
| 5 | 9 | Pierre Marc | Nirva is a robust application server combined with integration services and orchestration. |
| 6 | 9 | Pierre Marc | |
| 7 | 9 | Pierre Marc | Nirva is used as: |
| 8 | 9 | Pierre Marc | * An Application Server for enterprise-wide projects. |
| 9 | 9 | Pierre Marc | * An Application Platform for the products. |
| 10 | 9 | Pierre Marc | |
| 11 | 9 | Pierre Marc | _Projects_ |
| 12 | 9 | Pierre Marc | |
| 13 | 9 | Pierre Marc | Nirva targets tactical projects for large and medium companies, especially for back-end processes. This kind of project is often motivated by cost reduction but is paradoxically supported by oversized products (e.g. WebSphere, WebLogic). Nirva allows significant cost savings, not only for licenses, but also for development, maintenance and operations costs. |
| 14 | 9 | Pierre Marc | For the larger companies, Nirva adequately complements the enterprise strategic tools by allowing them to be perceived as a business solution by hiding the technical aspects of the various components and by federating heterogeneous information and application systems. |
| 15 | 9 | Pierre Marc | For medium size companies, Nirva projects can be used as a more strategic tool by supplying a robust, independent and complete application base layer. |
| 16 | 9 | Pierre Marc | |
| 17 | 9 | Pierre Marc | _Products_ |
| 18 | 9 | Pierre Marc | |
| 19 | 9 | Pierre Marc | For software suppliers, Nirva is used as an application backbone supporting their own products. Its feature rich and flexible architecture hides a significant part of the technical components, thus allowing product development to focus on core functionality. Nirva offers value from the technical integration layer up to the presentation and front-end layer. |
| 20 | 9 | Pierre Marc | Nirva supports the development of applications opened to the outside world (APIs), secured (users and rights management) and extensible (distributed architecture). Its application domain is unrestricted (bank, insurance, industry, health care, etc.). |
| 21 | 9 | Pierre Marc | Nirva can host and support standard applications (client/server) or ‘Software as a Service’ (SaaS) type with multitenancy management. |
| 22 | 9 | Pierre Marc | Users are small and medium software suppliers. Nirva can also be used by specialized integrators who wish to standardize and reuse their development. |
| 23 | 9 | Pierre Marc | |
| 24 | 17 | Pierre Marc | _read more:_ "Nirva overview":http://download.nirva-systems.com/server/docs/nirva_overview.pdf |
| 25 | 18 | Pierre Marc | |
| 26 | 18 | Pierre Marc | h2. Updates |
| 27 | 18 | Pierre Marc | |
| 28 | 19 | Pierre Marc | [[updates_40000|Version 4.0.000]] |