{"repo":"jchejarla/spring-batch-db-cluster-partitioning","free":true,"listed":false,"github":"https://github.com/jchejarla/spring-batch-db-cluster-partitioning","clone":"git clone https://github.com/jchejarla/spring-batch-db-cluster-partitioning.git","description":"Spring Batch distributed partitioning using a shared database for coordination and failover","language":"Java","stars":14,"topics":["batch-processing","clustering","database","distributed-systems","failover","high-availability","java","partitioning","spring-batch","spring-boot"],"license":"Apache-2.0","category":"databases-storage","readme_excerpt":"Spring Batch Database Cluster Partitioning Database-coordinated distributed partitioning for Spring Batch. Run partitioned batch jobs across many JVM nodes — scalable and fault-tolerant — with all cluster coordination handled through the relational database you already operate. No message broker, no coordination service, nothing extra to deploy or monitor. 📖 Documentation site → --- Why Spring Batch's standard remote partitioning dispatches partitions over a message broker as a fire-and-forget channel: the master can't tell how many workers are alive before it partitions, and once a partition is dispatched there's no built-in way to detect a worker that died after receiving it. Those are coordination concerns a broker was never meant to address. This extension adds that missing layer — proactive node awareness, transactional partition lifecycle tracking, and heartbeat-based failover — using the database Spring Batch already requires. You gain the coordination the broker never provided, and you drop the broker. (Spring Batch's own remote partitioning already needs a shared database for the job repository; this reuses it and removes the broker on top — see the FAQ.) Key features Decentralized master — the node that launches a job is the master for that execution; no elected coordinator to run or lose. Capacity-aware partitioning — the master queries the live node count before splitting and passes it to your partitioner, so work is sized to the cluster that actually exists. Plu","default_branch":null,"files":null,"tree":[],"storefront":"/r/jchejarla","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/jchejarla/spring-batch-db-cluster-partitioning/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}