#sdk #abi #api I see a lot of architecture discussions like #API vs. #SDK and pros and cons. For me, it is more like API and SDK that together enrich the ecosystem and unlock a client side and edge computation capabilities together. Let's understand the difference between #ABI, API, and SDKs together. Why do you still need SDK even if you have modern microservices architecture?

• edge computation and using distributed client-side computation power
• security - it is one of the reasons why we have SDK your private keys and secrets never leave your device and are never exchanged via the network
• offer a more user/developer friendly interface that hides the complexity of API and complex orchestration
• allow replacement of API implementation like protocols and formats
• use a device-specific capabilities or device-specific data

One of the challenges of SDK is language selection. So deeply believe in a future of WebAssembly as intermediate exchange architecture for SDK. So you use your favorite languages that fit better for a task and over a set of web assembly modules that could be consumed by an ecosystem that can execute WA modules. Also, I believe in federated modular monolithic SDKs that could upgrade themselves on the fly and load code on demand