/microservices-demo

Demo application to go with Blog on spring.io

Primary LanguageJava

microservices-demo

Demo application to go with my Microservices Blog on the spring.io website.

Demo System Schematic

Clone it and either load into your favorite IDE or use maven directly.

Using an IDE

You can run the system in your IDE by running the three servers in order: RegistrationService, AccountsService and WebService.

As discussed in the Blog, open the Eureka dashboard http://localhost:1111 in your browser to see that the ACCOUNTS-SERVICE and WEB-SERVICE applications have registered. Next open the Demo Home Page http://localhost:3333 in and click one of the demo links.

The localhost:3333 web-site is being handled by a Spring MVC Controller in the WebService application, but you should also see logging output from AccountsService showing requests for Account data.

Command Line

You may find it easier to view the different applications by running them from a command line since you can place the three windows side-by-side and watch their log output

To do this, open three CMD windows (Windows) or three Terminal windows (MacOS, Linux) and arrange so you can view them conveniently.

  1. In each window, change to the directory where you cloned the demo.
  2. In the first window, build the application using mvn clean package
  3. In the same window run: java -jar target/microservice-demo-0.0.1-SNAPSHOT.jar registration
  4. Switch to the second window and run: java -jar target/microservice-demo-0.0.1-SNAPSHOT.jar accounts
  5. In the third window run: java -jar target/microservice-demo-0.0.1-SNAPSHOT.jar web
  6. In your favorite browser open the same two links: http://localhost:1111 and http://localhost:3333

You should see servers being registered in the log output of the first (registration) window. As you interact you should logging in the second and third windows.

  1. In a new window, run up a second account-server using HTTP port 2223:
    • java -jar target/microservice-demo-0.0.1-SNAPSHOT.jar accounts 2223
  2. Allow it to register itself
  3. Kill the first account-server and see the web-server switch to using the new account-server - no loss of service.