Google Cloud Batch vs Xi-Batch
Google Cloud Batch
cloud.google.comXi-Batch
xisl.comSide by side
| Figure | Google Cloud Batch | Xi-Batch |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | Yes |
| Open source | — | — |
| Web | Yes | — |
| Windows | — | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 2 | 1 |
| Spec score · Job Scheduler Software | 8.7 (#3) | 7.4 (#17) |
| Founded | 1998 | 1986 |
| Headquarters | Mountain View, California | London, United Kingdom |
| Integrations | Google lists Cloud Storage, Pub/Sub, Cloud Logging and Workflows as native Batch integrations. | Jobs can use shell scripts and command processors such as Perl and SQL, and an API makes functionality available programmatically. |
| Support | Batch users can consult community forums and troubleshooting documentation; direct Google Cloud Support for Batch issues requires a paid support package. | Support for customers on a maintenance contract is available by telephone and email, with email treated at the same priority as a call. |
Plans
In their own words
Google Cloud Batch
Google Cloud Batch schedules, queues, and runs batch jobs on Google infrastructure. It obtains resources for jobs, creates or removes them during runtime to match job specifications, and can scale compute resources automatically for parallel work. Jobs run executable scripts or containerized workloads, with tasks arranged sequentially or in parallel. Storage options include persistent disks, local SSDs, Cloud Storage buckets, and network file systems such as Filestore. Integrations identified for a developer workflow include Cloud Storage, Pub/Sub, Cloud Logging, and Workflows. Batch can send job and task state changes through Pub/Sub, with notifications streamable to BigQuery. It supports IAM permissions and VPC Service Controls; Secret Manager can provide sensitive job data. Batch itself has no additional charge, but resources used by jobs are billed, and quotas and limits apply. Each job is restricted to one task group, named group0, and finished jobs are automatically deleted after 60 days unless deleted earlier. It is available through API and web, with cloud deployment.
Xi-Batch
Xi-Batch is a self-hosted scheduler for sequencing and controlling batch work across servers, positioned as an alternative to cron. Scheduling variables coordinate serial or parallel job chains across hosts. Calendar rules account for month ends, weekends, holidays and daylight saving time, while file monitoring can trigger jobs when files are created, deleted or amended. Administrators assign load values and queue ceilings to limit which job combinations start. Interfaces include command-line, full-screen character, Motif, GTK3 and a programmer API. Jobs can use shell scripts and processors such as Perl and SQL. User definitions and permissions control submission and visibility. Queues recover automatically after restart, and aborted jobs can go to operator action or automatic recovery. Xi-Batch supports Linux and Windows; Windows server support uses optional client modules. It is designed for trusted networks or one host, not untrusted exposure.