🚀 Caught up on AWS’s open-sourcing of API models in Smithy format (slipped my radar earlier this yea
🚀 Caught up on AWS’s open-sourcing of API models in Smithy format (slipped my radar earlier this year, but timeless value!). There is a GitHub Repository [4] available with AWS API smithy models for 200+ services. Announcement Blog: [1]
A Smithy model is the core semantic representation in Smithy, an open-source interface definition language (IDL) developed by AWS for defining APIs, services, and data structures in a protocol-agnostic way.
It consists of shapes (like primitives, lists, maps, structures, and services), traits for metadata, and shape IDs for referencing components, enabling code generation for SDKs, documentation, and validation across languages. Models are serialized in formats like Smithy IDL or JSON and include a prelude with built-in types.
Kind of an interesting twist in IT history: Did it need the advent of AI Agents
Kind of an interesting twist in IT history: Did it need the advent of AI Agents to drive developer friendly, standardized and discoverable interfaces to systems?
Recently Model Context Protocol (MCP) got a lot of attention and traction. While this is good and exciting thing, I was wondering why this is actual needed? In a perfect & developer friendly world, it shouldn’t need another protocol just for agents, does it? AI should easily be able to use the existing interfaces, which have been built for convenience of human developers, no?