Big Project Feature Check #3
Automatically Populated Github Issue
Standard Requirements
- Deployment, a full deployment of frontend and backend
- Key features must be deployed in order to be presented, localhost presentations are .55
- Multiple people need to be able to interact with features at the same time, data updates
- Searching/Sorting, 2 features must support searching and sorting from backend,
- 1 feature should have JPA build in sorting,
- 1 features should perform custom sort after retrieving backend data
- Extra. A feature that utilizes Stacks or Queues for ordering
Challenge Requirements
-
Mystery Enactment: SASS including dynamically switching features on and off (ie dark mode, colors), how to manage files and features in Version Control. Here are existing SASS documents basic and advanced. But, neither really go over architecture, so I think they are both basic.
-
Rachita Love Story: Websockets to support features like multiplayer and chat on Java, Python, and NodeJS. Here is original design guilde (outdated),here is code for NodeJS.
-
Rapping Directors: Login, Security, and CORS support for Java and Python, Here is Python guide, we should have something similar in Java. It would be best if it is broken into parts.
-
Giggle Juice: Dual Login / Dual Project / SIngle Frontend for both Python and Java in one project, share instance data (database), different DNS names. Never have tried this, putting a Java Project and Python project in same version control repository, sharing database. There are issues like database migration, build files, docker files and frontend logic to do two logins. I would start with Java project and add Python to it since Python seems more flexible in its directory locations.
-
Ballerina Mergers: RDS / SQLite switch for production, dynamic switching. I believe Adi is best person for former documentation. Here is 1st link, Here is hack link