News for hackers. Stuff that matters.
Re:How we designed Dropbox’s ATF – an async task framework by mfateev on Wednesday November 11, 2020 @07:02PM (#25064551)
Did you click on temporal.io?

It is hard to describe as it is a new way to build distributed applications that doesn't have a commonly agreed name yet.

Re:How we designed Dropbox’s ATF – an async task framework by dragonwriter on Thursday November 12, 2020 @01:25AM (#25067053)
> It is hard to describe as it is a new way to build distributed applications that doesn't have a commonly agreed name yet.

Seems to be a fairly straightforward, minimal (which can be good; that's not a criticism) workflow engine.

Re:How we designed Dropbox’s ATF – an async task framework by tsurkoprt on Thursday November 12, 2020 @12:13AM (#25066700)
new ? really ? this has been around since 1995
Re:How we designed Dropbox’s ATF – an async task framework by mfateev on Thursday November 12, 2020 @01:16AM (#25067017)
Great, show me a single product (besides AWS SWF and Azure durable Task Framework) that has the programming model of Temporal. For example, which product allows to write production code like this that survives any process failures:

  public void execute(String customerId) {
    activities.sendWelcomeEmail(customerId);
    try {
      boolean trialPeriod = true;
      while (true) {
        Workflow.sleep(Duration.ofDays(30));
        activities.chargeMonthlyFee(customerId);
        if (trialPeriod) {
          activities.sendEndOfTrialEmail(customerId);
          trialPeriod = false;
        } else {
          activities.sendMonthlyChargeEmail(customerId);
        }
      }
    } catch (CancellationException e) {
      activities.processSubscriptionCancellation(customerId);
      activities.sendSorryToSeeYouGoEmail(customerId);
    }
  }