Hi Anthony We are still new to Geode and yet using it in production.
But I think it would be great to discuss or answer these questions: - Are you putting any effort on database browsing tools for Geode? For example I know there was effort here: https://calcite.apache.org/docs/geode_adapter.html and when I tried it worked sort of from the command line but the support via DbVisualizer didn't work. I have used MongoDB and it helps to have a browser to view data. In Geode this is difficult as you don't have a standard format like JSON and devs can write their own serializers/deserializers which makes data browsing difficult. Also Pulse on a 44gig db is super slow to browse data and not easy to view data if you have a custom serializers/deserializers. I just think Geode has solid features. But lacking in the easy viewing of data. I feel weird asking this as this was the old question with Object Databases as well ;). I like Geode better than MongoDB but they do have some nice tools. - Discuss the status of https://cwiki.apache.org/confluence/display/GEODE/Simple+JDBC+Connector. Would be nice to synch data to a relational database as business always ask for this for some reporting tools to run. - Discuss allowing transactions to span across multiple nodes via a setting. I think by default Geode doesn't allow this and I can understand why. "For partitioned regions, you must colocate all your transactional data in a single member. See " But if you don't have a nicely sharded domain yet you cannot run transactions. I think MongoDB now allows distributed transactions across their shards. This might be slow or not as great if you had the data colocated. Maybe you don't want to support transactions in this way. Which is fair. But you do have a lot of support already and nice flags to turn stuff on and off. - https://codeburst.io/fawn-transactions-in-mongodb-988d8646e564 - https://docs.mongodb.com/manual/core/transactions/ Here they provide a nice warning: MPORTANT In most cases, multi-document transaction incurs a greater performance cost over single document writes, and the availability of multi-document transaction should not be a replacement for effective schema design. - https://techcrunch.com/2018/02/15/mongodb-gets-support-for-multi-document-acid-transactions/ Hope I am not off track. Wish I could attend but hope it is a huge success! Kindly Pieter van Zyl On Thu, Aug 16, 2018 at 10:10 PM, Anthony Baker <[email protected]> wrote: > Hey everyone! > > I'm moderating a panel of Apache Geode committers [1] at the > SpringOnePlatform conference [2] next month. This is a great chance > to talk directly to committers who have a long history with the code > base and understand it deeply. I think it is going to be a really fun > session but I need YOUR help to make it even better. What questions > would you like the panel to answer? > > For example: > - When would I want to use Geode? > - What advice do you have for someone building a Geode application? > - How does Geode maintain availability and consistency? > - How can I contribute improvements to the Geode project? > - What is one thing you wish everyone knew about Geode? > - If Geode was a superhero, which one would it be (and what is its > superpower)? > > These are some examples but I'd love to hear your ideas. Please > respond on this thread or send me email directly (or via @metatype). > I hope to see you there! If you can't attend live, the sessions will > be posted online afterwards. > > Thanks, > Anthony > > p.s. If you haven't registered yet, you can use this code > (Attendee_Speaker_100) to get a registration discount. > > [1] https://springoneplatform.io/2018/sessions/questions- > answers-and-oddly-specific-opinions-with-apache-geode-committers > [2] https://springoneplatform.io/geode >
