# Lots of little MVCs or just one MVC?

**URL:** <https://forum.kirupa.com/t/lots-of-little-mvcs-or-just-one-mvc/294074>\
**Category:** Uncategorized\
**Created:** [August 7, 2009, 9:17pm UTC](https://forum.kirupa.com/t/lots-of-little-mvcs-or-just-one-mvc/294074 "2009-08-07T21:17:02Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![smeared](https://avatars.discourse-cdn.com/v4/letter/s/9de0a6/32.png) [@smeared](https://forum.kirupa.com/u/smeared)\
**Post date:** [August 7, 2009, 9:17pm UTC](https://forum.kirupa.com/t/lots-of-little-mvcs-or-just-one-mvc/294074/1 "2009-08-07T21:17:02Z")

</div>

ok… so say you’re building a website… with a few different simple applications. a slideshow, a mp3 player, and whatever else…

I’m completing my first MVC website, and I have one main question.

do i use one large model for the data of each individual application, or do i use many smaller models to hold the data specific to that application.

Of course that one sounds better… keeping the apps separate, and cleaner… but then what if i want the views to respond to events from another model??

do i “nest” complete mvc apps inside one large mvc app? is that the normal practice… thanks for any help.