It's funny in that it was such a pivotal work looking back at it. It's possible in some filing cabinet at Xerox or elsewhere (from what I gathered in the thread). That said, it may have simply seemed somewhat obvious to many at the time and nobody bothered to hold on to or archive it. I suspect it's true of a lot of now commonplace software design strategies.
> it may have simply seemed somewhat obvious to many at the time and nobody bothered to hold on to or archive it.
I suspect this has been the case for many especially last century, everything was moving so fast and there was so much choice, it really was a free for all with no major players dominating the market place and some people didnt know the significance of what they were doing or building. People then retire or get moved to different projects and the knowledge gets lost.
https://shkspr.mobi/blog/2021/06/where-is-the-original-overv...
I can only find the Oracle reference to Sharding, which might be the same thing or not. https://docs.oracle.com/en/database/oracle/oracle-database/1...
Along with the wikipedia reference. https://en.wikipedia.org/wiki/Shard_(database_architecture)
And a Science Direct reference. https://www.sciencedirect.com/topics/computer-science/shardi...
Along with facebooks reference. https://engineering.fb.com/2020/08/24/production-engineering...
And Wolverhamptons reference to Oracle Sharding. http://ora-srv.wlv.ac.uk/oracle19c_doc/shard/sharding-overvi...
And Amazon's. https://aws.amazon.com/what-is/database-sharding/
So is the original paper a myth or was/is this demonstrating the closed circuit nature of the dissemination of knowledge?
How many different ways do you cut up the data?