---
title: "Discussion on \"Designing a REST API for a Payment Ledger: Resources, Verbs, and Why I Avoided GraphQL\" | Hashnode"
description: "Discussion on \"Designing a REST API for a Payment Ledger: Resources, Verbs, and Why I Avoided GraphQL\". The running-balance line in your banking app looks like a stored number, but building it taught me more about pagination and window functions than any tutorial ever did"
url: "https://hashnode.com/posts/designing-a-rest-api-for-a-payment-ledger/6a42b12ca95ac1e9b5d08557"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Designing a REST API for a Payment Ledger: Resources, Verbs, and Why I Avoided GraphQL](https://notes.sohag.pro/designing-a-rest-api-for-a-payment-ledger?utm_source=hashnode&utm_medium=feed)

The running-balance line in your banking app looks like a stored number, but building it taught me more about pagination and window functions than any tutorial ever did

Jun 29 · 10 min read · notes.sohag.pro  
Read the article

-   [#go](https://hashnode.com/tag/go)
-   [#golang](https://hashnode.com/tag/golang)
-   [#rest](https://hashnode.com/tag/rest)
-   [#api](https://hashnode.com/tag/api)
-   [#postgres](https://hashnode.com/tag/postgres)

## Written by

[Sohag Hasan](https://hashnode.com/@sohag)

@sohag · Dhaka, Bangladesh

  
[View profile](https://hashnode.com/@sohag)

Tech Lead at MobyPay | Certified Laravel Developer | PHP JS GO | DevOps Enthusiast | Open to projects

WhoAmI => notes.sohag.pro/author

## Responses

Markdown supported · ⌘↵ to post

No responses yet.