Guidance for Development and Management of Sustainable Enterprise Information Portals (2018) / Chapter Skim
Currently Skimming:
Pages 31-37
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 31... ...
31 Industry Practices for Sustainable EIPs Many industries outside of the traditional transportation IT environment have a longer history of leveraging EIPs to support their business processes. This section highlights current practices and technologies used across the IT industry to design and maintain sustainable EIPs.
|
From page 32... ...
32 Guidance for Development and Management of Sustainable Enterprise Information Portals reducing IT infrastructure operation and maintenance time to a minimum. Figure 3-1 shows a diagram representing the differences between on-premise and cloud architecture.
|
From page 33... ...
Industry Practices for Sustainable EIPs 33 3.1.2 Scalable, Flexible, and On-Demand IT Capabilities Traditional on-premise IT infrastructure is typically sized to satisfy an estimated maximum demand and as such always operates at its highest design level, no matter the actual level of demand. Moreover, if demand exceeds the planned maximum of on-premise infrastructure, it is not possible to scale up to meet the extreme demand.
|
From page 34... ...
34 Guidance for Development and Management of Sustainable Enterprise Information Portals a component is localized and independent. This characteristic allows distributed software running on a distributed computer system to recover from failure by restarting tasks that failed on a component on a different server using another software component.
|
From page 35... ...
Industry Practices for Sustainable EIPs 35 3.3 Use Layered System Design To further optimize the sustainability of EIPs and organize the distribution of software components across a server cluster, a three-tier or layer architecture, separating software components into groups or classes, is often preferred. As illustrated in Figure 3-3, the recommended three-tier architecture is composed of the following layers or groups of software components: • A user interface layer, also called a presentation tier, containing the various software components supporting the interfaces (mobile, web, or machine)
|
From page 36... ...
36 Guidance for Development and Management of Sustainable Enterprise Information Portals This type of architecture is often found in software used in critical systems, such as aircraft and power plants. It is one of the earliest ways that enterprise software was designed.
|
From page 37... ...
Industry Practices for Sustainable EIPs 37 Table 3-1. Proprietary versus open source versus SaaS cost comparison.6 Oracle Enterprise Edition on Spark Server EDB Postgres Plus Enterprise Edition on IBM Powerlinux AWS Aurora Type Proprietary Open Source SaaS Specification 4 sockets/32 cores 4 sockets/32 cores 4 servers of 8 cores Capital expenditure Server $62,874 $51,755 $- License fee per core Database $47,500 $- $- Partitioning $11,500 $- $- Data guard $11,500 $- $- Diagnostics $5,000 $- $- Total license fee per core $75,500 $- $- Total license fee per server $2,416,000 $- $- Operation expenditure Annual support/maintenance $531,520 $27,600 $- Server Instances $- $- $40,646 I/O Rate (1B I/O)
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.