Implementing a custom Route Attribute for Web API that considers Content-Type. This allows for routing based on the data encoding being supplied by the HTTP Request, not just the path and parameters it was sent to.
Can your average Developer/Maker afford to use Azure? I decided to skip any “back of the napkin” calculations (since most napkins are notoriously unreliable finks when it comes to architecture and finances) and actually build something. My criteria was simple, stand up an app on Azure that could communicate with 15-20 “things” for less than $12 per month. I determined this amount scientifically; it is what it costs for a 4-Screen Netflix account. I failed, it ended up being free.