Microservice is a service-oriented architecture where an application is deployed as a collection of loosely-coupled services. The goal is to make each service independent, fine-grained, scalable and flexible which allows faster testing and release.

This project takes advantage of the AWS infrastructure and it's services such as:

• ECR - docker registry
• ECS - service orchestration for service deployment, management, scaling, monitoring, etc
• AppMesh - service mesh that provides application level networking (normally used between internal services)
• Load Balancer - use for external client connection

applicant-services - Dummy service that returns a list of applicant names.

@GetMapping("/profiles")
public List<String> getApplicantsByJob() {
 
    log.debug("port={} get applicants by job", port);
    return Arrays.asList("Steve", "Bill", "Linus");
}

job-services - Dummy service that returns a job title with a list of applicant names.

@GetMapping("/profiles")
public ResponseEntity listJobsWithApplicantProfiles() {
 
    log.debug("get job details with applicants");
 
    JobWithApplicantsDto result = new JobWithApplicantsDto();
    result.setJob("Java Developer");
 
    result.setApplicants(applicantProxy.getApplicantsByJob());
 
    return ResponseEntity.ok().body(result);
}

• spring-cloud-starter-openfeign - this library is used for referencing a service in the naming server

To enable this feature, @EnableFeignClients must be annotated to a configuration class.

To call an endpoint from another service, an interface must be created with the same method signature as the method from the other service. In this example, we are importing 2 endpoints from the applicant-service.

@FeignClient(name = "applicant-services")
public interface ApplicantProxy {
 
    @GetMapping("/applicants/profiles")
    List<String> getApplicantsByJob();
 
    @GetMapping("/applicants/top")
    public List<String> getTopApplicantsByJob();
}

• spring-cloud-starter-sleuth - this library helps us trace our requests across different microservices by automatically adding a unique id to the logs.

As we can see in the logs, it started from api-gateway, pass thru job-services, and then application-services. In the 3 logs, notice the common unique id: 3b4039e47fb602a9. We can use this when tracing a request.

• applicant-services
• job-services

• czetsuyatech.lab (API, VPC)

• dev-vn-applicant-services
• dev-vn-job-services

• dev-vs-applicant-services
• dev-vs-job-services

Cluster - dev-layer3-businessservices

• Service - dev-service-applicant-services
• Task Definition - dev-td-applicant-services

Containers

• aws-xray-daemon amazon/aws-xray-daemon:1
• envoy

Environment Variables

• ENVOY_LOG_LEVEL=trace
• ENABLE_ENVOY_XRAY_TRACING=1
• XRAY_DAEMON_PORT=2000

Parameter Store

APPLICATION_SERVICE_URL=/dev/applicant-services/APPLICATION_SERVICE_URL=http://applicant-services.czetsuyatech.lab:8081

• Service - dev-service-job-services
• Task Definition - dev-td-job-services

Containers

• aws-xray-daemon amazon/aws-xray-daemon:1
• envoy

Environment Variables

• ENVOY_LOG_LEVEL=trace
• ENABLE_ENVOY_XRAY_TRACING=1
• XRAY_DAEMON_PORT=2000

• http://localhost:8081/applicants/profiles
• http://localhost:8081/applicants/top

• http://localhost:8080/jobs/profiles
• http://localhost:8080/jobs/top