Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance and Reliability #73

Closed
Tracked by #69
mervegrbz opened this issue Mar 27, 2023 · 6 comments
Closed
Tracked by #69

Performance and Reliability #73

mervegrbz opened this issue Mar 27, 2023 · 6 comments
Assignees
Labels
effort: level 1 How much effort is needed for this task priority: critical Issue must be fixed ASAP, cannot be postponed state: assigned This task is currently assigned to a contributor type: documentation Improvements or additions to documentation
Milestone

Comments

@mervegrbz
Copy link
Contributor

mervegrbz commented Mar 27, 2023

Performance and Reliability section in the requierements should be written clearly to the requirements page

@egecans egecans added this to the Requirements milestone Mar 27, 2023
@mervegrbz mervegrbz added type: documentation Improvements or additions to documentation state: assigned This task is currently assigned to a contributor priority: critical Issue must be fixed ASAP, cannot be postponed effort: level 1 How much effort is needed for this task labels Mar 27, 2023
@bgmrsln
Copy link
Contributor

bgmrsln commented Mar 27, 2023

I have added the following requirements:

  • 2.4.1. Response time: The system should respond to user requests within 5 seconds.
  • 2.4.2. Throughput: The system should be able to handle a minimum of 500 concurrent users.
  • 2.4.3. User Accounts: The platform shall support at least 5000 user accounts.
  • 2.4.4. Fault Tolerance: The system should be designed to recover quickly from any failure, and data should not be lost during failures.
  • 2.4.5. Capacity: The system should be designed to handle a large volume of data and user requests without any slowdowns.
  • 2.4.6. Data integrity: The system should ensure that all data stored is accurate, complete, and consistent.
    I used should for performance so as not to burden. Also I am not sure how much performance is expected from us. Can you review it? @mervegrbz

@mervegrbz
Copy link
Contributor Author

I think, response time and capacity explains our main goal. But the app can have a serious traffic in the first moments of disasters, So having a scalable server is a must for us. We need data to measure user traffic of disaster websites so I am not sure, neither 😢. Ellerine sağlıkkk 🚀

@mehmetkuzu
Copy link
Contributor

We can add a requirements in should form (even shall) to backup the server operation.

2.4.7. Backup servers for availability: All servers (application servers, database servers etc) should have a backup in different locations. A real time mirroring of these parallel servers should be a requirement.

Reason for this: Disasters might occur in such a way that our server is also affected.

@bgmrsln
Copy link
Contributor

bgmrsln commented Mar 28, 2023

We can add a requirements in should form (even shall) to backup the server operation.

2.4.7. Backup servers for availability: All servers (application servers, database servers etc) should have a backup in different locations. A real time mirroring of these parallel servers should be a requirement.

Reason for this: Disasters might occur in such a way that our server is also affected.

I thought of it but I think it should be inside Backup and Recovery

@mehmetkuzu
Copy link
Contributor

@egecans we talked about that in the closs.
Actually it is about Availability. So Egecan will add it there.

@mehmetkuzu
Copy link
Contributor

@egecans I guess "should" is enough for this. (Not shall)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort: level 1 How much effort is needed for this task priority: critical Issue must be fixed ASAP, cannot be postponed state: assigned This task is currently assigned to a contributor type: documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

4 participants