Configure Eureka to handle requests and responses for micro-services.

swe574-group2 / swe574

This repository is created for the course named "SWE 574 - Software Development as a Team".

5 stars 0 forks source link

Configure Eureka to handle requests and responses for micro-services. #51

Closed okanmenevseoglu closed 7 years ago

okanmenevseoglu commented 7 years ago

Currently we can access to the methods from both 8080 and 8081 ports. However, with Eureka, we can also access our controllers from 1111 ports. (Ex.: localhost:1111/annotation and localhost:8080/annotation gives same results).
We must design the system in a way that request should follow the following order: Client->Incoming Request->Eureka->Security->Annotation->Output response->Eureka?->Client
Research about Eureka and micro-service architecture are needed.

penumbram-zz commented 7 years ago

This repo should give us an idea. For some reason, I'm getting different responses for GET localhost:8080/annotation and GET localhost:1111/annotation .

ardaofluoglu commented 7 years ago

When you first start the server and make a GET request to both: localhost:8080/annotation localhost:1111/annotation then you should be seeing an empty list returned.

If you make a POST to either server, than a GET on that server should return you a non-empty list. The other server will still return an empty list.

okanmenevseoglu commented 7 years ago

@ardaofluoglu @penumbram Yes, now I checked again and it seems that somehow we have 2 annotation databases, one works from 1111 and one works from 8080. That is a weird problem.

penumbram-zz commented 7 years ago

@okanmenevseoglu maybe we don't need to run the separate application at all. running the EurekaCatPlugInService applicaton works both services on port 1111 and 8080/8081 don't respond, which can be the behaviour we're looking for, can't it? (not sure what a micro service would look like)

penumbram-zz commented 7 years ago

Regarding commit 90e7089:

Fixes the duplicate servers problem (Now port 1111 does not respond, only the relevant port to the microservice (i.e. 8080 for annotation micro service) is responsive.)
Adds Discovery Client login for Eureka instances (localhost:1111 now requires the username: admin and password: 123456 denoted in eureka-server.yml)
EnableWebSecurity now works, Booting the apps, starting with Eureka server and moving to the clients, everything should seem in order to everyone. @okanmenevseoglu @ardaofluoglu @gr3ysky