Backend
AtomicFaaS: Offloading Side-Effect Compensation to the Serverless Platform
arXiv cs.DC0 views
arXiv:2611.06601v1 Announce Type: new Abstract: Function-as-a-Service (FaaS) simplifies distributed application development by offloading operational concerns to the platform, but developers remain responsible for recovering from failures. Retries require idempotent functions, which means that developers have to write complex, error-prone code that undoes or skips the already completed operations of a failed function. To address this, we propose AtomicFaaS, a platform extension that provides semantic atomicity for the external side effects of a function invocation, whether the function fails or its instance crashes, without developer-written compensation code. AtomicFaaS intercepts outbound calls and records their effects in a fault-tolerant log, from which the platform compensates leaked effects outside the failed instance. Compared with a manually implemented saga, AtomicFaaS eliminates compensation code and leaves no compensatable effects after any tested failure, while adding ~1 ms per intercepted call. Under load, it lowers the sustainable throughput of CPU-bound functions, while its latency overhead becomes negligible once calls to external services dominate the invocation time.
Source:https://arxiv.org/abs/2611.06601PreviousOptimal Subcubic Byzantine Agreement with Plain PKINextflash-comm: Self-Synchronizing Collective Communication for LLM Decoding
Related posts

Build a Nuxt blog end to end: drafts, live preview, SEO and deploy
0dev.to Vue
The Film Catalogue Behind MovieMatcherAI: 650 Records, the Validation Errors That Document It, and 14 Fields That Are Always Empty
0dev.to JavaScript
Cloud Storage CORS Support for Direct Browser Receipt Uploads (A Go Retention Boundary)
0dev.to Go
5 Ways to Publish Timed Caption Segments with Reconnect Handling in Live Rooms
0dev.to Go

Efficiently Growing Unowned Maps in Go: Avoiding Resizes and Reducing Memory Overhead
0dev.to Go
Syncing 1C and Bitrix24 Without Duplicates: Designing an Idempotent Exchange
0dev.to Database