suggested note about this guide not being ideal for real world setup

[stguitar]

This guide creates a single deployable package (war) for 2 microservices.

The guide uses HTTP to communicate between these 2 services, to prove a point but this is not practical in real world usage. Typically, since all of the classes are in the same class path, you would just execute various methods on the injected classes directly, rather than making HTTP calls to get data between the 'services'.

It might be helpful to simply add a disclaimer note on the guide at a few points to point this fact out.

[yeekangc]

Thank you, @stguitar. We should either split things up or put a note as you said.

@gkwan-ibm

[salmad3]

I would suggest we update the application to a more practical use case, such as data being hosted on an origin, where the CORS application, hosted on another origin, would access that data.