feature: resolved challenge

README.md

@@ -1,3 +1,15 @@
+# Solution
+
+To solve the technical challenge, apply everything requested, first create a microservice that subscribes to Kafka topics and with this can create transactions in the DB and in the respective Topic and the second microservice is responsible for subscribing to the Kafka topic. creation to obtain the amount and be able to validate whether it is fraudulent or not according to the condition provided, in case the fraud microservice is restarted it will resume all the requests that were pending to analyze whether or not it was a fraud, the technological stack en Reactive programming with Java 17 (webflux), as well as GraphQL, H2 database with JPA, were used for the requests.
+
+# Deploy Local
+
+To deploy only run "docker compose up --build -d" with this command all microservices and components will be start and ready for use.
+
+# Test
+
+You can test the endpoints of microservices with the postman collection, it's located in directory "postman"
+
 # Yape Code Challenge :rocket:
 
 Our code challenge will let you marvel us with your Jedi coding skills :smile:. 
@@ -12,24 +24,24 @@ Don't forget that the proper way to submit your work is to fork the repo and cre
 
 # Problem
 
-Every time a financial transaction is created it must be validated by our anti-fraud microservice and then the same service sends a message back to update the transaction status.
-For now, we have only three transaction statuses:
+Every time a financial transactions is created it must be validated by our anti-fraud microservice and then the same service sends a message back to update the transactions status.
+For now, we have only three transactions statuses:
 
 <ol>
   <li>pending</li>
   <li>approved</li>
   <li>rejected</li>  
 </ol>
 
-Every transaction with a value greater than 1000 should be rejected.
+Every transactions with a value greater than 1000 should be rejected.
 
 ```mermaid
   flowchart LR
     Transaction -- Save Transaction with pending Status --> transactionDatabase[(Database)]
-    Transaction --Send transaction Created event--> Anti-Fraud
-    Anti-Fraud -- Send transaction Status Approved event--> Transaction
-    Anti-Fraud -- Send transaction Status Rejected event--> Transaction
-    Transaction -- Update transaction Status event--> transactionDatabase[(Database)]
+    Transaction --Send transactions Created event--> Anti-Fraud
+    Anti-Fraud -- Send transactions Status Approved event--> Transaction
+    Anti-Fraud -- Send transactions Status Rejected event--> Transaction
+    Transaction -- Update transactions Status event--> transactionDatabase[(Database)]
 ```
 
 # Tech Stack
@@ -44,7 +56,7 @@ We do provide a `Dockerfile` to help you get started with a dev environment.
 
 You must have two resources:
 
-1. Resource to create a transaction that must containt:
+1. Resource to create a transactions that must containt:
 
 ```json
 {
@@ -55,7 +67,7 @@ You must have two resources:
 }
 ```
 
-2. Resource to retrieve a transaction
+2. Resource to retrieve a transactions
 
 ```json
 {
@@ -73,12 +85,14 @@ You must have two resources:
 
 ## Optional
 
-You can use any approach to store transaction data but you should consider that we may deal with high volume scenarios where we have a huge amount of writes and reads for the same data at the same time. How would you tackle this requirement?
+You can use any approach to store transactions data but you should consider that we may deal with high volume scenarios where we have a huge amount of writes and reads for the same data at the same time. How would you tackle this requirement?
 
 You can use Graphql;
 
 # Send us your challenge
 
 When you finish your challenge, after forking a repository, you **must** open a pull request to our repository. There are no limitations to the implementation, you can follow the programming paradigm, modularization, and style that you feel is the most appropriate solution.
 
-If you have any questions, please let us know.
+If you have any questions, please let us know.
+
+