Saturday, June 30, 2007
Candidate for the EDA
For a long time, I am reading excellent posts on SOA and EDA blog by Jack Van Hoof. EDA reminds me of Telecom domain. This domain is excellent candidate for EDA. Telecom network generates the events. These events are intercepted by application services like Prepaid, Ringback tone, Follow me, VPN etc.
Explaining my point with scenario like execution of Single Service -
Consider scenario where prepaid caller dials a called party number. A event is generated, service capture the calling party number and called party number. Based on called party number it routes the call. Now caller listens the ringing. Called party picks up the phone. Another event is generated. Service captures the events and starts charging. There is voice channel between caller and called party. After sometime, called party hangs the phone call. Another event is generated and service based on this event stops charging and persist the duration of call. In this flow, based on current event and last event result, application service executes the business logic. There is requirement for storing the state of call. This makes scenario little bit complex. Events cann't be consider stateless in real sense.
Execution of Multiple Services
In this case, one approach is to introduce Service Manager and this Service Manager further manages the interactions with several services and their sequencing.
In contrast with Enterprise application, Telecom applications are more chatty i.e. Events are too many and are of very short duration. Due to this, scalability and performance becomes burning issues. Secondly, all these events are in real time. While events are processed, customers are waiting for call to connect, waiting for ring back tone, announcements etc. It makes true testing ground for EDA.
In last, I feel, SOA and EDA could change the landscape of Telecom services. Niche companies could provide services like charging, rating, application services on internet. These services could be consumed by operators instead every one building themselves. Telecom domain is always a front runner at concept level. Hub & Spoke model of Telecom switches was innovated three decades back. This model is foundation for buzzword ESB nowadays.
Explaining my point with scenario like execution of Single Service -
Consider scenario where prepaid caller dials a called party number. A event is generated, service capture the calling party number and called party number. Based on called party number it routes the call. Now caller listens the ringing. Called party picks up the phone. Another event is generated. Service captures the events and starts charging. There is voice channel between caller and called party. After sometime, called party hangs the phone call. Another event is generated and service based on this event stops charging and persist the duration of call. In this flow, based on current event and last event result, application service executes the business logic. There is requirement for storing the state of call. This makes scenario little bit complex. Events cann't be consider stateless in real sense.
Execution of Multiple Services
In this case, one approach is to introduce Service Manager and this Service Manager further manages the interactions with several services and their sequencing.
In contrast with Enterprise application, Telecom applications are more chatty i.e. Events are too many and are of very short duration. Due to this, scalability and performance becomes burning issues. Secondly, all these events are in real time. While events are processed, customers are waiting for call to connect, waiting for ring back tone, announcements etc. It makes true testing ground for EDA.
In last, I feel, SOA and EDA could change the landscape of Telecom services. Niche companies could provide services like charging, rating, application services on internet. These services could be consumed by operators instead every one building themselves. Telecom domain is always a front runner at concept level. Hub & Spoke model of Telecom switches was innovated three decades back. This model is foundation for buzzword ESB nowadays.
Subscribe to:
Post Comments (Atom)
"That man is successful who has lived well, laughed often, and loved much; who has gained the respect of the intelligent men and the love of children; who has filled his niche and accomplished his task; who leaves the world better than he found it, whether by an improved poppy, a perfect poem, or a rescued soul; who never lacked appreciation of earth's beauty or failed to express it; who looked for the best in others and gave the best he had." - Ralph Waldo Emerson
No comments:
Post a Comment