This website uses cookies to ensure you get the best experience.
Learn more.
A function writes data only to its local temporary filesystem and expects another invocation to read it later. What is the design flaw?
Published
- All function invocations necessarily share one permanent disk.
- Increasing log verbosity makes local files durable.
- Function names must match temporary filenames.
- Durable cross-invocation state should use an appropriate persistent service.
Comments — 0
Sign in to comment