In this part 2 of 5 for the series, we’re going to look at the “What & When”of digital connectivity among products.
The fastest way to make this whole topic area a confusing mess is to just list out technology definitions. This might not be the best way to learn how things work. Though we do need to quickly visit buzzwords like REST, GraphQL, gRPC, webhooks, MCP, and some others. They don’t all sit at the same conceptual level, and they’re not interchangeable answers to one problem. What we’re going to do in this article series is look at some use cases and a handful of popular options. And in the very next installment, some live examples and work products of things you can try yourself if you want to dive in a bit. Again, we’re not trying to be coders. We won’t be experts. But sometimes just seeing something actually work can bring those Aha moments we can keep with us over time vs. just spewing buzzwords. It’s the difference between sleepily scanning another bullet point list vs. “oh, yeah… I see how that works now.” (We are going to ask some questions and run some lists first before we get to the fun stuff though.)
A useful direction in this space can perhaps start by asking ”What interaction are you trying to create?” Then look at technologies that can do it. Or you can always ask your dev, architect or AI team members. Yeah, I said it. “AI team members.” While I believe in the “mostly sort of trust, but verify” framework here, at this point, I’ve found our still somewhat new AI friends rise to that level. Maybe they still have that fresh new AI smell, and we still need to sort out best ways to use them, but there you go.
Diving deeper now, we can see things like OpenAPI and AsyncAPI can describe interfaces. OAuth 2.0 handles delegated authorization. JSON and Protocol Buffers represent data. SDKs package interfaces for developers. HTTP, WebSockets and MQTT move information. All these things matter, but they are not all separate product interaction categories.
[Read more…]







