Simplifying the Fortification of your Data Lake with Apache Knox
GraphQL Server With .NET Framework (Not .NET Core)
#ICYMI: In a recent post, we had listed out analyses done and conclusions made when asked by a customer to convert their existing API to GraphQL. While exploring GraphQL with .NET framework, we realized there is a large gap in examples and demos on using GraphQL with full scale .NET framework and EntityFramework. We took some time out to create a sample repo and put it out there so that other programmers don’t have to wonder whether its even possible.
The repo is available at https://github.com/anshulee/GraphQLHobbyAPI https://goo.gl/AApcrF #DataIntegration #ML
Thinking Deeply About Other People Using Your API Is The Most Valuable Lesson Of API Design
I am deploying a patent review API for a client, using data from the Patent Examination Data System (PEDS). You can download complete JSON or XML data from the United States Patent Office (USPTO), and they even have an API. So, why would I be launching yet another API? Well, because what they have is so cryptic, complex, and lacking in any schema or API design, there is value in me pushing the API conversation forward a bit by thinking deeply about how other people will potentially be using these resources — something the USPTO clearly hasn’t done.
The USPTO PEDS API (that is more acronyms than you can shake a stick at) is a great example of how much database people and developers take for granted as they operate within their little bubbles, without much concern for how the rest of the world views their work — take a look at the screenshot of the USPTO PEDS API. https://goo.gl/14gN24 #DataIntegration #ML