bookmarks  2

  •  

    The success of Service-Oriented Architecture (SOA) has created the foundation for information and service sharing across application and organizational boundaries. Through the use of SOA, organizations are demanding solutions that provide vast scalability, increased reusability of business services, and greater efficiency of computing resources. More importantly, organizations need agile architectures that can adapt to rapidly changing business requirements without the long development cycles that are typically associated with these efforts. Event-Driven Architecture (EDA) has emerged to provide more sophisticated capabilities that address these dynamic environments. EDA enables business agility by empowering software engineers with complex processing techniques to develop substantial functionality in days or weeks rather than months or years. As a result, EDA is positioned to enhance the business value of SOA. The purpose of this white paper is to describe the approach employed to overcome the significant technical challenges required to design a dynamic grid computing architecture for a US government program. The program required optimization of the overall business process while maximizing scalability to support dramatic increases in throughput. To realize this goal, an architecture was developed to support the dynamic placement and removal of business services across the enterprise.
    15 years ago by @cschie
    (0)
     
     
  •  

    Most BREs today are deployed as “decision services”, and are used in “stateless” transactions to make “decisions” as a part of a business process. A CEP application is instead processing multiple event streams and sources over time, which requires a “stateful” rule service optimized for long running. This is an important distinction, as a stateful BRE for long-running processes needs to have failover support - the ability to cache its working memory for application restarting or distribution. And of course long-running processes need to be very particular over issues like memory handling - no memory leaks allowed!
    16 years ago by @cschie
    (0)
     
     
  • ⟨⟨
  • 1
  • ⟩⟩

publications  

    No matching posts.
  • ⟨⟨
  • ⟩⟩