Challenge Overview
Previously, we have created AWS Lambda Function for Adding Payment for a member, which works against Informix Database and EJBs calls. But we decides to move away from AWS Lambda and AWS API Gateway. We'd like to use our own microservice architecture, which uses dropwizard.
For this challenge, we'd like you to create a new microservice by reimplementing the same logic as AWS Lambda functions (source code will be provided in forum). For how to create new microservice, we will provide a codebase for reference. Please raise any question if you have.
1. Implement the logic as in AWS Lambda Functions, please follow the formal way used in the current microservice (provided in forum for reference), you can also check https://github.com/appirio-tech/tc-common-tutorials/tree/master/microservice for general guide.
2. Please use payment or Payment as the name base, like payment-service.yaml, com.appirio.service.payment as the main package etc.
2. Configurations should be put in src/main/resources/payment-service.yaml
3. Describe the new API using apiary.apib
4. Update the pom.xml to include the new libraries, For required libraries, use a lib directory to store them, since we don't have them in maven repositories yet.
About Testing
For this microservice, VM is required for testing.
In order to request your VM, please request your VM in the challenge forum.
For this challenge, we'd like you to create a new microservice by reimplementing the same logic as AWS Lambda functions (source code will be provided in forum). For how to create new microservice, we will provide a codebase for reference. Please raise any question if you have.
1. Implement the logic as in AWS Lambda Functions, please follow the formal way used in the current microservice (provided in forum for reference), you can also check https://github.com/appirio-tech/tc-common-tutorials/tree/master/microservice for general guide.
2. Please use payment or Payment as the name base, like payment-service.yaml, com.appirio.service.payment as the main package etc.
2. Configurations should be put in src/main/resources/payment-service.yaml
3. Describe the new API using apiary.apib
4. Update the pom.xml to include the new libraries, For required libraries, use a lib directory to store them, since we don't have them in maven repositories yet.
About Testing
For this microservice, VM is required for testing.
In order to request your VM, please request your VM in the challenge forum.
Information about VM can be found below:
VM specific information is found here: http://www.topcoder.com/wiki/display/docs/VM+Image+2.5
Upon registration as a submitter or reviewer you will need to request a VM based on the new TopCoder Cockpit/Direct image. To request your image, please use the forum. Before requesting your VM, you need to ensure that you have an SSH key created and in your member profile. If you don't have your SSH key set in your profile, please follow https://help.github.com/articles/generating-an-ssh-key/, and send the public ssh key to support@topcoder.com, once it is setup, you can request your VM in forum
Final Submission Guidelines
1. Complete Source Code for this microservice2. A README.md in the root directory for general steps to setup and run the microservice
3. Verification Document About how to carry out the testing