How triledinh159/project-future-tech works
This project is a full-stack solution built for an innovation challenge – it combines a mobile app that reads NFC signals (built with React Native, as seen in the “nfc_xelvis64_1” directory with its Android, iOS, src, and configuration files) with a backend hosted on AWS. The backend code is split between directories such as “AWS-Cloud-Training” and “AWSLambda,” which contain Python scripts and Lambda functions that interact with AWS services (for example, DynamoDB, S3, and Amazon Rekognition). The README confirms that the idea was to provide a more “convenient” payment solution using NFC technology for parking transactions.
Main Components
a. Mobile Frontend:
• The React Native mobile application (located under “nfc_xelvis64_1”) that handles NFC signal reading and user interactions.
b. AWS Backend Services:
• AWS Lambda functions – the Python scripts in “AWSLambda” (and similar code in “AWS-Cloud-Training”) represent serverless functions.
• AWS DynamoDB – used for storing transaction or user data.
• AWS S3 (or similar storage) – for storing assets or intermediary data.
c. Data Flow & Integration:
• Possibly an API Gateway (or similar integration layer) that triggers the Lambda functions from the mobile app.
• Event processors that check or update data (evident from files such as “checkdata.py” and “putBasictoDB.py”).
• “AWS Lambda” block(s) – note that there might be multiple functions (e.g., “checkData”, “texttoDB”, “putBasictoDB”) that process the incoming data.
• Link the Lambda functions with the “DynamoDB” component (for data storage) and the “S3 Bucket/ Rekognition” component (for storage of artifacts and image processing).
• If applicable, include an “AWS Cloud Training” block to represent testing or additional backend training functions.
• Certificate component (the tech.pdf file under AWSLambda/cert) to show that the solution’s technical quality was recognized.
Architectural Patterns and Design Principles
• Use of a serverless architecture for the backend using AWS Lambda.
• That the frontend and backend are decoupled, where the mobile app does not need to manage server infrastructure.
• Use of event-driven integration, as the Lambda functions are triggered by data events from the mobile app (or API endpoints).
• Security and scalability aspects where appropriate (for instance, AWS managed services increase scalability and reliability).
Technologies & Frameworks
• For the mobile app, list “React Native”, along with supporting technologies like Redux or navigators if known.
• For the backend, show “AWS Lambda”, “DynamoDB”, “S3 Bucket”, and “Amazon Rekognition”. Optionally include “API Gateway” if used.