Guidance for Development and Management of Sustainable Enterprise Information Portals (2018) / Chapter Skim
Currently Skimming:
Pages 38-46
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 38... ...
38 Next Generation EIP: Microservices Architecture Based on industry practice recommendations, sustainable DOT EIPs will need to move away from monolithic and heavily integrated portal applications to more distributed hardware and software portal applications. To remain sustainable, agencies will need to adopt distributed, autonomous processes and governance to manage each portal application.
|
From page 39... ...
Next Generation EIP: Microservices Architecture 39 by highlighting the evolutionary nature of development in the microservices framework, focusing on automating fast, frequent, and well-controlled software changes.7 4.1 Characteristics of Microservices Architecture Microservices architecture is a more granular evolution of SOA. Its goal is to decompose a software application into elementary software components to facilitate agile development and deployment.
|
From page 40... ...
40 Guidance for Development and Management of Sustainable Enterprise Information Portals Figure 4-2. Example of a microservices implementation of a DOT EIP on cloud infrastructure.
|
From page 41... ...
Next Generation EIP: Microservices Architecture 41 4.2 Considerations When Adopting a Microservices Architecture While the microservices architecture pattern brings many advantages, it also greatly increases application complexity. Microservices architecture essentially trades code complexity for operational complexity.
|
From page 42... ...
42 Guidance for Development and Management of Sustainable Enterprise Information Portals Like most enterprises or agencies, DOTs do not typically use cross-functional teams for the development of their EIP application, and they clearly separate (1) development and (2)
|
From page 43... ...
Next Generation EIP: Microservices Architecture 43 4.2.5 Many Languages, Many Options Traditional EIPs, with a monolithic architecture, usually use a single language and tend to have a limited number of technologies implemented across their application to ease integration and testing. Decentralization in microservices architecture allows for application software components (microservices)
|
From page 44... ...
44 Guidance for Development and Management of Sustainable Enterprise Information Portals to stay agile and make changes that do not affect any consumer and locate consumers that will be affected by a required change for deeper planning and discussion. These patterns allow software development teams to define the contract for a service.
|
From page 45... ...
Next Generation EIP: Microservices Architecture 45 implement; therefore, microservices architectures emphasize transactionless coordination between services, with the explicit recognition that consistency may only be eventual consistency and that problems will be dealt with by compensating operations. Managing data inconsistencies in this way is a new challenge for many development teams, but it is one that often matches business practices.
|
From page 46... ...
46 Guidance for Development and Management of Sustainable Enterprise Information Portals of the pipeline. At each stage, automated testing is performed before allowing the software to be promoted to the next stage.
|
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.