Process driven messaging service: Difference between revisions

Revision as of 17:05, 9 July 2016

Revision as of 03:03, 29 January 2018

Line 37:

PDMS is based upon [[Event-driven architecture|Event-Driven Architecture]] whereas the [[architectural pattern]] may be applied by the design and implementation of applications and systems which transmit events among [[Architectural pattern|loosely coupled software]] components and [[Service (systems architecture)|services]]. Unlike traditional information systems which work by issuing requests and waiting for responses, event-driven systems are designed to process events as they occur, allowing the system to observe, react dynamically, and issue personalized data depending on the recipient and situation.<ref name="Event Driven Architecture">{{cite book|title=Event Processing in Action 1st|date=September 2007|publisher=Manning Publications Co|___location=Greenwich, CT, USA|isbn=1935182218|author=Opher Etzion, Peter Niblett}}</ref>

== Applicable Areasareas ==

Areas where PDMS can be used are System to System, [[Short Message Service#Application-to-Person (A2P) SMS|A2P]] with the difference that other message types can be included in the PDMS, Application to Application, System to Person, [[Machine-to-Machine|M2M]] and all kinds of messages/data calls between systems, applications and/or people based upon [[event-driven process chain|event-driven processes]].