Using HTTP with miniservices keeps the agility, scalability, and functionality of binding of microservices without the prerequisites of event-driven design.
In an interview with Fred Churchville from TechTarget, Cloud Elements Head of Product Marketing Ross Garrett explains more about what miniservices are and how software teams should think about the ways they are approaching microservices in general.
A miniservice is taking the pragmatic approach to the content of microservices architecture. Microservices represent a very specific architectural model, compared to miniservices. Miniservices are just like microservices in regards to the agility, scalability, functionality of binding around services without being held up with the prerequisites around event-driven design.
It’s arguable that HTTP inherently doesn’t create the level of connectivity true to the vision of microservices, where the services should be able to exist completely independently. There are big steps forward in terms of service composition and reuse and scalability with surrounding technologies like HTTP, which makes everything much easier.
When choosing your approach, let’s first establish an understanding that you do not always have to follow the purist microservices requirements to achieve the same goals. Everything can still be achieved from the integration perspective without following microservice architectural model requirements.
Scalability is a big reason to take the microservices architecture approach. HTTP doesn’t solve the problem, but just because you have a hundred services or a thousand services doesn’t necessarily mean that HTTP is the wrong choice. It may be just as functional as any other integration technology. But there will be a point where the amount of traffic will make things inconvenient.
Ross Garrett, Head of Product Marketing, says, « I consider this miniservices thing to be pragmatic microservices, where I’m leveraging the pieces of that practice that makes sense for me and getting most of the functionality benefits. »
Another angle around HTTP or within web-centric integration that is useful is the concept of governance. HTTP gives more capability with an easier way of seeing where traffic is coming from and flowing to.
Does it seem to you like microservices are touted as a silver bullet, and that many organizations suffer from unrealistic expectations surrounding microservices?
« That’s why I consider this miniservices thing to be pragmatic microservices, where I’m leveraging the pieces of that practice that makes sense for me and getting most of the functionality benefits, » says Ross Garrett. « But I don’t have to throw everything away and start again. I don’t have to retrain an entire organization of engineers or architecture developers. I can get started and enjoy some of the quick wins. »
In the integration space, some vendors are pushing technologies not because it’s the best solution to the problem, but because it’s more self-serving for them.
Read the full interview: “ Miniservices may deliver, much to microservices purists’ chagrin ” from Fred Churchville and TechTarget.
