This summary is the result of work done to migrate S3 catalog away from using Kryo for record serialization because of issues described here: locationtech/geotrellis#1138
We have chosen Apache Avro as the alternative. In parallel ongoing work has motivated a closer look at S3 catalog performance and benchmarking. The main question is: is it possible to use S3 as a datasource in web request-response cycle? Original tests where not encouraging with a representative query taking ~20s to complete.
There has been some understandable confusion from the phrase "Kryo is out!" So it's worth while to go over the different serializations going on in GeoTrellis and Spark: