Posts Tagged: microservice

Using Test-Driven Development for Microservices

The microservices design paradigm has become a prominent software design methodology now that API-first industries embrace a more decoupled operational strata. In the past we’ve discussed asynchronous choreography, BFF design, as well as identity control for microservices. However, one question remains: what is the most effective means for testing microservices? Read more

Building a Backend for Frontend (BFF) For Your Microservices

APIs are, by design, vastly interconnected. In order to effectively function and carry out the purposes for their creation, APIs are crafted to connect easily to other services, both internal and external. While this certainly is beneficial from a user perspective, developers often find the result of this type of development to have some problematic elements. Read more

5 Lightweight PHP Frameworks to Build REST APIs

PHP is a powerful language, with a wide range of offerings that make utilizing it for anything from basic websites to complex APIs a very strong proposition. It’s got a wonderful low barrier of entry, a gigantic ecosystem of solutions, and a variety of framework implementations that can make it do almost whatever you dream. Read more

6 Tips to Become a Master Microservice Gardener

The art of providing an API is extremely interesting, largely due to the dichotomy of opposing requirements. On the one hand, an API must be innovative, quick to change, and ever evolving. On the other, consumers demand stability, and with it, the security that comes with proven solutions. 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