Pico Programming Lesson: Modules and External APIs
A new pico lesson is available that shows how to use user-defined actions in modules to wrap an API.
Continue reading {Pico Programming Lesson: Modules and External APIs}
Notes from Gluecon 2016
Here are notes I live tweeted at Gluecon 2016.
Continue reading {Notes from Gluecon 2016}
Building a Personal API
The BYU University API committee has been looking for a good project to jumpstart our efforts in personal APIs. The BYU Domains project is not only providing the means to host the personal API, but the initial project as well.
Continue reading {Building a Personal API}
Personal APIs in a University Setting
This is the abstract from my proposal to speak at APIStrat 2016.
Continue reading {Personal APIs in a University Setting}
Resources, Not Data
We need to stop trying to understand REST in terms of data-centric programming paradigms. The result will be better-designed APIs.
Continue reading {Resources, Not Data}
The Core of Your API
A university is a complex place with lots of constituencies. What does it mean to design a University API given the different focus that each constituency has?
Continue reading {The Core of Your API}
When Services Die
What happens when your favorite service dies? Will your data live on? Not if you're dependent on cloud-based services you don't control.
Continue reading {When Services Die }
Clean Sheets and APIs
David Barrett of Expensify just led a session at Kynetx Impact on APIs. His talk was listed as "When APIs go bad. APIs are powerful, but when should you consider not providing an API for your data." He followed Sam Ramji who gave an updated version of his Darwin's Finches talk. The updates are recorded in two recent articles The Building Blocks for a Successful API Strategy and With APIs It's Caveat Structor - Developer Beware. Consequently there was some good discussion and interaction from the audience. David's main point is that building an API isn't free and for
Continue reading {Clean Sheets and APIs}
Clay Loveless: Understanding API Usage
I was in a Point-of-View session at Defrag with Laura Merling of Alcatel-Lucent, Brian Mulloy of Apigee, and Clay Loveless of Mashery. Laura and Brian gave interesting talks, but since they went before me, I was too occupied to take notes. I did take notes for Clay's talk, however, since he went after me. :-) Clay gave six tips for making an API work: Test it all. Unit tests are just the beginning, but if you don't have them yet, don't start there. Instead, test what your user's experience with end-to-end black box tests. Replaying your access logs is
Continue reading {Clay Loveless: Understanding API Usage}
Events, Webhooks, and the Realtime Web: Kynetx Dev Days
At Kynetx we're very bullish on the real-time Web. There are several trends that are leading us inexorably toward better use of real-time data including webhooks, Restful APIs, streaming data from sources like Twitter and Facebook, and Internet identity protocols like OAuth. At Kynetx, we use the term "event-driven" to descibe systems and architectures that make use of these ideas. Kynetx is a system for building event-driven applications that make use of webhooks, APIs, stream data, and user-centric identity. As I said in my post on Static Queries, Dynamic Data: Enabling the Real Time Web, In a traditional database,
Continue reading {Events, Webhooks, and the Realtime Web: Kynetx Dev Days}





