Model–View–Controller (MVC) is a software pattern for implementing user interfaces. It divides a given software application into three interconnected parts to separate internal representations from how information is presented to or accepted by the user.
Whenever the user visits a website or interacts with a web application, clicks on a link, the browser sends an HTTP request to the server. The web applications Router file handles this request from the server. The Router acts as a sort of traffic controller for incoming HTTP requests. It decides which Controller to send the HTTP request to and in the route.rb …
As developers, we often need to gather data from external sources for use in our programs. Fortunately, in recent years, the Fetch API has made retrieving, adding, editing, and removing data from external databases more accessible than ever before. This…
So what is API? No, it’s not your favorite beverage at your local bar. API stands for Application Programming Interface. API’s essentially allow a developer to speak to another application online. API’s are built on existing applications. Usually, big companies make an API to enable developers to build applications that connect either by sending information to it, getting information from it, or both. Before, API’s businesses would have to go to Visa, Mastercard, or banks to get access to make payment transactions. Now developers can build software that handles payment transactions from an application without the hassle.
Let’s start with the biggest similarity between these two concepts. Both frameworks and libraries are reusable codes written by one or more developers that are used to help solve common problems. The biggest difference may seem strange, but it follows the “Hollywood principle”.
Library says: Just call me when you need me.
Framework says: Don’t call me, I’ll call you.
When you use a library, you are in charge of the flow of the application. You are choosing when and where to call the library.
When you use a framework, the framework is in charge of the flow…
Before talking about Git, let’s define what is version control. It is a system that records changes to a file or set of files over time so that you can recall specific versions later. Git was created by Linux kernel and it is a distributed version control system, originally designed for coordinating work among software engineers cooperating on source code during software development.
In complex projects, where multiple people might be making changes to the same files simultaneously, it’s easy to get into a weird state. …
ORM stands for Object-Relational Mapping and it is a programming technique that abstracts your code from the database behind it. When we work with an object-oriented system, there is mismatch between the object model and the relational database. RDBMSs represent data in a tabular format whereas object-oriented languages represent it as an interconnected graph of objects.
Simply put, if you’re building an application using an ORM library and your application speaks with PostgreSQL, you could switch to MariaDB at anytime without changing your code. You would only need to change data source configuration.
Let’s break this down with an example…
Object-oriented programming is one of the most common ways of writing code and, one of the best-known paradigms out there. The moment you start learning to code anywhere OOP is usually covered.
The four basic principles of object-oriented programming:
Encapsulation — the process of bundling data and operations done on the data together into a single unit. This is mechanism of hiding data implementation by restricting access. Usually, we have 3 main access specifiers:
Features of React