Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= Newsgroups: comp.lang.java.programmer Subject: Re: API vc MVC Date: Mon, 27 Jul 2015 22:40:21 -0400 Organization: Aioe.org NNTP Server Lines: 18 Message-ID: References: <6a96955c-6b2a-416e-9be1-8c5bcc12ff3e@googlegroups.com> NNTP-Posting-Host: bLmKSxgyEsD8qtT7wjgUDQ.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 X-Notice: Filtered by postfilter v. 0.8.2 X-Mozilla-News-Host: news://nntp.aioe.org Xref: csiph.com comp.lang.java.programmer:32175 On 5/11/2015 10:04 PM, Leonan Luppi wrote: > I have a sad doubt about this subject's. Today what is better? > > Use MVC Pattern and consuming request to load my view or just create > an API which any client can access (my environment, my front-end will > be AngularJS or any javascript MV* framework). I mean what can be > more scalable, performatic? I would go for the JavaScript application and JAX-RS web services server side. Technically I think it will become a maintenance nightmare for the client side code, but the reality is that this is the way the industry is going, so this is the solution that all the young developers you hire the next 10 years will know. Arne