Skip to content

README.md

Latest commit

 

History

History
75 lines (54 loc) · 3.01 KB

README.md

File metadata and controls

75 lines (54 loc) · 3.01 KB

Spring cloud

Sandbox to play with spring cloud features

Servers

Name Description Default port Details
Configuration server Configuration server 8888 You should set an JAVA_CLUB_SRC_HOME variable which points to the folder where your java club sources are checked out.
Configs URL example: http://localhost:8888/cloud/master
Discovery server Discovery server 8761 Eureka server for services registration.

Service

Name Description Default port Details
Rating service Rating Calculation Service 8081
Hackster service Hackster Detection Service 8082
Client service Client Service 8083
Realtor service Realtor Api Service 8080 To call other services used Feign, RestTemplate
Storage service Storage of Apartment Records Service 8091 H2 based service for ApartmentRecord data storage.
API gateway service Zull API Gateway Service 8090

Dev

Before

  • Set up JAVA_CLUB_SRC_HOME environment variable that point to folder with project spring-cloud

  • If you have issues with test containers (docker images) then check if you have DOCKER_HOST environment variable. If no then add it using this : export DOCKER_HOST=unix:///var/run/docker.sock (example for Docker For Mac)

Build

mvn clean install

Run



PCF


Pivotal cf can be used on both: server trial and local installation: PCF dev, more information:
https://docs.pivotal.io/pcf-dev/


manifest.yml was created to push with configured environment options and set spring-profile 'cloud' to enable eureka
detection via 'VCAP' environment based configuration. More information about environment variables:
http://docs.pivotal.io/pivotalcf/1-11/devguide/deploy-apps/environment-variable.html


To set eureka service after push to cloud-foundry run:
cf cups eureka -p '{"url": "http://discovery.{YOUR_DEFINED_CF_HOST}/eureka/"}', i.e.:
YOUR_DEFINED_CF_HOST = local.pcfdev.io.


In application \ bootstrap properties is used "nonSecurePort: 8080", as eureka is deployed on '8080',
as all other instances, so it redefines default 80 port to make possible interconnection between registered via
eureka services.


TODO Items


    

  •  Check Feign Fallback ?
    • 

  •  Storage Service (persistance + Eureka client)
    • 

  •  Rieltor Service
    • 

  •  All Eureka clients add Eureka server address to properties
    • 

  •  Client service for search
    • 

  •  Zuul like a proxy API gateway
    • 

  •  Cloud foundary
    • 

  •  FeignClient usage
    • 

  •  Circuit Breaker: Hystrix Clients
    • 

  •  Connect Zipkin
    • 

  •  Event Driven with JMS or Kafka
    • 

  •  Create parser for Visokiy Zamok data
    • 

  •  Security check to implement with Zuul only
    •