3 ms·

I'm the article author, and it's great to hear your feedback! I've published a couple of other articles that may help with the topic of microservices: https://

I'm the article author, and it's great to hear your feedback! I've published a couple of other articles that may help with the topic of microservices: https://opencredo.com/javaone-building-a-microservice-development-ecosystem-video/ https://opencredo.com/javaone-building-a-microservice-develo... https://opencredo.com/the-seven-deadly-sins-of-microservices-redux/ https://opencredo.com/the-seven-deadly-sins-of-microservices... I'm also looking for more suggestions of how people will want to use Hoverfly with Java projects, and so please do give me a shout via twitter @danielbryantuk if you have any ideas!

dpeterson 11y ago
One sticking point; what if the monolith does not have an endpoint you can call with an http request? What if you have a client that consumes the back end with server rendered pages and no services are exposed with url endpoints? Do you first have to make the monolith's internal functionality accessible via http requests?
- danielbryantuk 11y ago
  Adding 'seams' into the monolith (and exposing this typically via REST or AMQP) is the most effective way I have found. The alternative is to 'screen scrape' the data returned from calling the monolithic application via the interface exposed now. For example, calling a website page, parsing the HTML data returned, and extracting what you require. However, the code/algorithms you have to write are typically complicated, and the resultant code often fragile and highly-coupled