Previous post: Hacker News API part 1
Github project related to this post hnfetch
In the last post I demonstrated building a program to fetch data from the Hacker News API using a combination of libraries including scalaj-http and uPickle. This time I will demonstrate a wrapper around the core functionality using the Fetch library by the cool folk at 47 Degrees.
Fetch is based on the Facebook’s Haskell library Haxl and is designed to reduce the amount of complexity around managing calls to data sources such as caches, databases and web api’s. In this article I will show how to turn my simple http calls to the Hacker News API into Fetch friendly data sources. That will then enable us to take advantage of automatic caching of stories and users, management of how many concurrent calls to make as well as giving us a nice purely functional interface to the data which uses Free Monads.
Since their documentation already contains a very good tutorial and guide to all the features, I won’t repeat that here and encourage you to read that instead.
Fetch uses functional programming library Cats, so let’s bring that into the project as well as Fetch itself:
The next step in converting the Hacker News api code to Fetch is to create datasource for the user and story types.
As you can see in the Fetch documentation (and source) a datasource just has to say how to get one of a thing, multiple things, and some behaviour configuration: DataSource
Here’s the data sources for Hacker News items and stories.
Some things to note:
- You also need to make smart constructors for each datasource to create
- Each data source has a name to identify it. “item” and “story” in this case
- You can define how mant requests to make to each data source in batches, if the underlying DB or resource supports batching for example.
With that underway we can now utilize the Fetch library to grab our data in various ways. The example program FrontPageWithFetch demonstrates the runF command
fetchItems.runF[Future](cache.get) which returns both the Fetch result and a FetchEnv. The FetchEnv includes a detailed history of the fetch operaion as well as a cache that we can pass into the next call and avoid retrieving duplicate items. Check the Fetch documentation for how to implemnent your own cache should you need specific behaviour.
Here’s a little video of the interactive front page terminal app showing how repeated requests to the same page do not request them from the API…
Fetch’s big idea is to hide complexity such as caching, rate limiting and other complexities from client code, another big advantage of such a functional approach is that you can compose queries. In this example (not in the github repo) I demonstrate grabbing a user and his submitted items in a for comprehension. Note that the call to getUser and getItems compose nicely into Fetch operations and are then executed with runA to get the result.
This has been a short and sweet introduction to Fetch. It seems like a solid library with a lot of use cases, and a good example of Free Monad’s in the wild.
Postscript: Thanks to a suggestion from @peterneyens I’ve update the async datasources to use onComplete rather than map/recover