Part of planning for the next generation technical architecture for arXiv was evaluating technologies that could be adopted or adapted for arXiv.   At this point, we looked at technologies that were developed with similar motivation to what arXiv-NG needs.  The evaluation included open source frameworks, services that could fulfill part of arXiv's needs, and commercial solutions.   We met with technical leads of each candidate technology and looked at code and documentation when it was in an open repository.   The arXiv-NG development team created a "rubric" (see below) that covered the many aspects of what a technology would require to meet the needs of arXiv-NG going forward.    In recognition that any one technology would not be able to solve all of arXiv's needs, we set a priority for each item on the rubric.   At the end of the evaluation period, we narrowed our focus to two top candidates (i.e., open source approaches that were modular and evolvable), at which time we did testing and proof of concepts to essentially "kick the tires" for  essentials for arXiv.

arXiv-NG Technical Evaluation Rubric v2

...