Transcription of Software Architecture Patterns - O'Reilly Media
{{id}} {{{paragraph}}}
REPORTS oftware Architecture PatternsMark RichardsMark RichardsSoftware ArchitecturePatternsUnderstanding Common ArchitecturePatterns and When to Use Them978-1-491-92424-2[LSI] Software Architecture Patternsby Mark RichardsCopyright 2015 O Reilly Media , Inc. All rights in the United States of by O Reilly Media , Inc., 1005 Gravenstein Highway North, Sebastopol, Reilly books may be purchased for educational, business, or sales promotional editions are also available for most titles ( ). For moreinformation, contact our corporate/institutional sales department: 800-998-9938 Heather SchererProduction Editor: Colleen LobnerCopyeditor: Amanda KerseyInterior Designer: David FutatoCover Designer: Ellie VolckhausenIllustrator: Rebecca DemarestFebruary 2015: First EditionRevision History for the First Edition2015-02-24: First Release2015-03-30: Second Release2017-06-22: Third Release The O Reilly logo is a registered trademark of O Reilly Media , Inc. Software Architec ture Patterns , the cover image, and related trade dress are trademarks of O ReillyMedia, the publisher and the author have used good faith efforts to ensure that theinformation and instructions contained in this work are accurate, the publisher andthe author disclaim all responsibility for errors or omissions, including without limi tation responsibility for damages resulting from the use of or reliance on this of the information and instructions contai
solved by creating open layers within the architecture. As illustrated in Figure 1-3, the services layer in this case is marked as open, meaning requests are allowed to bypass this open layer and go directly to the layer below it. In the following example, since the services layer is open, the business layer is now allowed to bypass it
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document:
{{id}} {{{paragraph}}}