rafabc / microservices-maven-archetypes

Collection of maven microservices archetype to simplify its creation

microservices-maven-archetypes

Summary

Catalog of maven archetypes to develop microservices simplifying their creation and preconfigured to integrate directly with the tools Zuul, Eureka, Spring Boot Admin, Swagger, Zipkin and Spring Cloud Config.

Prerequisites

• JDK 8
• Maven 3

Ecosystem result

General installation instructions

Two installation ways:

Local

1. Clone repository

git clone https://github.com/rafabc/microservices-maven-archetypes.git

After clone this project contain a shell script "mvn-install-archetypes.sh" that run all the nexts steps, but its posible run it manually if you want one by one:

2. In console go to each archetype path

cd microservices-maven-archetypes/[archetype-path]

3. run next mvn install for each archetype

mvn install 	#for each archetype

4. After install all archetypes update the catalog

mvn install archetype:update-local-catalog
mvn archetype:crawl

Hosted

1. Clone repository

git clone https://github.com/rafabc/microservices-maven-archetypes.git

2. Install the archetypes in your maven repository
3. This repository provide a catalog file, with it you can update your hosted catalog and then use it where you want.

Instructions for creating projects

• Spring Cloud Config Server
• Eureka
• Spring Boot Admin
• Zuul
• Swagger Catalog
• Zipkin
• Spring microservice
• Nodejs microservice

Automation

If all archetypes are installed, its posible use mvn-create-projects.sh to create fast all environmet projects whit default value parameters and test it.

After the projects are ready its posible execute the script "run-projects.sh" that launch each project.

microservices-maven-archetypes's Issues

CORS problem in Swagger Catalog

CORS
CORS is blocking access to swagger catalog services.

To Reproduce
Steps to reproduce the behavior:

1. Install all archetypes
2. Create projects
3. Run projects
4. Try access to Swagger Catalog

Expected behavior
The correct result must be the Swagger web showing all servcies.

Spring boot admin can't kill node microservice

Spring boot admin cant kill node microservices
When try kill a node microservice from Spring Boot Admin only unregistered from Eureka, but the service still continue alive, so itshelf autoregister again int Eureka.

To Reproduce
Steps to reproduce the behavior:

1. Run config server, eureka, spring boot admin and node microservice
2. From spring boot admin try kill node microservice
3. After a few second apear registered again

Expected behavior
Its posible a spring boot admin personalization to kill the node microservice.