Do frameworks slow down the system? [closed]
up vote
-6
down vote
favorite
Do frameworks slow down the system?
I know this is a silly question but is it true that using different frameworks in front-end and back-end slow both the server or the client?
Thanks in advance!
django reactjs laravel flask
asked Nov 10 at 14:18
Saheb Giri
1
New contributor
Saheb Giri is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
closed as too broad by apokryfos, Graham, pirho, Saumini Navaratnam, Nguyễn Thanh Tú Nov 10 at 15:51
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
up vote
-6
down vote
favorite
Do frameworks slow down the system?
I know this is a silly question but is it true that using different frameworks in front-end and back-end slow both the server or the client?
Thanks in advance!
django reactjs laravel flask
asked Nov 10 at 14:18
Saheb Giri
1
New contributor
Saheb Giri is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
closed as too broad by apokryfos, Graham, pirho, Saumini Navaratnam, Nguyễn Thanh Tú Nov 10 at 15:51
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
Why should this be the case?
– trixn
Nov 10 at 14:27
Yes, frameworks do add some overhead but it's usually a few ms and once your application is complex enough you end up adding that same overhead for initialization anyway. .
– apokryfos
Nov 10 at 14:48
Not really. There is some overhead from using a framework, yes, but the actual bottlenecks in a production application are almost never the framework itself (most commonly they are inefficient database queries or third party API requests, and frameworks often provide tools to help mitigate these). Benchmarks are usually for "Hello, World" applications and don't often reflect real-world usage. Also, with something like bog-standard PHP pages it's all too easy to introduce all sorts of problems which a framework guards against.
– Matthew Daly
Nov 11 at 10:10
add a comment |
up vote
-6
down vote
favorite
up vote
-6
down vote
favorite
Do frameworks slow down the system?
I know this is a silly question but is it true that using different frameworks in front-end and back-end slow both the server or the client?
Thanks in advance!
django reactjs laravel flask
asked Nov 10 at 14:18
Saheb Giri
1
New contributor
Saheb Giri is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Do frameworks slow down the system?
I know this is a silly question but is it true that using different frameworks in front-end and back-end slow both the server or the client?
Thanks in advance!
django reactjs laravel flask
django reactjs laravel flask
asked Nov 10 at 14:18
Saheb Giri
1
New contributor
Saheb Giri is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 10 at 14:18
Saheb Giri
1
New contributor
Saheb Giri is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 10 at 14:18
Saheb Giri
1
New contributor
Saheb Giri is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 10 at 14:18
Saheb Giri
1
asked Nov 10 at 14:18
Saheb Giri
1
1
New contributor
Saheb Giri is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Saheb Giri is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Saheb Giri is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
closed as too broad by apokryfos, Graham, pirho, Saumini Navaratnam, Nguyễn Thanh Tú Nov 10 at 15:51
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as too broad by apokryfos, Graham, pirho, Saumini Navaratnam, Nguyễn Thanh Tú Nov 10 at 15:51
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
Why should this be the case?
– trixn
Nov 10 at 14:27
Yes, frameworks do add some overhead but it's usually a few ms and once your application is complex enough you end up adding that same overhead for initialization anyway. .
– apokryfos
Nov 10 at 14:48
Not really. There is some overhead from using a framework, yes, but the actual bottlenecks in a production application are almost never the framework itself (most commonly they are inefficient database queries or third party API requests, and frameworks often provide tools to help mitigate these). Benchmarks are usually for "Hello, World" applications and don't often reflect real-world usage. Also, with something like bog-standard PHP pages it's all too easy to introduce all sorts of problems which a framework guards against.
– Matthew Daly
Nov 11 at 10:10
add a comment |
Why should this be the case?
– trixn
Nov 10 at 14:27
Yes, frameworks do add some overhead but it's usually a few ms and once your application is complex enough you end up adding that same overhead for initialization anyway. .
– apokryfos
Nov 10 at 14:48
Not really. There is some overhead from using a framework, yes, but the actual bottlenecks in a production application are almost never the framework itself (most commonly they are inefficient database queries or third party API requests, and frameworks often provide tools to help mitigate these). Benchmarks are usually for "Hello, World" applications and don't often reflect real-world usage. Also, with something like bog-standard PHP pages it's all too easy to introduce all sorts of problems which a framework guards against.
– Matthew Daly
Nov 11 at 10:10
Why should this be the case?
– trixn
Nov 10 at 14:27
Why should this be the case?
– trixn
Nov 10 at 14:27
Yes, frameworks do add some overhead but it's usually a few ms and once your application is complex enough you end up adding that same overhead for initialization anyway. .
– apokryfos
Nov 10 at 14:48
Yes, frameworks do add some overhead but it's usually a few ms and once your application is complex enough you end up adding that same overhead for initialization anyway. .
– apokryfos
Nov 10 at 14:48
Not really. There is some overhead from using a framework, yes, but the actual bottlenecks in a production application are almost never the framework itself (most commonly they are inefficient database queries or third party API requests, and frameworks often provide tools to help mitigate these). Benchmarks are usually for "Hello, World" applications and don't often reflect real-world usage. Also, with something like bog-standard PHP pages it's all too easy to introduce all sorts of problems which a framework guards against.
– Matthew Daly
Nov 11 at 10:10
Not really. There is some overhead from using a framework, yes, but the actual bottlenecks in a production application are almost never the framework itself (most commonly they are inefficient database queries or third party API requests, and frameworks often provide tools to help mitigate these). Benchmarks are usually for "Hello, World" applications and don't often reflect real-world usage. Also, with something like bog-standard PHP pages it's all too easy to introduce all sorts of problems which a framework guards against.
– Matthew Daly
Nov 11 at 10:10
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Why should this be the case?
– trixn
Nov 10 at 14:27
Yes, frameworks do add some overhead but it's usually a few ms and once your application is complex enough you end up adding that same overhead for initialization anyway. .
– apokryfos
Nov 10 at 14:48
Not really. There is some overhead from using a framework, yes, but the actual bottlenecks in a production application are almost never the framework itself (most commonly they are inefficient database queries or third party API requests, and frameworks often provide tools to help mitigate these). Benchmarks are usually for "Hello, World" applications and don't often reflect real-world usage. Also, with something like bog-standard PHP pages it's all too easy to introduce all sorts of problems which a framework guards against.
– Matthew Daly
Nov 11 at 10:10