Serverless, GraphQL, Go, microservices… disruptive tech offers great benefits, but is “boring” tech better from a pragmatic viewpoint?
If it ain’t broke, don’t fix it. No need to reinvent the wheel. The KISS (Keep It Simple, Stupid!) principle. There are plenty of expressions and the like out there that advocate embracing the tried and tested over the complex and newfangled, but sometimes the siren song of cutting-edge technology is just too much to resist. Read more
Kubernetes is often talked about, but seldom fully understood system in the API industry. This is largely because containerization, the principle approach that Kubernetes is built upon, is still not nearly as ubiquitous as the classical approach to API design and resource management. Read more
Challenging Conventional Wisdom
Conventional wisdom suggests that a new project should start with a monolithic server because a unified application can make the workflow easier for a small start-up team. But microservices can be a valuable alternative in the right circumstances. Read more
Everyone’s excited about microservices, but actual implementation is sparse. Perhaps the reason is that people are unclear on how these services talk to one another; especially tricky is properly maintaining identity and access management throughout a sea of independent services. Read more
It’s no longer one app to rule them all. From a user experience perspective, the industry has reached what Web Informant David Strom calls a “cheaper, pay by the drink model, [where you] don’t have to implement a particular computing environment or end-point device–now it’s their phone or their tablets.” On the consumer side, we aren’t just offering behemoth platforms like Salesforce, but we are drilling down to add dimension, allowing users to pick and choose their workflows. Read more