Architetture enterprise

Le Architetture Enterprise (EA) sono l’espressione olistica degli obiettivi di business, della strategia, e dei processi di un organizzazione definiti all’interno dell’Information Tecnology. Nell’essenza, l’EA definisce l’architettura finale, ad un dato momento, che è necessaria per supportare la missione e la strategia di una organizzazione.

La comprovata esperienza di mondora s.p.a. nel disegno di architetture enterprise è maturata nel mondo CORBA e integrata da profonda conoscenza e frequente utilizzo delle specifiche J2EE.

Le sue applicazioni sono flessibili e robuste, scalabili e in grado di soddisfare un numero crescente di richieste evitando di compromettere le prestazioni e senza dover cambiare l’applicazione.

Mondora s.p.a. sostiene le aziende in tutte le fasi di sviluppo di una Architettura Enterprise, in particolare fornisce:

  • supporto nella selezione della tecnologia da utilizzare,
  • disegno e architetture a componenti e a servizi,
  • revisione di progetti e redazione di specifiche,
  • sviluppo di prototipi,
  • realizzazione di sistemi informatici completi,
  • ottimizzazione prestazionale e supporto per superare le contingenze,
  • refactoring e ridisegno di architetture per sistemi mission-critical,
  • base di supporto, validazione, test delle tue idee, anche le più bizzarre.

Mondora s.p.a., inoltre, documenta e rappresenta l’EA attraverso viste o modelli architetturali che mostrano come gli obiettivi correnti e futuri di un’organizzazione verranno raggiunti.

Oblique Scaling™

Last edited by on April 1, 2008 6:03 am

I’m just back after a weekend on the snow, and I’m happy to know that Oblique Scaling is producing the correct result in mondora.com. Mondora’s engineers thought Hardware could be thought as Software, like Virtualization does.
Having Sense as a common infrastructure, they’ve just released a component called Scent that meets Hardware availability and Software suffering.
During last past 2 weeks they stressed the Sense Workshop on a 4 core HP starting with 1 core switched on and the rest switched off. An endurance test of 12 hours has been run, to check how Sense self regulate having Hardware considered as an High Available Service with an identified Service Level Agreement.
When system increased in suffering by switching from good Service status to worst, Sense has anticipated lack of performance by working with the Hardware Virtualization Platform and asking to Scale Up.
In terms of Business, benefits gained are:
  1. This approach that Predict system performances and do some actions to make the system surviving.
  2. This approach let to Scale when unpredictable things occurs. This is the case of a Campaign that is producing more than the expectation and if the system is not adaptive, Campaign is loosing all the Customer, both the predicted and the unpredicted.
In terms of Manageability, benefits gained are:
  1. Vertical Scaling is predicted by Application Constraints and matched with Hardware Service Status
  2. Policy can be configured (ex. switch a CPU after a 15 minutes of suffering)
  3. Scaling policies are described as Algorithms and implements different strategy. This let to configure a strategy where network latency is compared with Service metrics. By comparing Sense can avoid Horizontal Scaling versus Vertical Scaling
In terms of Development, Hardware is saw as a Service itself and can be allocated runtime when business constraints need it, like another Service on the Net.
By having this building block certified, Sense is becoming a real implementation of a Future SOA where Services:
  • are available over the network in a cluster environment
  • are self federating
  • are balancing on SLA policies
  • are balancing on Business Constraints by flocking
  • can balance on most productive in terms of ROI
  • are multi protocol invokable
  • can be perceived from the outside environment as inside components
  • are physical resources
This is a really implementation of what SOA can be.

Comments (0)