Design a high-level API (like a framework)

[aoberoi]

Description

This is a ticket that tracks discussions related to the design of a high level framework-style API.

Some discussion naturally arose around the datastore API, specifically in this comment

An issue that outlines some differences between the old slack-client package and the @slack/client package contains a useful discussion: #141. the old package was more high-level, so some use cases for this API can be extracted from that.

Requirements (place an x in each of the [ ])

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

[aoberoi]

for inspiration: this ruby based framework seems to be popular and mature. there's probably quite a few lessons we can take from it.

[aoberoi]

this hasn't been a useful venue for a conversation, so i'm closing. if anyone has thoughts they'd like to contribute, feel free to comment and we'll reopen.