• We’re so glad you’re here. • You can expect all the best TNS content to arrive Monday through Friday to keep you on top of the news and at the top of your game. • Check your inbox for a confirmation email where you can adjust your preferences and even join additional groups. • Follow TNS on your favorite social media networks. • Become aTNS follower on LinkedIn. • Check outthe latest featured and trending storieswhile you wait for your first TNS newsletter.
Article Summaries:
- Kin Lane, founder of Naftiko, argues that the API ecosystem is cluttered with “API sediment” - legacy standards such as EDI, WSDL, Swagger, API Blueprint, and RAML that accumulate over time and become costly to replace. He attributes the proliferation to vendor “land grabs” and the timing of each spec’s development. Lane notes that while REST APIs displaced SOAP in the 2010s, newer asynchronous patterns (event‑driven, WebSockets, streaming) outgrow OpenAPI’s request‑response model, leading to the rise of AsyncAPI. Naftiko’s mission is to help organizations clean up this layered legacy and adopt more modern, stable integration practices.
- Kin Lane, founder of Naftiko, highlights the growing “API sediment” problem-organizations layer legacy integration standards (EDI, WSDL, Swagger, OpenAPI, AsyncAPI, etc.) over time, making migration costly and risky. Lane attributes the proliferation of competing specs to vendor “land grabs” and the historical context of each standard’s development. He notes that while REST APIs replaced SOAP in the 2010s, newer asynchronous patterns (event‑driven, WebSockets, streaming) outpaced OpenAPI’s request‑response model, prompting the AsyncAPI spec. Naftiko was created to address this accumulation of outdated layers and help enterprises streamline their API strategies.
Sources: