Mostrar el registro sencillo del ítem
Estudio Comparativo entre SQL Directo y un ORM.
| dc.contributor.advisor | Ruiz Parrales, Iván Rubén | |
| dc.contributor.author | Macias Carpio, Fersen Arturo | |
| dc.date.accessioned | 2023-10-24T17:02:44Z | |
| dc.date.available | 2023-10-24T17:02:44Z | |
| dc.date.issued | 2023 | |
| dc.identifier.uri | http://dspace.utb.edu.ec/handle/49000/14779 | |
| dc.description | Today, every application requires a database to function and store information about its customers, products, accounting, and other data necessary for its proper operation. Typically, the business logic of an application connects to the data source to perform read-write operations, and traditionally, SQL (Structured Query Language) has been used for this purpose as it was the only available option until the emergence of ORM (Object-Relational Mapping). From this point on, the decision to use one method over the other has become a topic of great interest in the software development field, as both approaches aim to access databases but differ in their implementation and developers' perceptions. SQL, which stands for Structured Query Language, is a programming language used to manage relational databases. It allows developers to write queries directly to the database, providing them with detailed control over how information is accessed and manipulated. SQL is widely accepted and used, especially in enterprise applications. On the other hand, ORM tools map objects from a programming language to tables in a relational database. They simplify interaction with the database by abstracting the complexity of SQL queries. Some popular examples of ORM include Hibernate for Java and Entity Framework for .NET. The level of acceptance among developers varies between SQL and ORM. Developers with database experience often prefer SQL, as it offers complete control and fine query optimization. However, ORM is more popular among developers who want a simpler, object-oriented way of working with databases. ORM is also useful in multidisciplinary teams where not everyone is an SQL expert. In terms of popularity, SQL remains the predominant choice in database development, especially in mission-critical applications. ORM is popular in web applications and projects where development speed is a priority. A comparative study between Direct SQL and ORM will help make a better decision on which technology to use to access the data source, depending on the specific project requirements, performance needs, portability, maintainability, and other relevant factors. | es_ES |
| dc.description | Today, every application requires a database to function and store information about its customers, products, accounting, and other data necessary for its proper operation. Typically, the business logic of an application connects to the data source to perform read-write operations, and traditionally, SQL (Structured Query Language) has been used for this purpose as it was the only available option until the emergence of ORM (Object-Relational Mapping). From this point on, the decision to use one method over the other has become a topic of great interest in the software development field, as both approaches aim to access databases but differ in their implementation and developers' perceptions. SQL, which stands for Structured Query Language, is a programming language used to manage relational databases. It allows developers to write queries directly to the database, providing them with detailed control over how information is accessed and manipulated. SQL is widely accepted and used, especially in enterprise applications. On the other hand, ORM tools map objects from a programming language to tables in a relational database. They simplify interaction with the database by abstracting the complexity of SQL queries. Some popular examples of ORM include Hibernate for Java and Entity Framework for .NET. The level of acceptance among developers varies between SQL and ORM. Developers with database experience often prefer SQL, as it offers complete control and fine query optimization. However, ORM is more popular among developers who want a simpler, object-oriented way of working with databases. ORM is also useful in multidisciplinary teams where not everyone is an SQL expert. In terms of popularity, SQL remains the predominant choice in database development, especially in mission-critical applications. ORM is popular in web applications and projects where development speed is a priority. A comparative study between Direct SQL and ORM will help make a better decision on which technology to use to access the data source, depending on the specific project requirements, performance needs, portability, maintainability, and other relevant factors. | es_ES |
| dc.description.abstract | Al Dia de hoy Toda aplicación necesita una Bases de Datos para funcionar y en ella poder guardar la información de sus clientes, productos, contabilidad y todo dato para su correcto funcionamiento. Por lo general la lógica de Negocios de una aplicación se Conecta a la fuente de Datos para realizar operaciones de lectura-Escritura y para esto siempre se ha venido utilizando el lenguaje SQL ya que era el único camino disponible hasta la aparición de los ORM , a partir de este punto la Decisión de utilizar un método u otro se ha convertido en un tema de gran interés en el ámbito de desarrollo de software ya que Ambos enfoques tienen como objetivo acceder a las bases de datos, pero difieren en su implementación y en la percepción de los desarrolladores. SQL, que significa Structured Query Language, es un lenguaje de programación utilizado para gestionar bases de datos relacionales. Permite a los desarrolladores escribir consultas directamente en la base de datos, lo que les brinda un control detallado sobre cómo se accede y manipula la información. SQL es ampliamente aceptado y utilizado, especialmente en aplicaciones empresariales. Por otro lado, los ORM son herramientas que mapean objetos de un lenguaje de programación a tablas en una base de datos relacional. Estos facilitan la interacción con la base de datos al ocultar la complejidad de las consultas SQL. Algunos ejemplos populares de ORM son Hibernate para Java y Entity Framework para .NET. El nivel de aceptación entre los desarrolladores varía entre SQL y ORM. Los desarrolladores con experiencia en bases de datos suelen preferir SQL, ya que les permite un control completo y una optimización fina de las consultas. Sin embargo, los ORM son más populares entre los desarrolladores que desean una forma más sencilla y orientada a objetos de trabajar con bases de datos. Los ORM también son útiles en equipos multidisciplinarios donde no todos los miembros son expertos en SQL. En cuanto a la popularidad, SQL sigue siendo la elección predominante en el desarrollo de bases de datos, especialmente en aplicaciones de misión crítica. Los ORM son populares en aplicaciones web y proyectos donde la velocidad de desarrollo es prioritaria. El Estudio Comparativo entre SQL Directo y un ORM permitirá tomar una mejor decisión de que tecnología utilizar para acceder a la fuente de datos dependiendo de las necesidades específicas del proyecto, los requisitos de rendimiento, la portabilidad, la mantenibilidad y otros factores relevantes. | es_ES |
| dc.format.extent | 37 p. | es_ES |
| dc.language.iso | es | es_ES |
| dc.publisher | Babahoyo: UTB-FAFI. 2023 | es_ES |
| dc.rights | Atribución-NoComercial-SinDerivadas 3.0 Ecuador | * |
| dc.rights.uri | http://creativecommons.org/licenses/by-nc-nd/3.0/ec/ | * |
| dc.subject | ORM | es_ES |
| dc.subject | Mapeo Objeto-Relacional | es_ES |
| dc.subject | SQL | es_ES |
| dc.subject | Base de Datos Relacional | es_ES |
| dc.title | Estudio Comparativo entre SQL Directo y un ORM. | es_ES |
| dc.type | bachelorThesis | es_ES |
Ficheros en el ítem
Este ítem aparece en la(s) siguiente(s) colección(ones)
Excepto si se señala otra cosa, la licencia del ítem se describe como Atribución-NoComercial-SinDerivadas 3.0 Ecuador