Weekly Community Meeting Notes – Friday, May 29 at 4 PM PDT

[Bismanpal Singh Anand <bi...@gmail.com>]

Hi everyone,
Here’s a brief summary of our weekly *Apache ResilientDB (Incubating)*
community
meeting held on *May 29, 2026* for those who couldn’t attend:

Bismanpal reported on website updates including fixing outdated links and
adding team member profiles, while also reviewing PRs for multiple team
members' blogs and projects. The team discussed Roshni's mobile project
demo which showed successful connection to ResilientDB using GraphQL APIs,
with plans to create an issue and potentially fork the repository for
better integration. Josh shared progress on Raft implementation showing
significant improvements in throughput compared to PBFT.
*Action Items:*

   - Ensure Paiman's PR for ResidentDB is finalized (all license issues and
   build issues fixed) and deploy it to development branch, then to master
   after successful testing.
   - Run Raft implementation experiments to replicate Hot Stuff 1 results
   (as per the Hot Stuff 1 paper and website graphs), and prepare to add Raft
   results to it.

Release Status and Website Updates
The team discussed the status of a release. Bismanpal provided updates on
website maintenance, including fixing outdated links, and reported ongoing
work with Paiman's PR for the ResidentDB repo which needs license fixes
before merging. The team also discussed the status of various blog posts
that have been reviewed and merged, including contributions from Paiman,
Harish, and Josh.

App Wallet Project
Bismanpal discussed a meeting with Roshni about her App Wallet project,
which demonstrated working connection to the block backend for ResilientDB
using GraphQL APIs. Mohammad suggested creating an issue in ResilientDB to
track the project's progress and recommended that Roshni work in a separate
repository to make future merging easier.

Composite Key Updates
The team discussed the status of the composite key implementation, where
Junchao reviewed the code and identified compile issues that need fixing.
Bisman was asked to follow up with the developer to bring the PR to closure
after Junchao's review.

Raft Performance Implementation Progress
Josh provided an update on the Raft implementation, mentioning that he had
fixed throughput issues related to I/O and multithreading, and had worked
on pipelining log entries. Josh reported progress on implementing crash
tolerance for replicas, categorizing them into replicate or probe states to
avoid overwhelming failed nodes with unnecessary requests. He shared
performance metrics showing Raft achieved 270,000 throughput with 0.0008
latency compared to PBFT's 43,000 throughput and 0.08 latency using 5 nodes
on Cloud Lab.

-
Best,

*Bismanpal Singh Anand*PPMC, ResilientDB (Incubating)