Hemneo Memory

Hemneo Memory remembers.
Visit a listing or selling price on Hemnet and change the URL fromhemnet.se to hemneo.se.

Logs from the latest runs

How does this work?

Hemneo Memory is a proof of concept long term storage of memories (i.e. listings) from Hemnet using Cloudflare's cloud native technology.

Here is a short summary of how Hemneo Memory creates memories:

1. Approximately every half hour, 12 of the 290 municipalities in Sweden are randomly selected. Thelisting IDs for all active listing in the selected municipalities are retrieved from HemnetAPI. Only currently published common listings and project unit listings are considered. A maximum of 1,100 listings are retrieved from each municipality. The sort order varies randomly between newest/oldest, so the range is practically the double over time.
2. The listings arecompared to what is currently stored in the key-value storageusing a fast individual GET request for each listing ID.
3. Listing details for all new listings are retrieved and storedin the key-value storage. The details are retrieved in batches of 100 listings from HemnetAPI. Each listing is stored in a separate key using the listing ID.

To display the listing page, the corresponding listing information is retrieved from the key-value storage using the listing ID.

No image data is saved in the key-value database – only the image URLs. This reduces the storage need dramatically.

Technology used

• GitHub Actions. Used for deployment and scheduled data retrieval.
• Cloudflare Workers KV. Used for long-term storage of the listing information retrieved from HemnetAPI.
• Cloudflare Workers. Used to server render the website using Flareact.
• Flareact. Used to quickly provide a Next.js like React environment that can be deployed to Cloudflare Workers and use Cloudflare Workers KV natively.