[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [soa-rm] Microservices re-use?
Doing a bit more reading, a consideration could be whether it is easier to move the data to the processing or the processing to the data. In our work on describing SOA, we assumed crossing ownership boundaries was a critical part of the paradigm: the consumer used services where they were offered rather than having a private copy. Part of the rationale was that private copies held by consumers (who were effectively also forcing themselves to be providers) often meant enumerable modified copies that became one-of-a-kind albatrosses to maintain. Under the SOA paradigm, the consumer and provider interacted under agreed upon terms (the execution context) with neither under the other’s control. (What control really existed before is another topic for discussion.) But with VMs and containers, we should be able to manage exact copies, including making sure the copies have a known, controlled configuration. So now if I generate terabytes of data a day, it may be more efficient to bring the processing to the data rather than the data to the processing. My configuration management makes sure the “manifest” for the new VM/container is up to date at all needed locations, and things like applications needing to be deployed are already pre-staged to any place that may need that application. What does this say about deploying on-premise infrastructure vs. cloud vs. what combination? What SOA principles are still useful to guide us? The house of the SOA paradigm may still basically function but it may need to have the kitchen remodeled. Ken ------------------------------------------------------------------------------
Dr. Kenneth Laskey MITRE Corporation, M/S F510 phone: 703-983-7934 7515 Colshire Drive fax: 703-983-1379 McLean VA 22102-7508
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]