I do like David Packer's answer on your other question. But to distill it a bit more:

• Some Business Logic on front end to reduce round trips.

• But all Business Logic on back end (which, yes, means you will have duplicated business logic)

Also, forget about how difficult or not is to implement it on a language. You are taking an architectural decision independent of the language (you could use different languages if the difficulty to implement it is of actual concern to you).

I do like David Packer's answer on your other question. But to distill it a bit more:

• Some Business Logic on front end to reduce round trips.

• But all Business Logic on back end (which, yes, means you will have duplicated business logic)

Also, forget about how difficult or not is to implement it on a language. You are taking an architectural decision independent of the language (you could use different languages if the difficulty to implement it is of actual concern to you).

I do like David Packer's answer on your other question. But to distilled it a bit more:

• Some Business Logic on front end to reduce round trips.

• But all Business Logic on back end (which, yes, means you will duplicated business logic)

Also, forget about how difficult or not is to implement it on a language. You are taking an architectural decision independent of the language (you could use different languages if the difficulty to implement it is of actual concern to you).

I do like David Packer's answer on your other question. But to distill it a bit more:

• Some Business Logic on front end to reduce round trips.

• But all Business Logic on back end (which, yes, means you will have duplicated business logic)

Also, forget about how difficult or not is to implement it on a language. You are taking an architectural decision independent of the language (you could use different languages if the difficulty to implement it is of actual concern to you).