On Sat, Feb 17, 2018 at 3:09 PM, Romain Manni-Bucau <[email protected]> wrote: > > If you give an example of a high-level need (e.g. "I'm trying to write an > IO for system $x and it requires the following initialization and the > following cleanup logic and the following processing in between") I'll be > better able to help you. > > > Take a simple example of a transform requiring a connection. Using bundles > is a perf killer since size is not controlled. Using teardown doesnt allow > you to release the connection since it is a best effort thing. Not > releasing the connection makes you pay a lot - aws ;) - or prevents you to > launch other processings - concurrent limit. >
For this example @Teardown is an exact fit. If things die so badly that @Teardown is not called then nothing else can be called to close the connection either. What AWS service are you thinking of that stays open for a long time when everything at the other end has died? Kenn
