php - MVC style application architecture catering to API -


i'm working on "community" style website, both fun , profit, , while aesthetic element of coming along nicely, haven't yet sunk teeth working out application logic reasons of unsureness in approach.

i'm creating php powered mvc style framework can reuse components of, i've noticed many existing mvc frameworks use sort of "convention on configuration" expedite whole process. queries intend run little more complicated select * entity_name.

i want design application in layers, api calls can made server. figured instead of doing twice, build site controllers on top of layer, follows standard. allow ajax calls, remote web application calls, etc., follow same route of request normalization , response document web requests.

anyways, perhaps of unnecessary detail, can shed light on api layered mvc architectures of nature? since api level (the model layer) data read/written, want incorporate authentication @ level, or abstract higher level , make entry point? other considerations should make haven't mentioned?

i know still have reading do, suggestions reading materials, or advice personal experience welcome. in advance.

this question. think best bet use soa approach rest resources as possible if website gets lot of hits, might worth segregating state mutating state exposing, first can use more complex oo approach whilst other can use simple dtos (in form of arrays) , retrieve data database using custom queries.


Comments

Popular posts from this blog

linux - Mailx and Gmail nss config dir -

c# - Is it possible to remove an existing registration from Autofac container builder? -

php - Mysql PK and FK char(36) vs int(10) -