Coadunation is a Java based daemon server. It enables developers to quickly and easily develop daemons, web applications, distributed applications, manage distributed services etc. It provides, SSO (Single Sign On), SOA (Service Oriented Architecture), Web Services, RMI, Containers, Message Services and much more.
The main characteristic to be aware of in these tools is that BE is primarily rule-based (using an embedded rule engine), whereas BW and iProcess are orchestration / flow engines. In BE we can use a state diagram to indicate a sequence of states which may define what process / rules apply, but this is really just another way of specifying a particular type of rules (i.e. state transition rules).
The main advantages to specifying behavior as declarative rules are:
Handling complex, event-driven behavior and choreography
Iterative development, rule-by-rule
The main advantages of flow diagrams and BPMN-type models are:
Ease of understanding (especially for simpler process routes)
Process paths are pre-determined and therefore deemed guaranteeable.
In combination these tools provide many of the IT capabilities required in an organization. For example, a business automation task uses BW to consolidate information from multiple existing sources, with human business processes for tasks such as process exceptions managed by iProcess. BE is used to consolidate (complex) events from systems to provide business information, or feed into or drive both BW and iProcess, and also monitors end-to-end system and case performance.
[...] Our approach is to define each term independently of any particular implementation, product, or domain of application. So, for example the term event object has popular meanings as a tuple, a vector, a row etc. These are all realizations of events i
Confusion about Services Based Architectures [SBA, SOA, EDA, ...] has been created by a number of industry elements. Industry critics like Forrester first used the term Services Based Architecture until 2000 when Gartner came up with their own term Services Oriented Architectures (SOA). Forrester was still using the term SBA in 2002. Gartner next created the term Event Driven Architecture and has now come full circle back to SOA 2.0 (supporting both SOA and EDA like the original SBA).
The intention for this project is a very simple API to call different kinds of services (provider/technology). Crispy's aims is to provide a single point of entry for remote invocation for a wide number of transports: eg. RMI, EJB, JAX-RPC or XML-RPC. It works by using properties to configure a service manager, which is then used to invoke the remote API. Crispy is a simple Java codebase with an API that sits between your client code and the services your code must access. It provides a layer of abstraction to decouple client code from access to a service, as well as its location and underlying implementation. The special on this idea is, that these calls are simple Java object calls (remote or local calls are transparent).
K. Kontogiannis, G. Lewis, and D. Smith. Proceedings of the 2nd international workshop on Systems development in SOA environments, page 1--6. New York, NY, USA, ACM, (2008)
R. Kazhamiakin, B. Wetzstein, D. Karastoyanova, M. Pistore, and F. Leymann. Service-Oriented Computing -- Revised Selected Papers of ICSOC/ServiceWave 2009 Workshops, Stockholm, Sweden, November 23-27, 2009, volume 6275 of Lecture Notes in Computer Science, Springer, Berlin--Heidelberg, Germany, (2010)
J. Coutaz, L. Balme, X. Alvaro, G. Calvary, A. Demeure, and J. Sottet. Universal Access in Human-Computer Interaction. Ambient Interaction, volume 4555 of Lecture Notes in Computer Science, Springer Berlin Heidelberg, (2007)
S. Bleul, T. Weise, and K. Geihs. International Journal of Computer Systems Science and Engineering (CSSE), 21 (4):
227--234(July 2006)Special issue on ``Engineering Design and Composition of Service-Oriented Applications''.