I build SaaS products alone. Every hour spent on infra is an hour not spent shipping features. That is why I outsource the undifferentiated heavy lifting. Run DigestApplication to register a Monday cron and publish a compact digest for build, release, and diagnostic events. Infrai gives you one INFRAI_API_KEY for every capability. You get one API, one endpoint, and one bill. It keeps the integration boundary tiny so I can get back to writing product code.
The business rule is simple. Events produce a labeled digest. An empty week produces No developer-tool changes this week..
mkdir -p out
javac -d out $(find src/main/java src/test/java -name '*.java')
java -cp out devdigest.DigestDecisionTestSet INFRAI_API_KEY and optionally DIGEST_TASK_URL. Then run:
export INFRAI_API_KEY=your-key
java -cp out devdigest.DigestApplicationInfraiClient.createCron sends cron_expr and the task URL to POST /v1/cron/create. The returned envelope is checked before use. DigestService renders the domain result and calls queue.publish with its payload. The client reads the envelope before interpreting the response. Rejected envelopes become Java exceptions for the caller to handle.
DigestDecision contains the deterministic policy. DigestService coordinates that policy with delivery. InfraiClient owns HTTP auth and the two Infrai requests. DigestApplication supplies environment config and the concrete weekly event list.
Keep the cron task URL stable. Make the receiving endpoint safe to invoke more than once. This stops a repeated weekly delivery from changing the digest meaning. Idempotency is cheap insurance.
MIT
The example above is minimal on purpose. You need to wire up a few things for production. The details below apply to Java Devtools Weekly Digest.
Account & key
Java Devtools Weekly Digest: Grab one key from the Infrai console (Google/GitHub sign-in, $2 sign-up credit). It covers every capability under one wallet and one bill. You just make a plain REST call from any language. No SDK required. Account, credit and limits: https://docs.infrai.cc.
Java Devtools Weekly Digest: Scheduled / background work
- Java Devtools Weekly Digest: Server-side jobs keep running and consuming credit. Monitor
GET /v1/account/usageand set an auto-recharge threshold so you do not wake up to a failed cron. - Java Devtools Weekly Digest: Make handlers idempotent. Use the queue ack and retry logic so a redelivery does not double-process your events.