Skip to main content
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

I think your question is architectural in its nature, and it's rather hard to tell whether you want to prerender as much as you can on server side (meaning via PHP) or do most of the work on the client (i.e. via Angular.js). Each approach has its pros and cons.

Here areHere are a few sources that may help you form your opinion about whether to go

  • client-heavy (would be my default pick)
  • server-heavy
  • spread complexity across layers (I'm really not a fan of having bits and pieces of scattered business logic).

To get a more definitive answer about which way to go, you would really need to provide the list of both functional and non-functional requirements to your system.

I think your question is architectural in its nature, and it's rather hard to tell whether you want to prerender as much as you can on server side (meaning via PHP) or do most of the work on the client (i.e. via Angular.js). Each approach has its pros and cons.

Here are a few sources that may help you form your opinion about whether to go

  • client-heavy (would be my default pick)
  • server-heavy
  • spread complexity across layers (I'm really not a fan of having bits and pieces of scattered business logic).

To get a more definitive answer about which way to go, you would really need to provide the list of both functional and non-functional requirements to your system.

I think your question is architectural in its nature, and it's rather hard to tell whether you want to prerender as much as you can on server side (meaning via PHP) or do most of the work on the client (i.e. via Angular.js). Each approach has its pros and cons.

Here are a few sources that may help you form your opinion about whether to go

  • client-heavy (would be my default pick)
  • server-heavy
  • spread complexity across layers (I'm really not a fan of having bits and pieces of scattered business logic).

To get a more definitive answer about which way to go, you would really need to provide the list of both functional and non-functional requirements to your system.

deleted 1 character in body
Source Link
mdfst13
  • 21.7k
  • 6
  • 33
  • 68

I think your question inis architectural in it'sits nature, and it's rather hard to tell whether you want to prerender as much as you can on server side (meaning via PHP) or do most of the work on the client (i.e. via Angular.js). Each approach has its pros and cons.

Here are a few sources that may help you form your opinion about whether to go

  • client-heavy (would be my default pick)
  • server-heavy
  • spread complexity across layers (I'm really not a fan of having bits and pieces of scattered business logic).

To get a more definitive answer about which way to go, you would really need to provide the list of both functional and non-functional requirements to your system.

I think your question in architectural in it's nature, and it's rather hard to tell whether you want to prerender as much as you can on server side (meaning via PHP) or do most of the work on the client (i.e. via Angular.js). Each approach has its pros and cons.

Here are a few sources that may help you form your opinion about whether to go

  • client-heavy (would be my default pick)
  • server-heavy
  • spread complexity across layers (I'm really not a fan of having bits and pieces of scattered business logic).

To get a more definitive answer about which way to go, you would really need to provide the list of both functional and non-functional requirements to your system.

I think your question is architectural in its nature, and it's rather hard to tell whether you want to prerender as much as you can on server side (meaning via PHP) or do most of the work on the client (i.e. via Angular.js). Each approach has its pros and cons.

Here are a few sources that may help you form your opinion about whether to go

  • client-heavy (would be my default pick)
  • server-heavy
  • spread complexity across layers (I'm really not a fan of having bits and pieces of scattered business logic).

To get a more definitive answer about which way to go, you would really need to provide the list of both functional and non-functional requirements to your system.

Source Link

I think your question in architectural in it's nature, and it's rather hard to tell whether you want to prerender as much as you can on server side (meaning via PHP) or do most of the work on the client (i.e. via Angular.js). Each approach has its pros and cons.

Here are a few sources that may help you form your opinion about whether to go

  • client-heavy (would be my default pick)
  • server-heavy
  • spread complexity across layers (I'm really not a fan of having bits and pieces of scattered business logic).

To get a more definitive answer about which way to go, you would really need to provide the list of both functional and non-functional requirements to your system.