Skip to main content

Service Modeling Realization

When we enable a platform / a set of capabilities for consumption through the enablement of custom development, some of the points to be considered for wider reach .

Wider reach means to provide flexibility such as facilitating development on heterogeneous platform through supporting interoperability, various communication protocols and data encoding formats.

  • Data encoding format – XML, JSON
  • Protocol – Http , Tcp-ip
  • Type of communication - Synchronous / Asynchronous communication
  • Consumption  type – Proxy objects, RESTful communication

In addition to this, other key infrastructure & administration related factors to be considered are:

  • Reliability – Data submitted is not lost. The infrastructure behind the service model should be reliable without losing any submitted messages that is submitted

  • Security  - Integration with the consumer’s security infrastructure

  • Performance – Of course, first & fire most requirement of any exposed services and will be governed by SLAs

  • Service Metering – very important especially in the “pay per use” model

  • Centralized Dashboard – for the consumers to have insight into logs & exceptions


Frist point in consideration in realizing a service model is to select a platform that has the potential to offer various required capabilities. For example, Windows Communication Foundation from Microsoft provides lots of options to provide flexibility such as :

  • Encoding – Plain text for interoperability, Binary to optimize performance, MTOM for large payloads
  • Channels – one way, Duplex , Request-Response, Streaming
  • WS-*
      • WS-Addressing – extra additions to SOAP headers which makes SOAP free from underlying transport protocol
      • WS-Security,WS-Trust,WS-SecureConversation
      • WS-ReliableMessaging
      • WS-Coordination , WS-AtomicTransaction
      • WS-Policy (for more dynamic features of a service), WS-Metadataexchange

So, for a successful realization of a Service Model, choosing a capable platform is very much important !

Comments

Post a Comment

Popular posts from this blog

Blockchain for a "Secured" AADHAAR

AADHAAR  is gradually becoming the “Most Important” digital identity (like a social security number in US) for the citizens of India. It is considered to be more important than any other identities such as Passport, Driving License, PAN card etc. as it is being recognized as the “Mandatory” proof for the authenticity of an Indian citizen, for all the Govt. as well as private transactions, starting from availing the subsidized residential gas benefits  to operating a trading account or even getting a Passport. Because of this, the secured accessibility & immutability of that digital identity is very critical. The AADHAR card once issued to a citizen should not be subjected to change especially in terms of AADHAAR number, name of the person etc.; Any compromise on AADHAR can lead to problems related to mistaken identity. Storing AADHAAR information in a Blockchain platform is a natural choice , as Blockchain offers "Cryptographically" secured decentralized storage...
4 comments
Read more

Heterogeneous Cloud Integration

Heterogeneous integration is common scenario in the Enterprises where their IT portfolio is based on heterogeneous platforms. Various solution approaches such as message broker, messaging middleware, SOA – service based integration were employed to address heterogeneous integration challenges.   These solution approaches were good when the integration happens on premise, with in the data centers of an Enterprise. Problem here is non-availability of “elasticity”.   With the Enterprises started leveraging cloud platforms extensively for various solution aspects such as elastic computing, storage, it opens new capabilities that can be leveraged for heterogeneous integration. Also, similar to existing on premise scenario, Enterprises are also leveraging multiple cloud platforms to address their business needs. This scenario will pose same integration challenges as those that were faced within on premise datacenters   Within datacenters / on premise, integ...
9 comments
Read more

Follow-up : Evaluating Application Architecture, Quantitatively

Since the publication of my article “Evaluating Application Architecture, Quantitatively” in the 23 rd issue of Microsoft’s The Architecture Journal , Iam receiving lots of questions / encouraging comments / wishes / suggestions. I never expected such a response back from the architects’ community around the world and result is this follow-up. In the article ‘Evaluating Application Architecture, Quantitatively’ which is outlining the framework for evaluating application architectures quantitatively, it is been specified that for a positive response to every question / statement in the questionnaire / checklist '1' will be assigned and '0' will be assigned for a negative response. When a set of questions / checklist is used for an application architecture evaluation, some of them may not be suitable for a particular context. Say for example, you are evaluating an application’s architecture that is meant for intranet only. So, in that context, assume that you are...
Post a Comment
Read more