CN116881223A - Implantable embedded database system and embedded database system transplanting method - Google Patents
Implantable embedded database system and embedded database system transplanting method Download PDFInfo
- Publication number
- CN116881223A CN116881223A CN202310843327.4A CN202310843327A CN116881223A CN 116881223 A CN116881223 A CN 116881223A CN 202310843327 A CN202310843327 A CN 202310843327A CN 116881223 A CN116881223 A CN 116881223A
- Authority
- CN
- China
- Prior art keywords
- layer
- file
- module
- interface
- cross
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 13
- 230000006978 adaptation Effects 0.000 claims abstract description 53
- 230000006870 function Effects 0.000 claims abstract description 18
- JEIPFZHSYJVQDO-UHFFFAOYSA-N iron(III) oxide Inorganic materials O=[Fe]O[Fe]=O JEIPFZHSYJVQDO-UHFFFAOYSA-N 0.000 claims abstract description 11
- 238000002054 transplantation Methods 0.000 claims abstract description 6
- 238000013509 system migration Methods 0.000 claims description 5
- 230000001360 synchronised effect Effects 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 8
- 238000013508 migration Methods 0.000 description 6
- 230000005012 migration Effects 0.000 description 6
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000005856 abnormality Effects 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 230000003044 adaptive effect Effects 0.000 description 1
- 230000008094 contradictory effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/214—Database migration support
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/31—Programming languages or programming paradigms
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/76—Adapting program code to run in a different environment; Porting
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Computing Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention belongs to the technical field of computers, and in particular relates to a portable embedded database system and a method for transplanting the embedded database system, which comprises the following steps: a business logic layer, an adaptation layer and an operation interface abstract layer; the business logic layer is used for inputting instructions and realizing system functions of the database non-bottom layer system resource call; the adaptation layer is connected with the database bottom layer system to realize the scheduling and the use of the database bottom layer system resources; the operation interface abstract layer is connected with the adapting layer and the operation system and is used for realizing cross-platform transplantation. In the scheme, functions with different platform differences are packaged into an adaptation layer for implementation, and functions without differences are packaged into a business logic layer for direct cross-platform transplantation. The adaptation layer is realized by utilizing the cross-platform characteristic of Rust language, so that the cross-platform transplanting of the functional module is realized.
Description
Technical Field
The invention belongs to the technical field of computers, and particularly relates to a portable embedded database system and an embedded database system transplanting method.
Background
The embedded database system is a lightweight database system, can run on embedded equipment and mobile equipment, can also run on a general platform after being integrated with other lightweight applications, and provides a method for accessing a database for a calling party. Unlike conventional client/server model database systems, embedded database systems are typically provided in the form of libraries that are compiled and deployed with applications.
Portability is very important for programs on embedded devices. Because the use field of the embedded system is very wide, the adopted operating system also has various software and hardware environments, so the embedded data system needs to have certain portability and can operate in various environments.
Disclosure of Invention
In order to overcome the defects of the prior art, the invention provides a portable embedded database system and an embedded database system transplanting method, so as to solve the problems of the prior art.
One aspect of the present invention provides a portable embedded database system, comprising: a business logic layer, an adaptation layer and an operation interface abstract layer;
the business logic layer is used for inputting instructions and realizing system functions of the database non-bottom layer system resource call;
the adaptation layer is connected with the database bottom layer system to realize the scheduling and the use of the database bottom layer system resources;
the operation interface abstract layer is connected with the adapting layer and the operation system and is used for realizing cross-platform transplantation.
In the scheme, a layering mode is adopted to divide the database system into a business logic layer and an adaptation layer, functions with different platform differences are packaged into the adaptation layer to be realized, and functions without differences are packaged into the business logic layer to be directly transplanted across platforms. The adaptation layer is realized by utilizing the cross-platform characteristic of Rust language, so that the cross-platform transplanting of the functional module is realized. In one aspect of the present invention, the adaptation layer includes at least: memory management module, semaphore & lock management module, file management module, thread management module.
In one application scenario of the scheme, the service logic layer and the adaptation layer do not require the same programming language, a unified acquisition system resource interface is arranged in a cross-platform language, and interface differences of different systems are realized by the interior of the language, so that small-range modification can be realized by only reconstructing the adaptation layer on the basis of the original database system project, the project whole portability is realized, the workload required for realizing the database system project whole portability can be effectively reduced, and the working efficiency is improved.
In one of the schemes of the present invention, the memory management module includes a memory management interface and a memory management structure, and the memory management structure is called through the memory management interface to implement memory initialization, memory application, memory allocation, memory expansion and memory release.
In one of the schemes of the invention, the semaphore & lock management module comprises a conditional variable management sub-module, a lock management sub-module and a semaphore & lock management interface, wherein the conditional variable management sub-module is called through the semaphore & lock management interface and is used for realizing acquisition of the mutex semaphore, release of the mutex semaphore, waiting of the event semaphore and release of the event semaphore; and calling the lock management sub-module through the semaphore and lock management interface to initialize the lock, acquire the lock and release the lock.
In one of the schemes of the invention, the file management module comprises a file basic operation sub-module, a file expansion operation sub-module and a file management interface, and the file basic operation sub-module is called through the file management interface and is used for realizing the opening and closing of a file, the reading operation of the file and the writing operation of the file; and calling the file expansion operation submodule through the file management interface to realize file reading operation with positioning, file writing operation with positioning, file length acquisition, file synchronization, file copying, file movement, file size setting and file comparison.
In one of the schemes of the invention, the thread management module comprises a thread management interface, and the thread management module is called through the thread management interface and is used for realizing the initialization of threads, the setting of thread priority, the exiting of threads, the synchronous waiting among threads, the acquisition of thread id and the waiting of threads.
In one aspect of the present invention, the operation interface abstraction layer includes: an operating system environment identification sub-module, an operating system judgment sub-module, a base library corresponding sub-module and a cross-platform external interface; the operating system environment recognition submodule recognizes the current operating system environment and outputs recognition information; the operating system judging submodule receives and judges basic library information corresponding to the identification information; the base library corresponding sub-module loads a base library corresponding to a current operating system based on the base library information, and the base library is used for being connected with the adaptation layer; the cross-platform external interface is used for connecting the basic library and the operating system;
wherein the cross-platform external interfaces of the basic libraries corresponding to different operating systems are consistent.
In one of the embodiments of the present invention, the business logic layer includes an SQL engine module, and a storage engine module, through which input instructions are received to generate a physical execution plan, and through which the physical execution plan is implemented.
In one aspect of the invention, the portable embedded database system is developed based on a cross-platform programming language, which is either Rust or Golang.
In one aspect of the present invention, there is also provided a method for transplanting an embedded database system, which can be used in the portable embedded database system of any one of the above aspects, the method for transplanting an embedded database system comprising:
the embedded database system at least comprises a business logic layer, an adaptation layer and an operation interface abstract layer;
based on the business logic layer, realizing the system function of the database non-bottom system resource call;
the adaptation layer interacts with the database bottom layer system to realize the scheduling and the use of the database bottom layer system resources;
connecting the adaptation layer and the operating system through the operation interface abstraction layer, and loading a cross-platform external interface corresponding to the operating system in the adaptation layer based on the implementation mode of the operating system, wherein the cross-platform external interface is used for realizing cross-platform transplantation;
wherein the adaptation layer is developed by a cross-platform programming language; and/or the programming language of the business logic layer is different from that of the adaptation layer.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to the structures shown in these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a portable embedded database system architecture according to one embodiment of the present invention;
FIG. 2 is a schematic diagram of an adaptive layer according to an embodiment of the present invention;
FIG. 3 is a schematic diagram illustrating a memory management module according to an embodiment of the invention;
FIG. 4 is a schematic diagram of a semaphore & lock management module according to an embodiment of the invention;
FIG. 5 is a schematic diagram showing a structure of a file management module according to an embodiment of the present invention;
FIG. 6 is a schematic diagram illustrating a thread management module according to one embodiment of the present invention;
FIG. 7 is a schematic diagram illustrating the architecture of an operation interface abstraction layer according to one embodiment of the present invention;
FIG. 8 is a schematic diagram illustrating the structure of a business logic layer according to one embodiment of the present invention;
FIG. 9 is a flow chart illustrating an embedded database system migration method according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
It should be noted that, if a directional indication (such as up, down, left, right, front, and rear … …) is involved in the embodiment of the present invention, the directional indication is merely used to explain the relative positional relationship, movement condition, etc. between the components in a specific posture, and if the specific posture is changed, the directional indication is correspondingly changed.
In addition, if there is a description of "first", "second", etc. in the embodiments of the present invention, the description of "first", "second", etc. is for descriptive purposes only and is not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In addition, if "and/or" and/or "are used throughout, the meaning includes three parallel schemes, for example," a and/or B "including a scheme, or B scheme, or a scheme where a and B are satisfied simultaneously. In addition, the technical solutions of the embodiments may be combined with each other, but it is necessary to base that the technical solutions can be realized by those skilled in the art, and when the technical solutions are contradictory or cannot be realized, the combination of the technical solutions should be considered to be absent and not within the scope of protection claimed in the present invention.
In this embodiment, the cross-platform programming language is a Rust language, and specifically, a Rust language base library identifies a current environment when a program is compiled, and base libraries of different systems are loaded for different environments. Although the underlying library layer interacts with the operating system differently, the exposed call interfaces to the upper layers are uniform. The interfaces called by different operating systems are the same, so that a set of codes can be directly compiled and run in a plurality of environments. And finally, portability of the database system is realized.
In another application scenario of the embodiment, golang language is adopted as a cross-platform programming language, and the action mechanism of the cross-platform programming language is consistent with that of Rust language.
Referring to fig. 1, one embodiment of the present invention provides a portable embedded database system, which includes: a business logic layer 100, an adaptation layer 200, and an operation interface abstraction layer 300;
the business logic layer 100 is used for inputting instructions and realizing system functions of database non-bottom system resource call;
the adaptation layer 200 is connected with the database bottom layer system to realize the scheduling and the use of the database bottom layer system resources;
the operation interface abstraction layer 300 connects the adaptation layer 200 with an operating system, and is used for implementing cross-platform migration.
In this embodiment, the database system is divided into the service logic layer 100 and the adaptation layer 200 in a layered manner, and functions with different platform differences are packaged into the adaptation layer 200 for implementation, while functions without differences are packaged into the service logic layer 100 for direct cross-platform migration. The adaptation layer 200 is implemented by utilizing the cross-platform characteristic of the Rust language, so that the cross-platform migration of the functional module is realized.
In one application scenario of the embodiment, the service logic layer and the adaptation layer do not require the same programming language, a unified acquisition system resource interface is provided in a cross-platform language, and interface differences of different systems are realized in the language, so that small-range modification can be realized by only reconstructing the adaptation layer on the basis of the original database system project, the project whole portability can be realized, the workload required for realizing the database system project whole portability can be effectively reduced, and the working efficiency is improved.
Referring to fig. 2, in one embodiment of the present invention, the adaptation layer 200 at least includes: memory management module 210, semaphore & lock management module 220, file management module 230, thread management module 240.
In this embodiment, the functions of the bottom operating system interface are required to be called for memory management, memory application/release, semaphore management, lock application/release, thread application/release, file opening/closing, and the like, and are implemented by using a functional module constructed by a rust language, and the unified rust interface is exposed for upper system call, so that cross-platform migration of the functional module is implemented.
Referring to fig. 3, in one embodiment of the present invention, the memory management module 210 includes a memory management interface 211 and a memory management structure 212, and the memory management structure 212 is called through the memory management interface 211 to implement memory initialization, memory application, memory allocation, memory expansion, and memory release.
In one application scenario of the present embodiment, the service logic layer 100 invokes the memory management structure 212 through the memory management interface 211 to initialize a memory management structure (two-dimensional structure): the service logic layer 100 transmits initialization parameters (rust_alloc_init) to the memory management structure 212 in the adaptation layer 200 through the memory management interface 211, the memory management structure 212 initializes the two-dimensional structure through the transmitted parameters and creates a dynamic array (Vec:: new ()) in the interface abstract layer, the memory management structure 212 returns an initialization result to the service logic layer 100 after initialization is completed, the service logic layer 100 judges whether the memory management structure initialization is successful or not, if so, the program runs normally, and when the memory is needed, the interface is called through the interface abstract layer to obtain; if not, recording an error, feeding back an abnormality and exiting.
Referring to fig. 4, in one embodiment of the present invention, the semaphore & lock management module 220 includes a condition variable management sub-module 221, a lock management sub-module 222, and a semaphore & lock management interface 223, where the condition variable management sub-module 221 is invoked by the semaphore & lock management interface 223, so as to implement acquisition of a mutex semaphore, release of the mutex semaphore, waiting of an event semaphore, and release of the event semaphore; the lock management sub-module 222 is invoked via the semaphore & lock management interface 223 for initializing a lock, acquiring a lock, releasing a lock.
Referring to fig. 5, in one embodiment of the present invention, the file management module 230 includes a file basic operation sub-module 231, a file expansion operation sub-module 232, and a file management interface 233, where the file basic operation sub-module 231 is called by the file management interface 233 to implement opening and closing of a file, reading operation of a file, and writing operation of a file; the file expansion operation submodule 232 is called through the file management interface 233, and is used for realizing file reading operation with positioning, file writing operation with positioning, file length acquisition, file synchronization, file copying, file movement, file size setting and file comparison.
Referring to fig. 6, in one embodiment of the present invention, the thread management module 240 includes a thread management interface 241, and the thread management module 240 is called through the thread management interface 241 to implement thread initialization, thread priority setting, thread exiting, inter-thread synchronous waiting, thread id obtaining, and thread waiting.
In this embodiment, the thread management module 240 is invoked by the business logic layer 100 through the thread management interface 241 for implementing creating threads: the service logic layer 100 transmits a parameter rust_thread_create (function pointer) to the thread management module 240 in the adaptation layer 200 through the thread management interface 241, and the thread management module 240 transmits the transmitted parameter to the interface abstraction layer to create an array, which may be defined by handle, in one possible implementation, for example:
lethandle＝thread::spawn(||{
let f is fn (parameter type) =unsafe [ std:: mem:: transform };
f (parameter pointer);
})；
the post creation memory management module 210 returns the join handle object to the thread management module 240, the thread management module 240 generates a unique thread id corresponding to the join handle, stores the unique thread id in the global map (thread id, join handle), and returns the thread id to the business logic layer 100, the business logic layer 100 stores the thread id, and subsequently calls a corresponding thread depending on the id.
Referring to fig. 7, in one embodiment of the present invention, the operation interface abstraction layer 300 includes: an operating system environment recognition sub-module 310, an operating system judgment sub-module 320, a base library corresponding sub-module 330 and a cross-platform external interface 340; the operating system environment recognition sub-module 310 recognizes a current operating system environment and outputs recognition information; the operating system judging sub-module 320 receives and judges the basic library information corresponding to the identification information; the base library corresponding sub-module 330 loads a base library corresponding to a current operating system based on the base library information, wherein the base library is used for being connected with the adaptation layer 200; the cross-platform external interface 340 is used for connecting the base library and the operating system;
wherein the cross-platform external interfaces 340 of the base libraries corresponding to different operating systems are consistent.
In this embodiment, the implementation manner refers to a processing manner of instructions or bytes by different compilers corresponding to different systems; based on different implementations corresponding to different operating systems, the operating interface abstraction layer 300 may load a cross-platform external interface 340 of the implementation of the corresponding operating system, for implementing connection between the operating system and the adaptation layer 200.
Referring to fig. 8, in one embodiment of the present invention, the business logic layer 100 includes an SQL engine module 110 and a storage engine module 120, and the SQL engine module 110 receives an input instruction to generate a physical execution plan, and the storage engine module 120 implements the physical execution plan.
In this embodiment, the service logic layer 100 may be used to implement a data function that the database has no difference under different operating systems.
Referring to fig. 9, in one embodiment of the present invention, there is further indicated an embedded database system migration method, which may be used in the portable embedded database system according to any one of the above embodiments, the embedded database system migration method includes:
s10, the embedded database system at least comprises a business logic layer, an adaptation layer and an operation interface abstraction layer;
s20, based on the business logic layer, realizing a system function called by a database non-bottom layer system resource;
s30, interacting with the database bottom layer system through the adaptation layer to realize scheduling and use of the database bottom layer system resources;
s40, connecting the adaptation layer and the operating system through the operation interface abstraction layer, and loading a cross-platform external interface corresponding to the operating system in the adaptation layer based on the implementation mode of the operating system, wherein the cross-platform external interface is used for realizing cross-platform migration;
wherein the adaptation layer is developed by a cross-platform programming language; and/or the programming language of the business logic layer is different from that of the adaptation layer.
In this embodiment, the database system is divided into the service logic layer and the adaptation layer in a layered manner, the functions with different platform differences are packaged into the adaptation layer for implementation, and the functions without differences are packaged into the service logic layer, so that a scheme of cross-platform migration of the database system can be formed. The adaptation layer is realized by utilizing the cross-platform characteristic of Rust language, so that the cross-platform transplanting of the functional module is realized.
In one embodiment of the present invention, the embedded database system migration method is used for performing portability improvement on database system items completed by non-cross-platform programming languages, wherein, the service logic layer has no programming language limitation in the portability scheme of the present invention, and the service logic layer and the adaptation layer do not require the same programming language. Therefore, based on the characteristics that the cross-platform language has uniform acquisition system resource interfaces and interface differences of different systems are realized by the language, the adaptation layer can be reconstructed only through the cross-platform programming language on the basis of the original database system project, so that the project whole portability can be realized by realizing small-range modification, the workload required for realizing the database system project whole portability can be effectively reduced, and the working efficiency is improved.
The foregoing description is only of the preferred embodiments of the present invention and is not intended to limit the scope of the invention, and all equivalent structural changes made by the description of the present invention and the accompanying drawings or direct/indirect application in other related technical fields are included in the scope of the invention.
Claims (10)
1. A portable embedded database system, comprising: a business logic layer, an adaptation layer and an operation interface abstract layer;
the business logic layer is used for inputting instructions and realizing system functions of the database non-bottom layer system resource call;
the adaptation layer is connected with the database bottom layer system to realize the scheduling and the use of the database bottom layer system resources;
the operation interface abstract layer is connected with the adapting layer and the operation system and is used for realizing cross-platform transplantation.
2. The portable embedded database system of claim 1, wherein the adaptation layer comprises at least: memory management module, semaphore & lock management module, file management module, thread management module.
3. The portable embedded database system of claim 2, wherein the memory management module comprises a memory management interface, a memory management structure, the memory management structure being invoked via the memory management interface for implementing memory initialization, memory application, memory allocation, memory expansion, and memory release.
4. The portable embedded database system of claim 2, wherein the semaphore & lock management module comprises a condition variable management sub-module, a lock management sub-module, and a semaphore & lock management interface, the condition variable management sub-module being invoked through the semaphore & lock management interface for implementing acquisition of a mutex semaphore, release of a mutex semaphore, waiting of an event semaphore, release of an event semaphore; and calling the lock management sub-module through the semaphore and lock management interface to initialize the lock, acquire the lock and release the lock.
5. The portable embedded database system of claim 2, wherein the file management module comprises a file base operation sub-module, a file expansion operation sub-module, and a file management interface, and the file base operation sub-module is called through the file management interface to realize opening and closing of a file, reading operation of the file, and writing operation of the file; and calling the file expansion operation submodule through the file management interface to realize file reading operation with positioning, file writing operation with positioning, file length acquisition, file synchronization, file copying, file movement, file size setting and file comparison.
6. The portable embedded database system of claim 2, wherein the thread management module comprises a thread management interface through which the thread management module is invoked for implementing initialization of threads, setting of thread priorities, exiting of threads, inter-thread synchronous waiting, acquisition of thread ids, waiting of threads.
7. The portable embedded database system of claim 1, wherein the operational interface abstraction layer comprises: an operating system environment identification sub-module, an operating system judgment sub-module, a base library corresponding sub-module and a cross-platform external interface; the operating system environment recognition submodule recognizes the current operating system environment and outputs recognition information; the operating system judging submodule receives and judges basic library information corresponding to the identification information; the base library corresponding sub-module loads a base library corresponding to a current operating system based on the base library information, and the base library is used for being connected with the adaptation layer; the cross-platform external interface is used for connecting the basic library and the operating system;
wherein the cross-platform external interfaces of the basic libraries corresponding to different operating systems are consistent.
8. The portable embedded database system of claim 1, wherein the business logic layer comprises an SQL engine module by which input instructions are received to generate a physical execution plan, a storage engine module by which the physical execution plan is implemented.
9. The portable embedded database system of any of claims 1-8, wherein the portable embedded database system is developed based on a cross-platform programming language, the cross-platform programming language being Rust or Golang.
10. An embedded database system migration method, applicable to the portable embedded database system of any one of claims 1 to 9, comprising:
the embedded database system at least comprises a business logic layer, an adaptation layer and an operation interface abstract layer;
based on the business logic layer, realizing the system function of the database non-bottom system resource call;
the adaptation layer interacts with the database bottom layer system to realize the scheduling and the use of the database bottom layer system resources;
connecting the adaptation layer and the operating system through the operation interface abstraction layer, and loading a cross-platform external interface corresponding to the operating system in the adaptation layer based on the implementation mode of the operating system, wherein the cross-platform external interface is used for realizing cross-platform transplantation;
wherein the adaptation layer is developed by a cross-platform programming language; and/or the programming language of the business logic layer is different from that of the adaptation layer.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310843327.4A CN116881223A (en) | 2023-07-10 | 2023-07-10 | Implantable embedded database system and embedded database system transplanting method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310843327.4A CN116881223A (en) | 2023-07-10 | 2023-07-10 | Implantable embedded database system and embedded database system transplanting method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116881223A true CN116881223A (en) | 2023-10-13 |
Family
ID=88269269
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310843327.4A Pending CN116881223A (en) | 2023-07-10 | 2023-07-10 | Implantable embedded database system and embedded database system transplanting method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116881223A (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101303644A (en) * | 2007-05-08 | 2008-11-12 | 西北民族大学 | Brahma-sutra Tibetan input method based on Windows OS and Linux OS |
| CN107977369A (en) * | 2016-10-21 | 2018-05-01 | 北京计算机技术及应用研究所 | Easy to the embedded data base management system of transplanting |
-
2023
- 2023-07-10 CN CN202310843327.4A patent/CN116881223A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101303644A (en) * | 2007-05-08 | 2008-11-12 | 西北民族大学 | Brahma-sutra Tibetan input method based on Windows OS and Linux OS |
| CN107977369A (en) * | 2016-10-21 | 2018-05-01 | 北京计算机技术及应用研究所 | Easy to the embedded data base management system of transplanting |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8661410B2 (en) | Managed enterprise software components as dynamic services | |
| Briot et al. | Concurrency and distribution in object-oriented programming | |
| US8706881B2 (en) | Automatic registration of enterprise resources in a dynamic module system services registry | |
| US8856734B2 (en) | Type-safe dependency injection of services into enterprise components | |
| US20040172618A1 (en) | Systems and methods for a common runtime container framework | |
| US20030188300A1 (en) | Parallel processing system design and architecture | |
| Roll | Towards model-based and ccm-based applications for real-time systems | |
| US7444618B2 (en) | Automatic generation of batch programs with identification, insertion of invariables, declarative statements and variables with the use of place-marks | |
| US8719778B2 (en) | Interconnection interface for flexible online/offline deployment of an n-layered software application | |
| US7802257B1 (en) | Mechanism for bridging a thread-oriented computing paradigm and a job-oriented computing paradigm | |
| US20120185860A1 (en) | Component Lock Tracing | |
| CN111522623B (en) | Modularized software multi-process running system | |
| CN109408212B (en) | Task scheduling component construction method and device, storage medium and server | |
| CN116881223A (en) | Implantable embedded database system and embedded database system transplanting method | |
| US7418713B2 (en) | Component processing system and component processing method | |
| US20070220531A1 (en) | Method and system for shimming COM objects | |
| US10534640B2 (en) | System and method for providing a native job control language execution engine in a rehosting platform | |
| Aldinucci et al. | Fastflow tutorial | |
| CN110347448B (en) | Method for constructing runtime model of terminal application behavior | |
| López Martínez et al. | Scheduling configuration of real-time component-based applications | |
| Sherwood et al. | Formulating efficient software solution for digital image processing system | |
| Murata et al. | Unification of active and passive objects in an object-oriented operating system | |
| Welch et al. | Reengineering computer-based systems for enhanced concurrency and layering | |
| Medeiros et al. | Grid programming frameworks | |
| CN117971313A (en) | Conversion method, system and storage medium for micro service to monomer service package |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |