Posts By: Kristopher Sandoval

The Power of Relay; The Entry Point to GraphQL

The Power of Relay; The Entry Point to GraphQL

In many ways, GraphQL is a futuristic approach to dealing with all the headaches surrounding high-data transfer, large-volume relational content. As more is written about the technology and as its implementation is discussed, it goes without saying that related components are becoming increasingly more interesting as well. Read more

3 Methods to Documenting JSON APIs

3 Methods for Documenting JSON API Services

JSON is a very powerful, open standard format that is used by many services and APIs across the internet. Unfortunately, while open standard carries a lot of good, it also creates some pitfalls that developers may not be prepared to handle. Read more

Leverage Public APIs

Leverage Public APIs to Make Your System Better

The software world has moved in many ways towards the idea of modularity rather than the archetypal monolith — services and systems are continually developed in chunks rather than as a single system. This has spilled over into many aspects of the API space, and represents a powerful opportunity for developers to not only simplify the development cycle, but to leverage modularity to make their own offerings more powerful. Read more

How to Wrap a REST API in GraphQL

How to Wrap a REST API in GraphQL

GraphQL is a powerful tool that we’ve discussed previously at Nordic APIs. As with any emergent tool in the API space, however, there’s some disagreement on exactly how to implement it, and what the best practices for its implementation and use case scenarios are. Read more

How to Handle the Continuous Delivery of Microservices

How to Handle the Continuous Delivery of Microservices

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