What's interesting to me is that if you read the summary (http://codecapsule.com/2014/02/12/coding-for-ssds-part-6-a-s...), most of the recommendations are exactly the same as when programming against a traditional spinning-oxide hard drive: read and write entire blocks if you can, combine block writes, &c.
It's nice to know that all that work on high-performance IO in databases doesn't need to be thrown away just yet.
It's nice to know that all that work on high-performance IO in databases doesn't need to be thrown away just yet.