architecture - Patterns for non-layered applications -
In the pattern of enterprise application architecture, Martin Fowler writes:
What are the patterns for building parts of non-level applications / applications? Take a statistical modeling engine for a financial institution. There may be a layer for data access, but I hope most codes will be in one layer. Would you still expect to see a four-pattern gang in this kind of layer? How about a domain model? Will you use oops at all, or will it be fully functional?
Specifies pipes and filters as alternate models for bid layers. I can easily imagine such an engine using pipes as a way to break data processing. Do other patterns exist? Are there any common patterns for areas like work schedules, result collection, or distribution of work? What are some options of MapReduce? I think the faller means that focus in focusing on "vertical" de-object in a layered application.
Coupled communication between layers
Another architecture is SOA (Services Oriented), where "horizontal" It is focused on organizing D-UPLD communication. (Can use the implementation model within a component). This is not something new. Other examples of this horizontal pattern are COM / COM +, Korba, workflows, and now "Messaging" or ESB architecture.