The only real problem I find with REST+microservices as an architecture is situations where the right framework for one of the microservices' jobs is not well-e

The only real problem I find with REST+microservices as an architecture is situations where the right framework for one of the microservices' jobs is not well-equipped for HTTP interactions. Although it's always possible to knock something up to get the job done, a developer working in (e.g.) XSLT is not necessarily in his or her comfort zone when working with remote services, and that tends to cause delays and other headaches. Otherwise, though, I'm all in favour of it as an architectural choice.