Skip to content

Latest commit

 

History

History
114 lines (73 loc) · 5.1 KB

README.md

File metadata and controls

114 lines (73 loc) · 5.1 KB
Raw

microservices_poc

Proof of concept of microservices based on Devonfw (Spring Cloud). More info here

The Project Includes

  • Microservices Infrastructure: Eureka, Zuul, Centralized Configurations, Auth service sample.
  • Microservices:
    • Microservice 1
    • Microservice 2

Installation of Devonfw modules (if you are new on Devonfw)

⚠️ This project is based on devonfw 2.4.0

  1. Download devonfw
  2. Initialize the distribution executing the create-or-update-workspace.bat script
  3. Launch the console.bat script and install the microservices module C:...\Devon-dist\workspaces\examples\devon\modules\microservices>mvn install
  4. Clone this repository in a new directory microservices_poc created in your workspaces folder
  5. Execute the script update-all-workspaces.bat to generate the Eclipse instance for the microservices_poc project
  6. Launch the just created eclipse-microservices_poc.bat script and import the microservices projects included in this repo.

Implemented Services

  • login (Auth service) --> is mocked, only a PoC
  • logic in Microservice 1
  • logic in Microserivce 2
  • Microservice 1 calling Microservice 2 to get some data.

Postman collection

Also included a postman collection (microservices.postman_collection.json) to test the project. The collection uses Environment variables to ease of use of the calls.

See: - https://www.getpostman.com/docs/v6/postman/environments_and_globals/manage_environments - https://www.getpostman.com/docs/v6/postman/environments_and_globals/variables

Calls included in this Postman collection:

- login: returns the jwt based on a user/password POST call.
- Through Zuul
	* call to microservice 1
	* call to microservice 2
	* call to microservice 1 that also calls microservice 2

Running the microservices

You can run it using Eclipse, Maven or using the bootified artifact of each project. In order to see all the system working together you will need to run the following list of infrastructure services:

  • service-eureka
  • service-zuul
  • service-configserver
  • service-auth

And then you need to launch the microservices:

  • sampleapp1
  • sampleapp2

As we will see later you can run as many instances as you want of each microservice, only using a different port.

Once everything is up and running you can go to the url http://localhost:8761/ (the Eureka's url) and see the status of the system.

With Eclipse

Once you have your projects imported into the Eclipse instance you can go to the main class of each one (the one with the @SpringBootApplication annotation), right click on the class and select Run As > Java Application. You will see the output in the Console Tab of Eclipse. Repeat the same operation in all the projects, a different Console tab will show in Eclipse the output of each project.

With Maven

To run the services from a command line, as all are Spring Boot projects, you can use Maven to run each of them. Go to the root of each project (where the pom.xml file is located) and use the command (with different command line instance for each project):

C:\...\the-project> mvn spring-boot:run

Run multiple instances of a microservice with Maven

In the case of the microservices (sampleApp1 and sampleApp2) you can run multiple instances of each project (that will be automatically registered in Eureka) providing different server ports.

In the root directory of the microservice you want to replicate run the command

C:\...\the-project> mvn -Dserver.port=[a-port-number] spring-boot:run

Example:

C:\...\sampleapp1> mvn -Dserver.port=9092 spring-boot:run

This will run an instance of the sampleapp1 in the 9092 port.

With bootified artifact

Alternatively to the Maven option you can run the Spring Boot projects using the bootified artifact that is created in the packaging process of each project.

First create the bootified artifact (in each project) with the command

C:\...\project> mvn clean package

Repeat the same process in all the projects (eureka, zuul, config, auth, sampleApp1 and sampleApp2).

Run the infrastructure with the bootified artifacts

Then in the target directory you will find the just created bootified artifact that can run in "stand alone" mode. Run the artifact with the command

C:\...\project\target> java -jar [name-of-the-project]-bootified.jar

Repeat the same process

Run multiple instances of a microservice with the bootified artifact

In the case of the microservices (sampleApp1 and sampleApp2) you can run multiple instances of each project (that will be automatically registered in Eureka) providing different server ports.

In the target directory launch the command

C:\...\the-project\target> java -jar -Dserver.port=[a-port-number] [project-name]-bootified.jar

Example:

C:\...\sampleapp1\target> java -jar -Dserver.port=9091 sampleapp1-bootified.jar

This will run an instance of the sampleapp1 in the 9091 port.

You can repeat the same operation again with sampleapp1 or with sampleapp2.