One of the many things to take into account when building a great API is granularity. For more experienced developers, the concept of granularity is a given, but it may be a confusing concept for programmers new to API development. Read more
API security is complex, and the underlying systems that support it are even more so. Getting a grasp on API security requires understanding many underlying components. Accordingly, any tool that can help contextualize these systems is not only a good educational tool, but it’s also a good business tool. Read more
Web services and APIs are two of those overlapping tech terms that regularly get confused. You might have even heard these words used interchangeably, but are they even the same thing?
While they do have some overlap, web services and APIs are two different concepts. Read more
Many of us are guilty of, even if only subconsciously, thinking about what we can get out a partnership. To convince partners to consume our APIs, we often consider great API design and quick developer onboarding. However, we may not be giving enough thought to the relation itself. Read more
Automatically generating documentation is a dream come true for developers looking to focus on the code instead of copywriting. It’s also a dream for end users, who get documentation that’s up-to-date and reliable.
REST vs SOAP. REST vs GraphQL. JSON vs XML. There are many dichotomies in the world of API design. It seems for each architectural choice there exists an opposite solution purpose-built for a specific application. We can see this in issues like statelessness and statefulness, as well as functional choices such as SOAP and REST. Read more
New software architecture design styles are coming out every year. They promise to offer greater flexibility, more power, and more freedom to compute in unique ways. Unfortunately, with this greater power comes a greater responsibility to ensure security holes are addressed. Read more