Database vs static html files for storage solution (Site Builder) -


project description:
learning exercise asp mvc 4, i'm creating site builder / multitenancy site. it's nothing fancy wysiwyg editing on templates custom routing direct users correct template based on subdomain. usr1.mysite.com directed template edited usr1. main concern @ moment method of storing edited templates.

storage dilemma:
@ first going make templates views , store changes made user in database. when usr1's template displayed system pull view , populate usr1's data.

instead i've implemented system takes user's modified template , saves whole thing static html files in file system. path usr1's site (and other details) saved in database. when usr1.mysite.com called have "content" controller retrieve correct html file.

question:
there reason choose database/view method on static html file method? i'm not concerned having dynamic content in end user pages. 1 reason tried file method.

decision (edit):
i'm implementing file method. after more research (verifying previous research), have few doubts file system have trouble few hundred sites. structure in way group user data directories group directories based on naming convention i've yet dream up, 000usr1, 000usr2 in 000 group directory. goal of less 100 files/folders in given directory , less 4 levels deep. should give me capability of holding 10000 sites. have no plans of having activity near level software, want , running , torture awhile , see it's capable of handling. if expresses interest i'll post results.


Comments

Popular posts from this blog

javascript - RequestAnimationFrame not working when exiting fullscreen switching space on Safari -

Python ctypes access violation with const pointer arguments -