ISPyB Collaboration Strategy for Sustainable Software Stack Development
"Explore the ISPyB collaboration strategy aimed at making sustainable decisions to advance the software stack development. Learn about the challenges, existing competition, strategic approaches, and future direction towards microservices development for efficient collaboration. Discover how this strategy benefits the ISPyB project and fosters innovation in a challenging environment."
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
ISPyB Strategy Gianluca Santoni
Our goal Take decisions to move the collaboration forward And make a sustainable software stack
Currently COMPETITION VS ISPyB Synchweb UI UI DATA BASE DATA BASE API API Backend JAVA Backend PHP Lesson learned Duplication of effort No possibility of sharing code Endless unfruitful discussions
Currently COMPETITION ISPyB Synchweb Software Stack compliant with ESRF software policy React Java BioSAXS Tailored to the ESRF Workflows, etc.. Interesting key features DHL API Statistics Nice and clean interface Both are good and have advantages but are too crucial to be changed easily No short term solution BUT
EMBL Approach: they can coexist CHOICE AND ISPyB Synchweb UI UI DATA BASE DATA BASE API API Backend JAVA Backend PHP ispyb.embl-hamburg.de exi.embl-hamburg.de synchweb.embl-hamburg.de Unsustainable short term solution
Synchweb at the ESRF? Missing a lot of features for our side. Will take 1.5 years (full time) of development to implement those. Just to be back were we are now. Not a sustainable solution
Where we need to go COLLABORATION ISPyB Synchweb UI UI API API Backend JAVA PYTHON JS Backend JAVA PYTHON JS DATA BASE ... DATA BASE API API Backend JAVA Backend PHP Offline Data Analysis Sample Definition Microservices Smoothly migration from JAVA and PHP to micro services Technical solution agreed with DLS
Actions (ESRF and ispyb collaboration) Focus the next two years of the collaboration not in ISPyB or Synchweb but in developing the microservices This will make possible to collaborate A good test to see if we can do this together!
Advantages It keeps collaboration alive In a constructive way Makes ISPyB project future-proof Current resources in the collaboration are better used
Our proposed plan Explore the microservice scheme Develop it TOGETHER New Software-centered collaborations (new name?) Decision making: Developers committee + scientific committee Convergence of Users Interfaces in the new collaboration framework
