Notes
microservice template
Content of the notes (1)
Page 1
contract:
contracts.v1: swagger.yaml - declaration of the restful api. Easily edited by http://editor.swagger.io/
pom:
used to generate interfaces from swagger.yaml file in specific language (in our case, spring)
generated documantaion in S3 (in our case, in html and dynamic-html)
logic:
controllers: Responsible for rest requests
auth: ApplicationSecurity, AuthenticationSecurity..
internal: holds all the logic that v1/v2/ect controllers use. Compenent of ApiController
v1/v2..: restController, implemets the interface generated from the swagger by maven (placed in the target folder of contract)
logic:
processors
processorExecutor: excecutes all processors and merges the results. Each processor implement single method: process.
processorMerger: merges the results from all the processors
messagebus
models: Objects used.
utils:
Application: contains the main. Loads Spring with its annotatios using @SpringBootApplication, which includes @ComponentScan
pom: Responsible for the logic dependencies
more & important:
target: generated with maven, represents the build directory. Every temporary file that is generated during the build with maven from the sources ends up there
procfile: configuration file for heroku
Information
- Description
- Note on microservice template , created by Moran Abelev on 27/08/2017.
- Created by
- Moran Abelev · Aug 2017
- Updated
- Sep 4, 2017
- Views
- 5
- Rating