The API space is ever-evolving. As the needs of end-users grow in both complexity and frequency, new software development strategies continue to emerge. When working with APIs, it’s not uncommon to see a network of systems handling a single purpose. In fact, during the modern age of microservice architectures, this has become the design paradigm de jure, with each API operating a small fraction of the much larger machine. Read more
Posts Tagged: system
Have you ever tried to implement a new process in a big company? Believe us when we tell you that it’s not an easy (or fun) task. From obtaining initial approval all the way through to disseminating information, it takes time and there are often bumps along the road. Read more
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
Have you noticed that your API sometimes feels a bit misunderstood, seen as a sideline or a purely technical solution?
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