Downloaded 57 times
![Identifying Super-Patterns
• Build platform with super-patterns
Super-pattern. [noun] Pattern from which all others in
same category can be derived, by:
1. Adding constraints and/or
2. Composing it with itself
• Build applications (1) based on derived patterns
or (2) isolate logic from pattern altogether
– For programming ease of use
– For correctness
– For manageability
© 2012 RTI 12](https://image.slidesharecdn.com/patternsofdatadistribution-120423164357-phpapp01/75/Patterns-of-Data-Distribution-11-2048.jpg)
Uploaded byRick Warren
Patterns of Data Distribution
This document discusses patterns of data distribution that are commonly used when building distributed systems and applications. It identifies three main patterns: publish-subscribe, point-to-point, and request-reply. The document argues that middleware platforms typically implement these patterns in a rigid way, whereas a better approach is for platforms to be built using fundamental "super-patterns" that can be constrained or composed to derive the common patterns. This allows platforms to be more flexible and performant while still providing familiar patterns to application developers. The document also discusses challenges for platform builders in areas like system architecture, performance, and application interfaces.
More Related Content
![New Drug Application [NDA]](https://cdn.slidesharecdn.com/ss_thumbnails/newdrugapplicationnda-160619063242-thumbnail.jpg?width=640&height=640&fit=bounds)
![ocuserts [ocular inserts]](https://cdn.slidesharecdn.com/ss_thumbnails/tarunppt-copy2-210523054503-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Patterns of Data Distribution
![[FREE PDF sample] Enterprise Integration Patterns Designing Building and Depl...](https://cdn.slidesharecdn.com/ss_thumbnails/71522-241112050632-704b8f5a-thumbnail.jpg?width=640&height=640&fit=bounds)
Patterns of Data Distribution
- 1. Your systems. Workingas one. Patterns of Data Distribution Workshop on Real-Time, Embedded and Rick Warren Enterprise-Scale Time-Critical Systems Dir. Tech. Solutions, Principal Engineer April 2012; Paris [email protected]
- 2. System Lifecycle …Because we still 1. Build cool small app. think like this 2. Needs more capability! Scale out. …But mostly we 3. Interop., maintenance, and screw up here reuse are hard! Refactor out platform. Repeat until you’re ready to… Mature 4. Build new capabilities atop ecosystems are unmodified platform. already here © 2012 RTI 2
- 3. Think Different. Building Applications Building Platforms • Designed as a unit • Connect independently • Managed as a unit developed applications • …To serve a single business • Focus on interoperability and function heterogeneous versioning • …To solve business function(s) different than its constituent parts We will discuss just one aspect here: Mostly from this Patterns of data distribution perspective © 2012 RTI 3
- 4. Distribution Pattern Overview Publish- Point to Request- Subscribe Point Reply * See Hohpe and Woolf, 5 “Enterprise Integration Patterns”, www.eaipatterns.com
- 5. Pattern: Publish-Subscribe Subscriber Subscriber Publisher Topic Message … Subscriber Scenario for App Use Variation Points • Distributing data • Topic structure: flat vs. hierarchical • Subscriber quorum © 2012 RTI 6
- 6. Pattern: Point toPoint Receiver Receiver Sender Queue Message … Receiver Scenario for App Use Variation Points • Distributing computation • Allowed current consumers • Message visibility to consumers of other roles © 2012 RTI 7
- 7. Pattern: Request-Reply Request “Method”? Channel Message Requester Replier Reply Channel Message Scenarios for App Use Variation Points • Sending / acknowledging • # Repliers commands • # Replies per Replier – Called “Command Pattern” • Pulling data (often large) • Synch. vs. asych. • RMI vs. messaging API © 2012 RTI 8
- 8. Middleware Comparison Middleware standardshard code specific patterns. • JMS • HTTP – Publish-Subscribe – Request-Reply (data-centric) • TopicPublisher • Messaging: GET, PUT, POST, • TopicSubscriber DELETE, etc. – Point to Point • CORBA • QueueProducer – Request-Reply (imperative) • QueueConsumer/QueueBrow • RMI, user-defined ser – Point to Point (partial) – Request-Reply (idiomatic) • oneway call to predefined • Based on JMSReplyTo header recipient • DDS – Publish-Subscribe • DataWriter • DataReader © 2012 RTI 9
- 9. Combining Patterns Subscriber Recording Subscriber Monitoring Receiver Receiver Queue Sender Topic Request Channel … Publisher Reply Channel Receiver Requester Replier Topic © 2012 RTI 10
- 10. Combining Patterns Subscriber Insight: Recording • Data is Platforms are Subscriber concerned with this Monitoring global • Patterns Receiver Applications are are local concerned with this Receiver Queue Sender Topic Request Channel … Publisher Reply Channel Receiver Requester Replier Topic © 2012 RTI 11
- 11. Identifying Super-Patterns • Buildplatform with super-patterns Super-pattern. [noun] Pattern from which all others in same category can be derived, by: 1. Adding constraints and/or 2. Composing it with itself • Build applications (1) based on derived patterns or (2) isolate logic from pattern altogether – For programming ease of use – For correctness – For manageability © 2012 RTI 12
- 12. This is theSuper-Pattern • Someone produces some data • Some other(s) observe(s) that data Subscriber Subscriber Publisher Topic Message … Subscriber • Apply platform concerns here – Interoperability – Connectivity – Governance © 2012 RTI 13
- 13. We Can ConstrainIt • Apply delivery policy to limit observation based on Receiver role(s) • Encompasses concurrent consumers and multiple roles Receiver Receiver Sender Queue Message … Receiver • Apply application concerns here – Portability – Ease of (business logic) development © 2012 RTI 14
- 14. We Can ComposeIt • Request, Reply Channels each instance of super-pattern • Encompasses multiple Repliers, multiple Replies, additional producers and consumers Request Channel Message Requester Replier Reply Channel Message • Apply application concerns here – Portability – Ease of (business logic) development © 2012 RTI 15
- 15. Challenges for PlatformBuilders Challenge: System Architecture Architects and developers need training and support • Many platform developers were trained as application developers, not systems engineers • Many people think imperatively: “Do this, then do this, …” © 2012 RTI 16
- 16. Challenges for PlatformBuilders Challenge: Performance • General, reconfigurable implementation typically has overhead vs. highly specialized one • …But beware premature optimization © 2012 RTI 17
- 17. Challenges for PlatformBuilders Challenge: Application Interface Option #1: Provide Derived Option #2: Separate Apps from Patterns? Patterns? • Application developers will • Example (JMS MDB): demand many of them! void onMessage( – Pub-Sub, Point to Message event) { Point, Request-Reply // biz logic… – Others? } • Pro: Perceived as • Pro: Elegant; one thing to familiar, easy to use learn; easy to reconfigure • Con: Many ways to do same • Con: Requires inversion of thing; less reconfigurable; control => requires heavy work for vendors container, retraining © 2012 RTI 18
- 18. Summary • From appprogramming POV, certain problems feel natural to solve with certain patterns • From platform or systems POV, handling each pattern in independent ad hoc ways results in brittle, poorly performing systems • Solution: Build platform in terms of fundamental super-patterns 1. Option: Derive high-level patterns from super- patterns; expose those to apps 2. Option: Invert control; enforce patterns within platform, not apps; make app developers cope © 2012 RTI 19
- 19. P.S. Exercise forthe Reader Find the Super-Patterns: • Topology • Invocation – Peer-to-Peer – Event-Driven – Hub and Spoke – Imperative – etc. – etc. © 2012 RTI 20
Editor's Notes
- #2 This talk is not specific to any one middleware technology.
- #7 Each message delivered to all available consumers.
- #8 Each message is delivered to only a subset (usually one) of a set of consumers that all share a certain role.
- #9 Each message is delivered to one recipient, which sends a related message back to the original sender.
- #11 Sender has a job to do, so posts a job to a queue: Point-to-Point pattern. A receiver picks it up.The one that processes the job posts a response back; there’s a layered Request-Reply Pattern.Other consumers use different patterns: consider monitoring and recording scenarios.The queues are really topics! Does the original sender know that?
- #12 If you remember nothing else from this talk, remember this slide.You could substitute “portability” for “applications” and/or “interoperability” for “platforms”.