EMC has killed its Centera XAM development, virtually signalling the end of the road for this object storage access protocol. XAM, aka the eXtensible Access Method, is an SNIA-developed and maintained initiative that was intended to become a standard way to access fixed-content storage devices, such as EMC's Centera and Atmos. …
typical for EMC
Bet on a horse, cripple it and then shoot it.
So.... does that mean there is an open market here for some kind of middleware, i.e. a daemon or library that accepts... well, XAM, or something, on one end, and the dozen proprietary methods on the other? Or, do the people that buys these things become so phobic of changing vendors that this is not an issue?
I could see XAM not catching on if a) It was a "standard' that other vendors were *expected* to support, but in actuality was only supported by EMC. b) If XAM was pants (either bad by design -- i.e. hard to use, not feature complete compared to native libs, etc.... or, bad in terms of the implementation being slow and/or buggy.) But otherwise, I know for sure I'd rather code so my app is not tied to one vendor's product if feasible.
- +Comment Trips to Mars may be OFF: The SUN has changed in a way we've NEVER SEEN
- OnePlus One cut-price Android phone on sale to all... for 1 HOUR
- MARS NEEDS WOMEN, claims NASA pseudo 'naut: They eat less
- UNIX greybeards threaten Debian fork over systemd plan
- Back to the ... drawing board: 'Hoverboard' will disappoint Marty McFly wannabes