Posts Tagged: microservices architecture

Using Kubernetes to Build Versatile Microservices

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

Should You Start With A Monolith or Microservices?

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

Tooling Review: AsyncAPI

Documentation will set you free – this is a mantra often delivered by experienced developers, and it bears repeating whenever the value of documentation is discussed. Simply put, documentation is perhaps one of the most important elements of effective API developer communication, second only to active demonstrations, tutorials, and other interactive systems. Read more

7 Unique Benefits of Using GraphQL in Microservices

This post is included in our eBook on GraphQL. Download a free copy here!

We’ve talked about GraphQL at length previously, and for very good reason – GraphQL is, in many ways, one of the more powerful tools an API provider has in terms of providing singular endpoints to the consumer and controlling data flow. 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