this post was submitted on 02 Aug 2023
21 points (92.0% liked)

Programming

17450 readers
73 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
 

We are working on a tool that essentially allows external customers to access various extracts of our datasets, with parameterized filtering, aggregation, the usual stuff, though REST API. Some of these extracts are time consuming to prepare, so we are looking for ways to manage asynchronous report generation or making it possible for customers to schedule reports upfront, as opposed to having a synchronous API. There are tons of libraries for implementing synchronous REST APIs, but are there any standard approaches or tools for this kind of asynchronous cross-organizational communication? Like, maybe something that would allow each customer inspect their schedules and pending queries, configure how they want the results to be delivered? I fear we will need to build something like that from scratch.

all 3 comments
sorted by: hot top controversial new old
[–] ArmoredCavalry@lemmy.world 16 points 1 year ago* (last edited 1 year ago) (1 children)

Sounds like what you want is some form of webhooks that your customers can sign up for, that will send out when the reports are complete.

There are quite a few ways to do that. One I've looked at recently is Convoy, for setting up a user-facing webhook Dashboard -

https://getconvoy.io/

By using webhooks for delivery, then your actual configuration / viewing of schedules just becomes standard API calls.

[–] liori@lemm.ee 5 points 1 year ago* (last edited 1 year ago)

Yep, thank you, that's pretty close to what I imagined!