<transcript><audio_10>vice versa this helps build applications in a fairly modular fashion and below the business logic layer is the data access layer which actually talks to the database now typically data access is done directly in SQL however</transcript><transcript><audio_11>increasingly these days there is a something called object relational mapping which helps to hide the SQL from the upper level program and i have a slide coming up on that so i will talk</transcript><caption><image_12>The image is a diagram of an application architecture. It shows a web browser, an internet connection, a controller, a model, a data access layer, and a database. 

The web browser is connected to the controller, which is located on the left side of the image. The controller is located in the center of the diagram. The model is located to the right of the controller. The data access layers are located at the bottom of the web application server.

There is also a view of the view, which allows the user to view the view from the top of the computer. The view is represented by a cloud-like shape, which represents the internet connection. The cloud is represented as a cloud with a network connection, and the network connection is represented in a rectangular shape. The image also shows a database with a database on the bottom right corner.</caption><transcript><audio_13>more about that in a little bit so this is a pictorial depiction of the same architecture Model View and controller so a request comes to something called a controller which talks in the model which is basically</transcript><transcript><audio_14>the business logic and when it gets a response back it talks to the view part of the code which formats it returns it and then that view is displayed to the user this is a abstract model and the model itself talks to the data access</transcript><caption><image_15>The image is a slide from a presentation about object-relational mapping. It has a blue background and white text. The slide has a title at the top that reads "Object-Relational Mapping" and below it, there are three bullet points.

The first bullet point explains that the application code is written on top of object-oriented data model, while storing data in a traditional relational database. The second bullet point states that the user has not been commercially successful in mapping between object data and relational schema. The third bullet point mentions that the data model is a Java class student mapped to relation student, with corresponding mapping of attributes. The fourth bullet point discusses how the application can be created and saved to the database using session-saver(object) and how it can be used to create appropriate types in the database.</caption><transcript><audio_16>layer which talks to the database so as I said increasingly there is something called object relational mapping which is used in many applications so what is object relational mapping many of you might know about object oriented</transcript> vice versa this helps build applications in a fairly modular fashion and below the business logic layer is the data access layer which actually talks to the database now typically data access is done directly in SQL however increasingly these days there is a something called object relational mapping which helps to hide the SQL from the upper level program and i have a slide coming up on that so i will talk more about that in a little bit so this is a pictorial depiction of the same architecture Model View and controller so a request comes to something called a controller which talks in the model which is basically the business logic and when it gets a response back it talks to the view part of the code which formats it returns it and then that view is displayed to the user this is a abstract model and the model itself talks to the data access layer which talks to the database so as I said increasingly there is something called object relational mapping which is used in many applications so what is object relational mapping many of you might know about object oriented
{"source": "grass-yt-cc-by.0RitPJG0BgI|shard_10035_43|create_multimodal_data.extract_yt_and_generate_transcripts.56|shard_10035|create_multimodal_data.generate_captions.29|shard_10035|create_multimodal_data.generate_captions.42", "params": {"id": "0RitPJG0BgI", "channel_id": "UC3lp1Pk33sziERUwvmiNBqQ", "duration": 2528, "view_count": 249, "age_limit": 0, "chapters": [{"start_time": 0, "end_time": 35.0, "title": "<Untitled Chapter 1>"}, {"start_time": 35.0, "title": "Application Architectures", "end_time": 718.0}, {"start_time": 718.0, "title": "Object-Relational Mapping and Hibernate (Cont.) \u2022 The Hibernate object-relational mapping system is widely used public domain system, runs on a variety of database systems \u2022 supports a query language that can express complex queries", "end_time": 728.0}, {"start_time": 728.0, "title": "Web Services . Allow data on Web to be accessed using remote procedure call mechanism . Two approaches are widely used", "end_time": 2528}], "like_count": 4, "channel_follower_count": 34800, "license": "Creative Commons Attribution license (reuse allowed)", "uploader_id": "@StudioIITBombay", "yt_tar_file": "/leonardo_work/EUHPC_E03_068/audio/fixed_download/grass-yt-cc-by//shard_10035/0RitPJG0BgI.tar.gz"}}