Pluggable adapter library: Stripe, Twilio/WhatsApp, Resend, S3 behind a common interface
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 8/100
Research direction
No files, tests or entry points are named in the issue. Start by mapping the Go module and any existing mail, storage, payments or messaging wiring to see where adapter contracts would live, then compare that with the four proposed interfaces. Done means the contracts exist, at least one adapter per category is implemented, and a config change switches providers without handler edits.
Written by the indexing model from the issue text.
Description
Vision
Every business app needs payments + SMS + email + file storage. Today, each app picks providers and wires them — switching providers is a 1-week migration. A framework that abstracts these behind one interface and ships swappable adapters wins the "oh I'll just build it on Grit" moment.
Proposal
Three adapter contracts:
```go
type PaymentsAdapter interface {
Charge(ctx, ChargeRequest) (Charge, error)
Refund(ctx, RefundRequest) (Refund, error)
Subscribe(ctx, SubRequest) (Subscription, error)
Webhook(payload []byte) (Event, error)
}
type MessagingAdapter interface {
SendSMS(ctx, to, body) (MessageReceipt, error)
SendWhatsApp(ctx, to, body, attachments) (MessageReceipt, error)
}
type StorageAdapter interface {
Put(ctx, key, body, contentType) (URL, error)
PresignPut(ctx, key) (URL, error)
Delete(ctx, key) error
}
type MailAdapter interface {
Send(ctx, MailMessage) (Receipt, error)
SendBatch(ctx, []MailMessage) ([]Receipt, error)
}
```
Ship adapters: Stripe + Paystack (payments), Twilio + WasenderAPI + WhatsApp Cloud (messaging), Resend + SendGrid + SES (mail), S3 + R2 + MinIO (storage). Switching providers is a config change.
Why this is differentiating
Encore + WunderGraph are betting the company on this exact pattern. Grit beating them to it for self-hosted Go is a real opening.
Acceptance
- Switching from Stripe to Paystack (for African markets) is a one-line config change — zero handler edits
- A Grit app written today still works in 5 years when Stripe pivots their API; the adapter shim absorbs the change
- Dominant language
- Go
- Stars
- 152
- Forks
- 20
- Avg merge
- 1d 49m
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MUKE-coder/grit
-
[Plugin] calendarOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MUKE-coder/grit#228 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 65/100
MUKE-coder/grit#227 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 18/100
MUKE-coder/grit#224 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
MUKE-coder/grit#199 · 4 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
MUKE-coder/grit#179 · 4 comments ·
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
Chemaclass/agnostic-ai#3681 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
OSS TEST
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
seaweedfs/seaweed-block#268 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day