Ruby on Rails development is basically a web application development framework which is normally written in Ruby. Rails MVC framework, provides default structures for databases, web services and web pages. It uses typical web standards like JSON or XML for data transfer, and HTML, CSS & JavaScript for User interface (UI/UX).
Ruby On Rails Technical overview
Like many of the web application development frameworks, Ruby on Rails generally uses the model view controller yupp it’s MVC to organize application programming.
In it’s default configuration, a model in the Ruby on Rails MVC framework maps a table in a database to a Ruby file.
Ruby on Rails Development includes serveral tools that make most of the web application or normal application development tasks easier , such as scaffolding that automatically build models and views which is needed for a basic website. Next is WEBrick is a Ruby library provides simple HTTP web server services. Both of these tools provide a basic ruby on rails development environment.
Ruby On Rails Framework structure
Ruby on Rails is divided into several various packages like ActiveRecord ( for database access using objects relational mapping), Active Resource (that generally provides all web services), Action Pack, Active Support and Action Mailer.
Ruby On Rails Deployment
Ruby on Rails is usually installed using RubyGems( a package manager which contains current versions of Ruby). Many free Unix systems also support Ruby on rails installation and its dependencies via native package management system.
Ruby on Rails is basically deployed with a database server such as MySQL or PostgreSQL and a web server such as Apache.
Ruby on Rails is basically emphasize on Convention over Configuration (CoC) where developer only needs to specify just unconventional aspects of the application and that’s it. and the Don’t Repeat Yourself (DRY) principle it means there’s one unambiguous place where all the the information is present or located.
“Convention over Configuration” means a developer only needs to specify unconventional aspects of the application. For example, if there is a class Sale in the model, the corresponding table in the database is called sales by default. It is only if one deviates from this convention, such as calling the table “products sold”, that the developer needs to write code regarding these names. Generally, Ruby on Rails conventions lead to less code and less repetition.
“Don’t repeat yourself” means that information is located in a single, unambiguous place. For example, using the ActiveRecord module of Rails, the developer does not need to specify database column names in class definitions. Instead, Ruby on Rails can retrieve this information from the database based on the class name.