The world of API architecture and development is tricky in many ways. Unfortunately, there is no such thing as a “perfect” solution, and with every new implementation or solution, new problems are bound to crop up.
It is important to remember, then, that even the most positive, powerful decisions in API architecture could have significant issues in the long run that, if not recognized in the hazy glow of post-adoption euphoria, could easily interfere with the success of an API or collection of APIs. Read more
How does one go about securing APIs, microservices, and websites? One way to do this is by focusing on the identity — knowing who the caller is, and what the caller is allowed to do with your data. Too often, though, providers rely too heavily on user social identity, pairing it way too closely with the design of their APIs. Read more
One of the major issues universally faced in API development is the management, packaging, and distribution of dependencies. The dependency set required by an API might make it extensible, wonderful to use, and extremely powerful. However, if hard to manage, dependencies could spell adoption limbo.read
A solution to this age-old problem has exploded onto the scene in recent years, however. Read more
In Writing Microservices in Go pt. 1, we highlighted a whole bevy of reasons for coding in Go, the novel, forward-thinking language developed at Google. However, there are two sides to every coin; the benefit of a language or system can often be a drawback in other use cases, and a host of hidden faults can make what was once an awesome idea significantly less awesome. Read more