Technology Stack

Following is the purposed technology stack to use for Canonizer 3.0:

Frontend:

1. HTML5

2. CSS3 / Sass

3. Ant Design

4. React.js*

5. Redux toolkit (including Redux thunk, Redux-Slice, Redux Middleware, RTK Query)

6. Redux-orm

7. React Router

*Note: We would prefer react over Next.js because of following reasons:

1. React has a very big community of developers

2. React is fast as compared to Next.js

3. Many third party libraries do not support SSR

Backend:

1. PHP / Laravel (Laravel Socialite)

Database:

1. MySQL 

AWS

1. SNS (Simple Notification Service)

2. SES (Simple Email Service)

3. CW log (CloudWatch Logs)

4. CF (CloudFront)

5. EC2

6. ECR (Elastic Container Register)

7. ECS (Elastic Container Service)

8. ELB (Elastic load balancer)

9. S3 buckets

10. RDS

Container Service

1. Docker

Testing

1. Laravel PHPUnit

Version Control System:

1. Github (With CI/CD)

Issue Tracking Software

1. Jira / Github

Other Tools

1. Visual Studio Code

2. Postman / Swagger 

3. Workbench for Database Modeling

4. Figma  (interactable UI/UX)

5. Draw.io (ERD, Class Diagram, Flow Diagram)

Yes Brent. Good idea. We can certainly break them into multiple topic.

As requested, I am linking all of them to their reference URLs:

Backend/Server-Side Language: PHP Laravel Framework (7.x or +) (A framework upgrade will be required)

User & API Authentication: Laravel Passport Authentication + OAuth (for Google, Facebook, LinkedIn, Twitter, GitHub)

Services/API: Laravel Lumen Framework

Front-End: React.JS with Next.JS framework (can be discussed & validated)

Design Framework: Ant Design

Database: MYSQL 8.x (upgrade might be required)

Tree Snapshot/Caching: NoSQL like Amazon DynamoDB or MongoDB

Deployment: CI/CD Pipeline

Testing: Selenium WebDriver with Python + Laravel PHPUnit

Wow, thanks for this Sunny.  This proposal looks like a huge step forward with a design.

I'm thinking we should break each of these items into their own topic, then have a list topic, with a camp for each one, linking to it's actual topic.

Then people could rank the importance of each of these items in those camps, in the list topic, regardless of which side of that topic one is on.

Then people could indicate whether they support the building consensus being developed on each individual item or something else.

I'm not experienced with Ant Design, but it looks very exciting, so need to learn more.  It'd help if there were links to description pages for things like this, as I have added here.  Could we put all of this design info into that tool?

..adding few more:

Deployment: CI/CD Pipeline

Testing: Selenium WebDriver with Python + Laravel PHPUnit

Proposed Technologies

Backend/Server-Side Language: PHP Laravel Framework 7.x or + (A framework upgrade will be required)

User & API Authentication: Laravel Passport Authentication + OAuth (for Google, Facebook, LinkedIn, Twitter, GitHub)

Services/API: Laravel Lumen Framework

Front-End: React.JS with Next.JS framework (can be discussed & validated)

Design Framework: Ant Design

Database: MYSQL 8.x (upgrade might be required)

Tree Snapshot/Caching: NoSQL like Amazon DynamoDB or MongoDB

Hello Everyone, I have created this forum so that we can note down the minutes of the meeting here after every meeting and we can also add a recorded video link of the meeting.