CUBRID is an open-source relational database management system designed for internet portal services, offering features like a multi-threaded architecture, various APIs, and a graphical interface for management. The document details CUBRID's system architecture, including its server, client, and broker subsystems, as well as its processes for query handling and transaction management. It also emphasizes the importance of following Creative Commons attribution and licensing conditions when reusing or modifying the work.

1. CUBRID InsideFirst Look Inside CUBRIDJan 18, 2009

2. 저작권 Copyright NoticeCREATIVE COMMONS 저작자표시-동일조건변경허락 2.0 대한민국이용자는 아래의 조건을 따르는 경우에 한하여 자유롭게이 저작물을 복제, 배포, 전송, 전시, 공연 및 방송할 수 있습니다.이차적 저작물을 작성할 수 있습니다.다음과 같은 조건을 따라야 합니다:저작자표시. 귀하는 원저작자를 표시하여야 합니다. What does "Attribute this work" mean? The page you came from contained embedded licensing metadata, including how the creator wishes to be attributed for re-use. You can use the HTML here to cite the work. Doing so will also include metadata on your page so that others can find the original work as well. 동일조건변경허락. 귀하가 이 저작물을 개작, 변형 또는 가공했을 경우에는, 이 저작물과 동일한 이용허락조건하에서만 배포할 수 있습니다. 귀하는, 이 저작물의 재이용이나 배포의 경우, 이 저작물에 적용된 이용허락조건을 명확하게 나타내어야 합니다.저작권자로부터 별도의 허가를 받으면 이러한 조건들은 적용되지 않습니다.Nothing in this license impairs or restricts the author's moral rights.CREATIVE COMMONS Attribution-Share Alike 2.0 KoreaYou are free:to Share — to copy, distribute and transmit the workto Remix — to adapt the workUnder the following conditions:Attribution. You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work). What does "Attribute this work" mean? The page you came from contained embedded licensing metadata, including how the creator wishes to be attributed for re-use. You can use the HTML here to cite the work. Doing so will also include metadata on your page so that others can find the original work as well. Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one. For any reuse or distribution, you must make clear to others the license terms of this work. The best way to do this is with a link to this web page.Any of the above conditions can be waived if you get permission from the copyright holder.Nothing in this license impairs or restricts the author's moral rights.http://creativecommons.org/licenses/by-sa/2.0/kr/Copyright 2009 Search Solution Corporation. All Rights Reserved.

3. CUBRID

4. ContentsSystem Architecture and ProcessesDesign & Implementation ConceptsModule and Source StructureIn The Next CUBRID Inside4/41 First Look Inside CUBRID

5. What is CUBRID?

6. System Architecture

7. CUBRID Processes and IPC

8. Query Processing WorkflowSystem Architecture and Processes15/41 First Look Inside CUBRID

9. System Architecture and ProcessesWhat is CUBRID?CUBRID isOpen Source DBMS owned and developed by NHNHosted at nForge siteTargeted to a database platform for Internet portal serviceRelational database system with object extensions – Object-Relational Model1,000,000 line of source code scaled projectEngine – C/C++, CUBRID Manager (GUI) and JDBC driver – JavaCUBRID providesFull-featured database server engineServer and Broker architectureGUI management and query toolCUBRID ManagerVarious API (JDBC, ODBC(OLE DB), PHP, and CCI)Python and Ruby as contributed projects1.16/41 First Look Inside CUBRID

10. System Architecture and ProcessesSystem Architecture1.2Server SubsystemMulti-threaded storage engine part which runs as DB serverConsists of Transaction Manager, Object Manager, Lock Manager, Query Manager, Log Manager, and Storage ManagerClient SubsystemClient library part providing native C APIConsists of Query Parser & Optimizer, Object & Lock Cache, Transaction Manager and Object ManagerBroker SubsystemLinked with client library and implemented CCI protocolDoes job queuing, connection pooling, monitoring and loggingConnectorsJDBC driverCCI libraryMany drivers are implemented with CCI library – ODBC, OLEDB, PHP, Python, and Ruby7/41 First Look Inside CUBRID

11. System Architecture and ProcessesSystem Architecture1.2CUBRIDManagerGUIInterfacePHPOLE DBRubyCUBRIDManagerJDBCODBCCCIPythonCM ServerJobQueuingMonitoringConnectionPoolingLoggingAdminUtilityBrokerCreate, Delete, Copy, RenameQueryParser &OptimizerLockCacheObjectManagerTransactionManagerAdd VolumeLoad /UnloadBackup /RestoreQueryManagerLockManagerServerCompact /OptimizeStorageManagerLogManagerCheck /DiagActiveLogFile BasedObjectsDataVolumeIndexVolumeTempVolumeArchiveLog8/41 First Look Inside CUBRID

12. 1.2CUBRIDManagerGUIInterfacePHPOLE DBRubyCUBRIDManagerJDBCODBCCCIPythonCM ServerCreate, Delete, Copy, RenameJobQueuingMonitoringConnectionPoolingLoggingAdminUtilityBrokerClient LibraryAdd VolumeNative C APIParserObjectManagerSchemaManagerTransactionManagerLoad /UnloadQueryTransformWorkspace ManagerBackup /RestoreQueryOptimizerMemory ManagerCompact /OptimizePlanGenerationCheck /DiagCommunication ModuleStorage EngineServerCommunication ModuleTransactionManagerLogManagerLockManagerQueryManagerAccessMethodB+TreeModuleFile ManagerSystemCatalog ModuleSystem ArchitectureBuffer ManagerDisk ManagerActiveLogFile BasedObjectsDataVolumeIndexVolumeTempVolumeArchiveLog9/41 First Look Inside CUBRID

13. System Architecture and ProcessesCUBRID Processes and IPCMaster Process ‘cub_master’Daemon process listening on the TCP port for clients’ connectioncsql, broker, and admin utilitiesRegistrar of server processes using Unix Domain SocketServer Process ‘cub_server’Multi-threaded process serving clients’ requestsHas thread pool and job queueAccesses database volume and log filesOne server process per one databaseBroker Process ‘cub_broker’Daemon process listening on the TCP port for connectors’ connectionControls cub_cas processes (fork/kill) with connection queueCAS Process ‘cub_cas’Connects to the server process in behalf of connectorsAccording to the database and user nameCSQL Program ‘csql’Interactive SQL execution1.310/41 First Look Inside CUBRID

14. System Architecture and ProcessesCUBRID Processes and IPC1.3JDBC driverCCI libraryconnectquery &resultquery &resultport listeningcub_brokercubrid_broker.confforkparsedescriptor passAPWeb Servercub_cascub_casshared memorycubridcs.socubridcs.socsqlconnectcubridcs.sorequest &responserequest &responseparseBrokerTCPjob queuemulti-threadport listeningdescriptor passparsecub_mastercub_servercubrid.socubrid.confUDSActiveServerStandbyServermount(read/write)readregistervolume filelog filedatabases.txtvolume filelog fileReplicationcub_admincubridsa.so11/41 First Look Inside CUBRID

15. System Architecture and ProcessesQuery Processing Workflow1.412/41 First Look Inside CUBRID

16. System Architecture and ProcessesQuery Processing Workflow1.4XASL TypeUNIONExtended Access Spec Language(XASL)DIFFERENCEINTERSECTIONOBJFETCHQuery ManagerTransactionManagerLock ManagerSETFETCHBUILD_LISTBUILD_VALUEQuery Result CacheQuery Plan CacheQuery Evaluator(Interpreter)SCANMERGE_LISTScan ManagementREADUPDATEStorage ManagerDELETEINSERT13/41 First Look Inside CUBRID

17. Design & Implementation Concepts2Client-Server and Standalone Mode

18. Object, Class and OID

19. Representation, Record Descriptor, and Memory Object Pointer

20. Workspace – Object & Lock Caching

21. 2PL vs. MVCC

22. XASL (Extended Access Spec Language)

23. Heap, B+tree, Catalog, and Temp

24. Click Counter14/41 First Look Inside CUBRID

25. Design & Implementation ConceptsClient-Server and Standalone Mode2.115/41 First Look Inside CUBRID

26. Design & Implementation ConceptsObject, Class and OID2.216/41 First Look Inside CUBRID

27. Design & Implementation ConceptsRepresentation, Record Descriptor, and Memory Object Pointer2.317/41 First Look Inside CUBRID

28. Design & Implementation ConceptsWorkspace – Object & Lock Caching2.418/41 First Look Inside CUBRID

29. Design & Implementation Concepts2PL vs. MVCC2.519/41 First Look Inside CUBRID

30. Design & Implementation ConceptsXASL (Extended Access Spec Language)2.620/41 First Look Inside CUBRID

31. Design & Implementation ConceptsHeap, B+tree, Catalog, and Temp2.721/41 First Look Inside CUBRID

32. Design & Implementation ConceptsClick CounterIn Terms of UserWhenever the user clicks an article, the read counter of the article is increased.Counts the clicks on the articleIn Terms of Service Application DeveloperThe read counter is very important for bulletin board type service.Combine getting article data and increasing read counter togetherget_article() + increase_counter() = get_article_and_increase_counter()(SELECT article_info) + (UPDATE read_counter+1)In Terms of Database EngineerDo SELECT and UPDATE in one SQL statementSELECT trigger? SELECT FOR UDPATE?UPDATE the record with the short term lockExampleSELECT doc_id, title, INCR(read_counter), post_date FROM board WHERE doc_id=?2.822/41 First Look Inside CUBRID

33. Design & Implementation ConceptsClick Counter2.8Don’t walk the same passage twice!When you get there, do as many things as possible.Killing two birds with one stone.23/41 First Look Inside CUBRID

34. Module and Source Structure3Overall Structure

35. Query Processing Component

36. Transaction Management Component

37. Server Storage Management Component

38. Client Storage Management Component

39. Object Management Component

40. Job and Thread Management Component

41. Client-Server Communication Layer

42. Broker Component24/41 First Look Inside CUBRID