Tuesday, 15 March 2011

php - Multiple applications under one domain website best architecture -



php - Multiple applications under one domain website best architecture -

i developing internal website consists of around 30 individual utilities (and more added in future). trying laravel. best practice this?

here characteristics of website.

some utilities big plenty considered individual applications some small, displaying static info without user interaction, database interaction some display dynamic contents result of interaction users some crud utilities each utility has own permission, , each user has different sets of permissions with 1 login, user should able access utilities he/she permitted use each utility interacts different tables in different databases.they have tables beingness used in common, rare case

currently, have separate controller, model, view each utility, makes mvc pattern useless.i thought of making each utility bundle, violates dryness(i have repeat parts of code).

what best way build website?

putting 1 single monolithic application may fine time being, nowadays challenges in future. has beingness able release individual applications separately.

if design have scratch, looking @ this:

base framework, extended of existing framework components added mutual applications. framework should versioned , linked each application (using svn external). each application take framework version using in case alter presents break 1 or more applications.

single signon, if have existing ldap server, domain controller, google apps, utilize basic authentication of applications.

all applications access same database or info stores.

you may able centralize permissions command depends. rather unwieldy @ same time give 1 place handle permissions. maybe allow each app publish permissions needs.

php architecture laravel

No comments:

Post a Comment