Posts

Showing posts with the label Software Architecture

Implementing a tactical system

Anyone who worked in large scale implementation would have come across the issue of implementing a tactical system, which is either hard or never replaced. Below are my views of the potential reason. Most of the below points are apparent but often overlooked. What is a tactical system? A solution to temporarily bridge a significant technical or a business gap. Characteristics of a tactical system. 1. Cheaper to implement. 2. Easy to train. 3. Quicker to roll out. 4. The life span of a tactical system is not higher than six months. 5. Has less business benefit compared to an end state system. When a tactical system becomes an end-state system? 1. When it delivers beyond MVP.  2. When it is more flexible compared to a strategic system. 3. When its life span is more than a year. 4. When its user base is high. 5. When there is no road map and a secured business case and funding for a strategic system. 6. When deeply embedded within the business pro...

Service oriented architecture

Image
What is Service oriented architecture? Service oriented architecture, commonly called as SOA is a collection of services. Each and every service is used to achieve a functionality for example processing online credit card. These services are exposed over a network, to be used by the consumers. Any authorized consumers can consume the service. Service provider and the service consumer use a common protocol to communicate with each other one such protocol is SOAP. Above diagram shows a simple Service oriented architecture, with one service provider and one service consumer. Service consumer sends a service request to the service provider over a network accessible by both (example internet). On receiving the service request the service provider processes the request and sends the result back to the service consumer. Sometimes there are scenarios in which Service providers communicate...