nicholasveloso commented on issue #2111: URL: https://github.com/apache/age/issues/2111#issuecomment-2645861568
Sincerely, I hope the problems will be sorted out sooner rather than later, and that the project continues. At our startup we had reached an agreement to use AGE as the graph database of choice to use for our products, just a couple days before it was posted that the core developer meant team had been dismissed and the project would have no active development for the foreseeable future. Since then we kind of froze our work towards graph database implementations, because without any certainty fo the Apache AGE project would continue and after analyzing the other solutions, we concluded that ifwe go for something like Neo4j or AWS Neptune, which have very steep costs, our company would not be able shoulder th costs without a good revenue stream for it. We are still probing if our current clients would be willing to agree to an increase of price on their current contracts for the additional capabilities. Specialy since thr need for Graph DBs was identified based on their suggestions and requests for new functionalities of current products. If they aren't willing absorb the cost, it would be hard to get it going with a non open source solution, so AGE was practically our only choice, but if the amount of time without active development goes on, it would be ever harder to use AGE as time passes, as the landscape of solutions in need for Graph DBs widens and get ever more sofisticated. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
