Webservice or Toll-Bridge?
Note: This blog does not contain any technical complexity.
The most expected thing during any project is any Un-expected requirement shared at the last stage of the project. Somewhat similar happened in my project.
We got a requirement to receive any traffic diverted to our site from one of the sub-site developed by a third-party. We proposed a solution : Implement Web Service.
Here comes the tricky part,we as a technical guy knows the backdrop of webservice and all the technical intricacies involved but how to make all the non-technical guys understand the problem and solution.
Lets try to associate our scenario with some real life object, we can consider our base site as one road and sub-site as another road. These two roads are not connected in any way. We can assume the vehicles running on the road as internet traffic to each site. Now our job is to divert traffic from sub-site road to our base site road. How that can be possible?
Simply think and you will know that you have to build a bridge/flyover to connect these roads.So this bridge, we call ,as our webservice. A webservice is a bridge which is used to connect these roads to facilitate traffic.
Now, the bridge can be one way or two-way which in technical terms can be mentioned as simplex or duplex communication. It’s a common practice to identify what traffic is coming from one site to another so to monitor this part, we just have to place ‘toll’ at each end and just start tracking. Phew! I know this article only provides non-technical explanation for few items, so for all other items which are missed will be covered in other articles.
Prior to this incident, it was a regular feedback from non-tech guys that they require some common language explanation.It might be a general problem of all non-tech guys so please see one of my attempt to help those guys.if you think this article helped you somewhat, please provide your questions for which you require a non-technical explanation.