Should i develop games using MVC architecture or is there other architecture for game development?
A passive implementation of MVC is pretty useful, MVC in the “normal” sense is too much.
Be wary of using a design pattern to use a design pattern, you should first build something and come to the conclusion yourself whether a design pattern fits your needs or not. Don’t try to pile on patterns because they’re easy to apply oppose to thinking up solutions yourself.
I love me some design patterns, but it’s all about getting to know what you’re doing first.
I personally take elements from Model-View-Controller and Entity-Component designs to achieve the following results, which I like:
- With components, you can develop entities more quickly
- With components, you can create generic controllers for updating/interacting with entities
- With the view aspect, you can decouple your rendering code from your game logic. I’m trying to keep these two in entirely separate projects sometimes. Really helps when it comes to writing for another operating system or graphics library.
We are using a custom MVC like framework for a game that in some way resembles Ember.js or AngularJS. For a game with a lot of UI, especially one that needs to be localized in different languages, it can be pretty good.
For most small indie games I would say getting too caught up in design patterns will just waste your time. 
I’ll just upload my code when its finished. I’ve tried to code it MVC like desing.