Skip to main content

What and Why MVC(Model View Controller)?

As we know In an application there is thousands line of code and hundreds of files. In this environment we can't predict exactly that, changes in one section will affect how many other sections. For a programmer, it is difficult to manage it.

But if we notice, basically there is three part in any application:
  1. which user sees(interface)
  2. which handle interaction between the user and business logic
  3. code which interacts with the database(business logic)
As we manage things in our house as
  • One place for grocery products(kitchen)
  • Makeup and cosmetics are in one place
  • Medicines are in a fixed place
So we can get them with less effort on time. same way MVC works regarding code to which our ROR follows.

MVC(Model View Controller) is just a software architectural Pattern to manage code:
  1. View(User interface related code)
  2. Controller(bridge between view and model)
  3. Model(database related code and business logic)
According to MVC, View will never interact directly to Model. It will be the Controller who will decide that which section of view related to which Model part


  1. Review of Lucky Club Casino Site - Lucky Club Casino
    Lucky Club is a small, high-end casino that is open 24 hours a day and uses a standard operating system for its own selection of luckyclub games and  Rating: 9.5/10 · ‎Review by


Post a Comment


Popular posts from this blog

Why "F" and "L" suffix | (10.0F, 10L)

Let us take it this way, We will create their needs. So we will get why they are needed. Try to guess, which functions will be executed in the following program: public class MyClass {     public static void main(String args[]) {         MyClass obj = new MyClass();         obj.fun1(10);     }     void fun1(byte val){         System.out.println(val);     }     void fun1(int val){         System.out.println(val);     }     void fun1(float val){         System.out.println(val);     }     void fun1(long val){         System.out.println(val);     }     } It seems like every method is capable to run this program because 10 is still literal because It has no data type. Before Java, In previous technologies, this scenario gave an ambiguity error. But Java solves this problem by removing the concepts of literals. It means Java provide a data type immediately when these born. So here 10 is no more literal. Java provides Integer data type for it. So now it is of Integer t

only large files upload on S3 | Ruby On Rails

models/attachment.rb class Attachment < ApplicationRecord after_initialize :set_storage private def set_storage # larger that 5mb file would be upload on s3 if file . blob . byte_size > 5_000_000 Rails . application . config . active_storage . service = :amazon else Rails . application . config . active_storage . service = :local end end # end of private end

Typecasting | How is Long to Float Conversion possible?

We will take a brief description of Typecasting and will try to do focus on Log to Float Conversion. Typecasting: Assigning a value of one data type to another. When we assign a value of smaller data type to a bigger one. it is called Widening. Java did this conversion automatically as they are compatible. As shown in the following figure: One another kind of conversion, when automatic conversion not possible i.e. when they are not compatible is Shortening. It will be just opposite of above and diagram will be reversed. How is Long to Float Conversion possible? If we look carefully at the diagram, there is one conversion which looks questionable is Long(8 bytes) to Float(4 bytes) conversion. It looks like data lossy conversion. Actually, Type conversion does two things: Either change in range or change in behavior or both. Change in Range: short a = 3456 // this value can be varied within the range of -32768 to 32767 int b = a // now this value can be varied wi