Did you and how did that go?

“Information Immortality”
Create an Information entity/object once and it lives forever in the global namespace. It may not be online, nearline, offline or even in the distant archives but its name lives. The SOA system for this global namespace has to search for the Information and deliver the result to the requestor. Hopefully this will be the Information or a Context cluster for “fuzzy” requests. A human may remove the name of no longer existing Information from the global namespace but any request for that Information returns the removal Information. Immortality!

To do this the SOA system must scale resources as determined by the SLA for the Information requested. If the Information can no longer be found anywhere, that fact is noted for future reference and that Information is returned to the requestor. Takes quite a system to do this.

An obvious issue is the searching of the global namespace every time for every request. Then there are Security issues. Do you have the authority to access that Information?

I made the post here about “pace layering” as a new way to look at Information.
To me, it appears that Google has one pace and one layer in their search engine.
I wonder if this is true?
Amazon appear to have a multi-layered approach. SOA lends great strength to the multi-layered approach through the aggregation and then the integration of those resources for task completion.

Think “stateless”. I have loved “stateless” since I first heard about it. Everything on the fly. Shoot from the hip. Space age stuff.

We really should give credit to the wonderful engineers who have designed and built Storage devices in all media over the years. This Unit of Technology precision is what gives us the freedom to go “stateless” and “shoot from the hip” with accuracy. I can recall spending more time on the “error correction” system in a Storage device to make sure it was written correctly and “in the place it said it was written” than retrieving and using that Information.