1 / 0

Architecture-Driven Context-Specific Middleware Specializations for Distributed Real-time and Embedded Systems Akshay Da

Architecture-Driven Context-Specific Middleware Specializations for Distributed Real-time and Embedded Systems Akshay Dabholkar, and Aniruddha Gokhale Dept . of EECS, Vanderbilt University, Nashville, TN, USA {aky, gokhale}@dre.vanderbilt.edu Work supported by NSF CAREER Award # 0845789.

delano
Download Presentation

Architecture-Driven Context-Specific Middleware Specializations for Distributed Real-time and Embedded Systems Akshay Da

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Architecture-Driven Context-Specific Middleware Specializations for Distributed Real-time and Embedded Systems Akshay Dabholkar, and Aniruddha Gokhale Dept. of EECS, Vanderbilt University, Nashville, TN, USA {aky, gokhale}@dre.vanderbilt.edu Work supported by NSF CAREER Award # 0845789
  2. 1. Motivation: Why Specialize Middleware? General-purpose middleware offer a number of features to support a wide range of applications Middleware features are organized into cooperating layers But the rigid layered processing adds time and space overhead In general, the application & middleware design forces are antagonistic
  3. 2. What is Middleware Specialization? Middleware Feature Layers Prune away unnecessary features based on domain requirements , desired configurations, platform constraints and physics of operating environment. Optimize performance by moving away from the rigid layer processing Incorporate domain-specific semantics through AOP and FOSD techniques Correct-by-construction of specialized middleware stacks RTCORBAFeatures Memory Resources Processor Resources Communication Resources Key goal: Automation of all stages of specializations
  4. 3. Impediments to Middleware Specialization Number of How To?s Identification of execution context Inference of the specialization opportunities from the context Selection of specialization points and paths in middleware Realization of the specializations Automate all of the above
  5. 4. GAMMA Approach to Middleware Specialization Generators and Aspects for Manipulation of Middleware Architectures GAMMA leverages existing system modeling and specialization engines based on FOP/AOP, D&C and runtime weavers Specializations need to be validated to ensure that they meet the end-to-end requirements of the application. GAMMA allows pluggability of language-specific transformations as well as middleware platforms
  6. 5. Preliminary Results: FORMS Feature-Oriented Reverse Engineering for Middleware Specialization Focus on Vertical Decomposition of middleware in terms of Domain Concerns Savings in Static Footprint  41% reduction Reduction in source files  64% reduction Feature Reduction  60-76% reduction
  7. 6. Work In Progress: Deducing Specialization Opportunities from the Context Periodic Timer: Sends same data repeatedly Single method interfaces: Sends same operation on wire Mapping Ahead of Time (AOT) System Properties to Specialization Directives Collocation  Remove networking code Periodicity  Pre-create marshaled Request Single Interface Operations  Specialize Request Path Reactor/Protocols  Plug in right reactors (remove indirections) Investigating use of Model Driven Engineering Tools Profiling and Automated Feedback

  8. EXTRAS

  9. 5. Selection of Specialization Points & Path Middleware Developer can define the specialization points through annotating their design models as well as source code A collection of related specialization points forms the Specialized Path
  10. 6. Instrumenting the Specializations Automate creation of specialization rules using design knowledge and specialization paths Automate selection of specialization rules once context is determined
More Related