APIs are complex webs of interconnected applications, interfaces, frontends, and backends. Making sense of these systems is not always easy to do. When so much of the data coming into a system is from external sources that run the gamut from trusted to untrusted, known to unknown, the easiest way to classify that data is to classify it by the source origin – that is, to not talk about the nature of the data, but rather the nature of that which sent the data. Read more
Posts Tagged: server
One of the biggest challenges in agile development is enabling dependent teams to work independently. For instance, how do you keep your quality assurance teams busy while the backend is still being built?
Development does not occur in isolation – it is an active, interconnected process. Because of this, one of the most important things a developer can incorporate into their development lifecycle is testing. Testing each stage of code development and deployment can ensure that services perform as expected, and have a high-quality user experience. Read more
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
Above all else, API communication is really a negotiation between the client and the server. Once we clear all the dust, this basic communication underlies every protocol, architecture, and approach. These negotiations are often complex, and deciding who has the responsibility for what aspect of this negotiated communication is an age-old conversation. Read more