4 ms·

Tandem started selling their NonStop systems in the mid-70s, so clearly high availability was important. At Basho we worked hard to acknowledge our debt to dis

Tandem started selling their NonStop systems in the mid-70s, so clearly high availability was important. At Basho we worked hard to acknowledge our debt to distributed systems pioneers. Not everyone is ignorant of that history.

notacoward 5y ago
Yup, the Basho folks were/are very good about that. BTW hi, we've quite likely met, though I don't know which Basho alum you are. ;) And yes, even I was a pretty late entrant to the HA game. I never worked on Tandem systems, but I worked with Tandem people at the job I mentioned, after having worked with both Stratus and Sequoia systems previously. Those were all FT rather than HA, but the point remains that work on making systems survive failures through redundancy goes back much further than the OP mentions.
- macintux 5y ago
  Oh, definitely, was trying to add to rather than detract from your point. I was mainly on the periphery at Basho, started as tech evangelist, migrated to engineering to help get 2.0 out the door. John Daily.
bogomipz 5y ago
I always thought Basho was a great company with a great product. I felt like I learned a lot through Basho documentation. I never really understood what happened to the company though as it seemed highly regarded amongst the dev community as well and Riak was always mentioned in the same sentence as the other distributed data stores at that time.
- macintux 5y ago
  Tough market, limited potential customer base for such a specialized tool, some product/release planning issues with Riak 2.0, and ownership structure that didn’t make anything easy at the end (but I’m far from an expert on this topic, especially the last one, just parroting distant memories). Engineering was very talented, and the customer support team was truly top notch. Such a shame, best job I’ve ever had.

4 ms·

Tandem started selling their NonStop systems in the mid-70s, so clearly high availability was important. At Basho we worked hard to acknowledge our debt to dis

by macintux 5y ago

notacoward 5y ago
Yup, the Basho folks were/are very good about that. BTW hi, we've quite likely met, though I don't know which Basho alum you are. ;) And yes, even I was a pretty late entrant to the HA game. I never worked on Tandem systems, but I worked with Tandem people at the job I mentioned, after having worked with both Stratus and Sequoia systems previously. Those were all FT rather than HA, but the point remains that work on making systems survive failures through redundancy goes back much further than the OP mentions.
- macintux 5y ago
  Oh, definitely, was trying to add to rather than detract from your point. I was mainly on the periphery at Basho, started as tech evangelist, migrated to engineering to help get 2.0 out the door. John Daily.
bogomipz 5y ago
I always thought Basho was a great company with a great product. I felt like I learned a lot through Basho documentation. I never really understood what happened to the company though as it seemed highly regarded amongst the dev community as well and Riak was always mentioned in the same sentence as the other distributed data stores at that time.
- macintux 5y ago
  Tough market, limited potential customer base for such a specialized tool, some product/release planning issues with Riak 2.0, and ownership structure that didn’t make anything easy at the end (but I’m far from an expert on this topic, especially the last one, just parroting distant memories). Engineering was very talented, and the customer support team was truly top notch. Such a shame, best job I’ve ever had.