amazon-ecs-java-microservices | reference architecture for java microservice | Microservice library

by aws-samples Java Version: Current License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | amazon-ecs-java-microservices Summary

amazon-ecs-java-microservices is a Java library typically used in Architecture, Microservice applications. amazon-ecs-java-microservices has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. However amazon-ecs-java-microservices build file is not available. You can download it from GitHub.

This is a reference architecture for java microservice on Amazon ECS

Support

Quality

Security

License

Reuse

Support

amazon-ecs-java-microservices has a low active ecosystem.

It has 338 star(s) with 297 fork(s). There are 79 watchers for this library.

It had no major release in the last 6 months.

There are 10 open issues and 4 have been closed. On average issues are closed in 51 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of amazon-ecs-java-microservices is current.

Quality

amazon-ecs-java-microservices has 0 bugs and 0 code smells.

Security

amazon-ecs-java-microservices has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

amazon-ecs-java-microservices code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

amazon-ecs-java-microservices is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

amazon-ecs-java-microservices releases are not available. You will need to build from source code and install.

amazon-ecs-java-microservices has no build file. You will be need to create the build yourself to build the component from source.

amazon-ecs-java-microservices saves you 3427 person hours of effort in developing the same functionality from scratch.

It has 7993 lines of code, 597 functions and 192 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed amazon-ecs-java-microservices and discovered the below as its top functions. This is intended to give you an instant insight into amazon-ecs-java-microservices implemented functionality, and help decide if they suit your requirements.

Ensures that the object is valid .
Get a Pet by name
Parses a PetType string .
The list of specialties .
Add custom cache manager customizer
Gets the tail list .
Get the visits for a pet .
Gets the list of visited visits .
The home endpoint
Sets the id of the pet .

Get all kandi verified functions for this library.

amazon-ecs-java-microservices Key Features

No Key Features are available at this moment for amazon-ecs-java-microservices.

amazon-ecs-java-microservices Examples and Code Snippets

No Code Snippets are available at this moment for amazon-ecs-java-microservices.

Community Discussions

Trending Discussions on amazon-ecs-java-microservices

ECS + ALB - My applications only respond a few times

QUESTION

ECS + ALB - My applications only respond a few times

Asked 2019-Sep-04 at 13:16

I've developed two spring boot applications for microservices and I've used ECS to deploy these applications into containers. To do this, I followed the official pet clinic example (https://github.com/aws-samples/amazon-ecs-java-microservices/tree/master/3_ECS_Java_Spring_PetClinic_CICD). All seems to works correctly, but when I make a request to the ALB very often I receive the 502 or 503 HTTP error and a few times I can see the correct response of the applications. Can someone help me? Thanks in advance.

...

ANSWER

Answered 2019-Sep-04 at 13:16

You receive a 502 when you have no healthy task running and 503 when task is starting/restarting.

All of this mean that your task got stopped and then your cluster restart it, so you should find what make your task failed.

It can be something directly in your code that make it crash. or it can be the cluster healthcheck defined in your target group that failed.

Firstly you should look your task in the AWS ECS Console and see what error your task receive when it's stopped.

But as you are able to make request for some time and then it failed. I pretty sure your problem come from your healthcheck. So go in your target group used by the task (in AWS EC2 Console) and make sure the healthcheck path configured exist and returned a 200 status code.

Source https://stackoverflow.com/questions/57786244

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install amazon-ecs-java-microservices

You can download it from GitHub.
You can use amazon-ecs-java-microservices like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the amazon-ecs-java-microservices component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: