If a user wants to access all metadata on the registry, they need to make several hundred requests. This takes a long time, and it’s possible to come unstuck by rate limiting etc.
We use it internally for other services, including IATI data dump and Code for IATI Analytics. Since we’re using it internally, we thought we might as well make it available externally too.
NB We should also include a shout-out to the d-portal team, who already did this years ago!
What’s the goal of the blog?
To inform technical users of this service, and to demonstrate that Code for IATI takes a microservices approach. Our services reuse other services as much as possible. Reuse makes maintenance much easier, since we can use the same resource for lots of projects, and only have to maintain it in one place.
What’s the blog about?
If a user wants to access all metadata on the registry, they need to make several hundred requests. This takes a long time, and it’s possible to come unstuck by rate limiting etc.
This service allows you to get all metadata in just two requests: https://registry.codeforiati.org
It’s regularly updated (roughly every 3 hours).
We use it internally for other services, including IATI data dump and Code for IATI Analytics. Since we’re using it internally, we thought we might as well make it available externally too.
NB We should also include a shout-out to the d-portal team, who already did this years ago!
What’s the goal of the blog?
To inform technical users of this service, and to demonstrate that Code for IATI takes a microservices approach. Our services reuse other services as much as possible. Reuse makes maintenance much easier, since we can use the same resource for lots of projects, and only have to maintain it in one place.