Help me understand pro and cons of REST API approach vs gRPC Protobuff client.

[epheo]

So I wrote this: https://github.com/epheo/anytype-go as a proof of concept and to start playing with the Anytype API.
But I am now thinking that one would rather use anytype-heart gRPC with Protocol Buffers instead.
My longer term goal here is to have a foundation for developing other projects I have in mind such as:

• Infrastructure management from Anytype (IPAM / service configuration etc)
• Infrastructure monitoring with reporting in Anytype
• Blog publishing from Anytype Notes
• Command line interface to interact with Anytype
• Other various home / lab / life / work automation based on my anytype Types structure.

So I thought I would start with a GoLang SDK with an easy design pattern, but I'm lost now.

Would you:

• Consider this SDK useless ?
• Refactor this SDK to replace HTTP client with a direct gRPC client implementation ?
• Refactor this SDK as a wrapper around anytype-heart ?

Maybe @vas3k ?

Merci / many thanks.

[jmetrikat]

hey @epheo, that's cool, thanks for sharing your experimentation with anytype-go!

quick context on our API landscape:

• REST API: publicly documented (official launch just arround the corner!) and designed specifically for external extensions, agents, automations, etc.. we're actively improving it
• gRPC API: used only internally by our clients; powerful but not intended for external integrations

your sdk definitely isn't useless, it's such projects we love to see developers create! i'd recommend sticking with rest, which has safeguards in place, whereas the gRPC internals are risky to use. roadmap-wise, we'll extend the REST API with block operations and more advanced search & filtering. also, we're looking into auto-generation of official sdks in other languages.

lmk if you have feedback regarding the API, your input is super valuable! :)