CN105653334A - Rapid development framework for MIS system based on SAAS mode - Google Patents
Rapid development framework for MIS system based on SAAS mode Download PDFInfo
- Publication number
- CN105653334A CN105653334A CN201511027295.2A CN201511027295A CN105653334A CN 105653334 A CN105653334 A CN 105653334A CN 201511027295 A CN201511027295 A CN 201511027295A CN 105653334 A CN105653334 A CN 105653334A
- Authority
- CN
- China
- Prior art keywords
- access
- layer
- client terminal
- service end
- system based
- 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.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- 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/25—Integrating or interfacing systems involving database management systems
Abstract
The invention discloses a rapid development framework for a MIS system based on a SAAS mode. The framework comprises an operation framework layer, a communication layer, a service application layer, a data access layer and a plug-in interface layer, wherein the operation framework layer is used for realizing management on a main interface and a plug-in when a program is operated and loading of data; the communication layer is used for realizing communication between a client side and a service side; the service application layer is used for realizing processing to a service and service process controlling and distributing; the data access layer is used for realizing access to a database and supporting for multiple databases; and the plug-in interface layer is used for defining a basic interface of a system operated plug-in. The rapid development framework disclosed by the invention has the characteristics of being high in development efficiency and low in development period, development cost and development difficulty.
Description
Technical field
The present invention relates to a kind of development platform, particularly a kind of quick Development Framework of the mis system based on SAAS pattern.
Background technology
SAAS is Software-as-a-service (namely software serves). SAAS call in the field of business is software operation, or claims soft battalion. It it is a kind of application model that software service is provided based on internet. Along with the development of Internet technology and a maturation for application software, in the software application pattern innovated completely starting in 21st century to rise, it is the recent tendency of software development in science and technology. SAAS provider is that the all-network Infrastructure required for informationization and software, hardware running platform are built by enterprise, and a series of services such as the enforcement in responsible all early stages, the maintenance in later stage, enterprise is without the need to buying software and hardware, build machine room, recruit IT personnel, namely by internet use infosystem. But use SAAS mode development mainly to there is following shortcoming at present: developer is when developing each business, often need to from the bottom business such as data communication, database access, this just increases the workload of exploitation business, reduce development efficiency, increase development difficulty simultaneously, the technical ability of exploitation technician is required corresponding raising.
Summary of the invention
It is an object of the present invention to provide a kind of quick Development Framework of the mis system based on SAAS pattern. The present invention has, it is to increase development efficiency, shortening construction cycle reduce cost of development and reduce the feature of development difficulty.
The technical scheme of the present invention: a kind of quick Development Framework of the mis system based on SAAS pattern, this framework
Comprise:
Operation frame layer, for realizing main interface when program is run and the management to plug-in unit and the loading to master data;
Communication layers, for realizing communicating of client terminal and service end;
Service application layer, distributes for realizing the process to business and realize the Row control to business;
Data access layer, for realize the access to database and to the support of multitype database;
Card i/f layer, for defining the basic interface of system cloud gray model plug-in unit.
The aforesaid quick Development Framework of the mis system based on SAAS pattern also comprises interface control layer, and described interface control layer is for realizing the expansion to the basic control of client terminal.
The aforesaid quick Development Framework of the mis system based on SAAS pattern works in the steps below:
A, operation frame layer are after loading master data, then define corresponding client plug-in interface by card i/f layer, and client terminal can be loaded;
After b, client terminal are loaded, client terminal is by communication layers access services end, and now the access request of client terminal is distributed to corresponding service end by service application layer;
C, service end access corresponding database according to the access request of service end through data access layer, access after service end the data of access are fed back to client terminal again.
In the aforesaid quick Development Framework of the mis system based on SAAS pattern, described service end realizes the database that class can access respective type through accordingly.
In the aforesaid quick Development Framework of the mis system based on SAAS pattern, first described client terminal realizes the client terminal interface specification under card i/f layer before being loaded, under the dynamic base generated is put into the plugins catalogue of master routine, client terminal can be loaded automatically when master routine runs.
In the aforesaid quick Development Framework of the mis system based on SAAS pattern, described client terminal by communication layers access services end time, by under communication layers static method conduct interviews.
In the aforesaid quick Development Framework of the mis system based on SAAS pattern, when described client terminal is by static method access services end, after static method operate services end, return an information object ServiceMsg.
In the aforesaid quick Development Framework of the mis system based on SAAS pattern, when described service end is by client-access, service end by realize service end interface specification then according to the access request of client terminal by client call.
In the aforesaid quick Development Framework of the mis system based on SAAS pattern, the described Dao object under service end accessing database data access layer and DaoTool object accesses.
Compared with prior art, the client terminal of the present invention is before being loaded, first realizing client terminal interface specification, client terminal can be loaded when master routine runs under being placed to the plugins catalogue of master routine by its dynamic base generated automatically, pass through which, when developer develops client terminal again, it is not necessary to carry out low level development again, namely without the need to again the interface of client plug-in being carried out secondary development, developer only needs relation business logic development, thus improves development efficiency. Realize the communication between client terminal and service end by YtClient.dll (i.e. communication layers) simultaneously, during communication, the YtService.dll (i.e. service application layer) of service end by the distribution of services to be accessed to corresponding service end, the database of the respective type that service end is called by YiTian.dll (i.e. data access layer) according to the access of client terminal again, now client terminal just can call the business of corresponding service end; By above-mentioned Development Framework, developer has been embedded in Development Framework in the bottom architecture (such as card i/f, database access) of exploitation business required exploitation in early stage, developer carries out overlapping development again without the need to spended time and energy, and this just effectively improves development efficiency, shortens the construction cycle; Moreover, also reduce development difficulty, developer only need to be absorbed in the realization of business logic, the realization of the bottom business such as data communication, database access need not be concerned about, thus greatly reduce the technical ability requirement of developer, only need developer to be familiar with the programming knowledge of the performance layers such as WinForm, ASP.NET, the business management system based on cloud Data centre can be realized fast.
Accompanying drawing explanation
Fig. 1 is the system architecture figure of the present invention.
Embodiment
Below in conjunction with drawings and Examples, the present invention is further illustrated, but not as the foundation that the present invention is limited.
Embodiment 1. Based on the quick Development Framework of mis system of SAAS pattern, as shown in Figure 1, this framework comprises:
Operation frame layer, i.e. YtMain.dll procedure set, for realizing main interface when program is run and the management to plug-in unit and the loading to master data;
Communication layers, i.e. YtClient.dll procedure set, for realizing communicating of client terminal and service end;
Service application layer, i.e. YtService.dll procedure set, distribute for realizing the process to business and realize the Row control to business;
Data access layer, i.e. YiTian.dll procedure set, for realize the access to database and to the support of multitype database;
Card i/f layer, i.e. YtPlugin.dll procedure set, for defining the basic interface of system cloud gray model plug-in unit, be namely integrated with client terminal interface specification, service end interface specification and database interface specification in card i/f layer; Client terminal interface specification, loads client terminal for realizing master routine; Service end interface specification, for the communication realized between client terminal and service end; The communication of database interface specification for realizing between service end and database.
Aforesaid quick Development Framework also comprises interface control layer, i.e. YtWinContrl.dll procedure set, and described interface control layer is for realizing the expansion to the basic control of client terminal.
Aforesaid quick Development Framework works in the steps below:
A, operation frame layer are after loading master data, then define corresponding client plug-in interface by card i/f layer, and client terminal can be loaded, and client terminal to be realized client terminal interface specification and could be loaded by master routine;
After b, client terminal are loaded, client terminal is by communication layers access services end, and now the access request of client terminal is distributed to corresponding service end by service application layer;
C, service end access corresponding database according to the access request of service end through data access layer, during access, service end by realizing accordingly class access corresponding database, access after service end the data of access are fed back to client terminal again.
Aforesaid service end can access dissimilar database; The type of described database comprises MSSQL, ORACLE, DB2 etc. During access, service end realizes class access MSSQL database by MSSQL, realizes class access ORACLE database by ORACLE, realizes class access DB2 database by DB2, realizes class accordingly by other and access other corresponding relevant databases. Aforesaid when realizing class accessing database, it is necessary to fulfillment database interface specification. By this database interface specification, service end has unified database interface and query criteria, different databases is allowed to support unified query grammar, and the above-mentioned class that respectively realizes has been embedded in quick Development Framework, allow developer without the need to being concerned about that various disparate databases grammer is different, thus alleviate the difficulty to database development.
First aforesaid client terminal realizes the client terminal interface specification under card i/f layer before being loaded, and under the dynamic base of generation is put into the plugins catalogue of master routine, can client terminal automatically be loaded when master routine runs. By which, when developer develops client terminal again, it is not necessary to carry out low level development again, namely without the need to again the interface of client plug-in being carried out secondary development, developer only needs relation business logic development, thus achieves quick exploitation. The dynamic base of described master routine comprises YiTian.dll, YtClient.dll, YtDict.dll (the synchronous storehouse of dictionary, basis), YtJsEngine.dll (JS script applications storehouse), YTMain.dll, YtPlugin.dll, YtSys.dll (system initialize storehouse), YtUtil.dll (public function class storehouse) and YtWinContrl.dll.Each module of described client terminal comprises YiTian.dll, YtClient.dll, YtDict.dll, YtPlugin.dll, YtSys.dll, YtUtil.dll and YtWinContrl.dll.
When aforesaid client terminal is by communication layers access services end, conducted interviews by the static method under communication layers. Fast access can be realized by static method.
The object of client-access service end is that LData, LData provide the access to service end, and it comprises inquiry, performs and preserves data etc.; Some of them parameter is provided by SvrParam object.
The method of LData object is:
1.DataTableLoadDataTable(stringkey,paramsobject[]pa)
Key corresponding with service end configuration ID
Pa is the parameter needed for inquiry
Obtaining service end inquiry DataTable service end default query interface is Find
2.DataTableLoadDataTable(stringkey,stringDbConn,paramsobject[]pa)
DbConn data cube computation
3.stringExe(stringkey,stringDbConn,paramsobject[]pa)
Perform service end inquiry return first trip first
Service end default query interface is Find
It is equivalent to stringEs (stringkey, stringDbConn, paramsobject [] pa)
4.staticboolDo (stringkey, Dictionary<string, object>param) performs service end operation
The OPT configuration ID of Key service end
Param parameter sets
Execution service end operates, true success, false failure
5.staticboolDo(stringkey,stringDbConn,Dictionary<string,object>param)
DbConn data cube computation
6.staticboolDo(SvrParamsvr)
Perform the method service end parameter object SvrParam specified
7.ServiceMsgExe (SvrParamsvr) executable operations returns service end information.
When aforesaid client terminal is by static method access services end, after static method operate services end, return an information object ServiceMsg, namely server return message is provided. Information object ServiceMsg, the running condition of timely aware service end can be passed through. Described ServiceMsg can be simple data type, it is also possible to be two dimension table data sets.
The attribute of ServiceMsg object is:
Whether boolSuccess service end performs successfully;
The information of stringMsg service end prompting;
The method of ServiceMsg object is:
1.DataTableGetDataTable()
Obtain data that server end returns and it is converted into DataTable
2.DataTableGetDataTable(intindex)
Obtain, by parameter index, data that server end returns and it is converted into DataTable customer side and returns multiple parameter array mode and return;
3.stringGetValue()
Obtain data that server end returns and it is converted into String;
4.stringGetValue(intindex)
Obtain, by parameter index, data that server end returns and it is converted into String.
When aforesaid service end is by client-access, service end must realize service end interface specification could according to the access request of client terminal by client call. By the interface specification of uniform service end, allow developer without the need to when the business of exploitation without the need to again from the interface exploitation of bottom, and only need to be concerned about the exploitation of business logic so that development more simply, development amount reduces greatly, then development efficiency is improved, it is achieved develop fast.
The parameter object of client-access service end is SvrParam;
The instantiation method of SvrParam object is:
1.SvrParam(stringAction,stringDbConn)
The business object access realizing IEx of Action access services end comprises name space+class name
The DataBase combining of DbConn access services end is for sky is then for acquiescence connects this access generally providing multiple database
2.SvrParam(stringAction,stringDbConn,stringsql)
The control tactics that Sql is id or oneself definition that service end XML configures OPT is obtained by the Sql attribute of service end data.
The method of SvrParam object is:
1.SvrParamAdd (stringk, objectobj) adds the parameter of service end
The value that the parameter name obj that K is corresponding is corresponding
2.Adds (Dictionary<string, object>a) add parameter in batches
3.SvrParamAddParam (paramsobject [] pa) arranges the parameter of the implicit queries of service end.
Dao object under aforesaid service end accessing database data access layer or DaoTool object accesses. Described DaoTool is the expansion to Dao, it is possible to by database manipulation configuration file to the access of database, such as inquiry, preservation, renewal, deletion etc. Described Dao object implementatio8 is to the elementary operation of disparate databases; Described DaoTool object provides a series of basic skills being configured fast access database by XML;
The instantiation method of Dao object is,
1.Dao(stringclassName,stringconnStr)
ClassName realizes class, and this place is, name space+assembly name
ConnStr connects character string
2.Dao(stringappkey)
The key corresponding in appconfig of appkey be connected character string paired [key] and [key_Conn]
The method of Dao object is,
1. return inquiry first trip first
objectExecuteScalar(stringSelectStr)
It is equivalent to objectEs (stringSelectStr)
ObjectExecuteScalar (stringSelectStr, object [] param) band parameter note in sql improve parameter unification with "? " number coupling, as dao.ExecuteScalar (" select*fromttfromwhereid=? ", newobject [] 1});
It is equivalent to objectEs (stringSelectStr, object [] param)
2. return affected line number
intExecuteNonQuery(stringSelectStr)
It is equivalent to intEn (stringSelectStr)
IntExecuteNonQuery (stringSelectStr, object [] param) band parameter
It is equivalent to intEn (stringSelectStr, object [] param)
3. return the DataTable of inquiry
DataTableFind(stringSelectStr)
It is equivalent to DataTableFd (stringSelectStr)
DataTableFind (stringSelectStr, object [] param) band parameter
It is equivalent to DataTableFd (stringSelectStr, object [] param).
The configuration of database XML operation is described as follows:
The configuration file of accessing database is made up of multiple operative configuration, and wherein the ID of operative configuration is unique in whole configuration.
Operative configuration comprises the inquiry to data, newly-increased, renewal and deletion thereof etc.
The xml document of configuration can be multiple but must be positioned at service end bin conxml under catalogue, and operation must be included in<opts>node;
The configuration of inquiry is as follows:
Above-mentioned being configured for performs an inquiry, and query configuration comprises implicit expression parameter pattern and explicit parameter pattern, as:
Wherein "? " representing the parameter that inquiry needs, this parameter has the AddParam method of the SvrParam object of customer side to arrange, and this is exactly implicit expression parameter pattern query;
As:
Wherein "? " from left to right with Pa parameter from top to bottom this parameter of one_to_one corresponding arrange by the Add method of the SvrParam object of customer side, this is exactly explicit parameter pattern query.
The configuration that database preserves is as follows:
Being configured for of above-mentioned preservation preserves data or more new data, wherein " key " is the major key of table, multiple major key uses "; " separately, the title that " table " is table, the field that " Pa " is correspondence database, the field name that " name " is correspondence database, " update ", for whether upgrading this field, is defaulted as true.
The method that DaoTool object provides is static method, and the method is specific as follows:
The method that 1.longSeq (Daodao, stringsequenceName) obtains sequence is generally used for Oracle database
2.intSave (Daodao, stringkey, OptDatadata) preserves data by configuration ID, and wherein key is the configuration ID of operation in XML, and data is the parameter sets that service end is passed in customer side
IntSave (Daodao, stringkey, Dictionary<string, object>param) is the same, and just parameter is provided by Dictionary<string, object>object
3.intUpdate (Daodao, stringkey, OptDatadata) upgrades database information by configuration ID
intUpdate(Daodao,stringkey,Dictionary<string,object>param)
4.intExecuteNonQuery (Daodao, stringop, OptDatadata) performs by configuration ID to return affected row
intExecuteNonQuery(Daodao,stringkey,Dictionary<string,object>param)
5.ObjItemExecuteScalarDaodao, stringop, OptDatadata) performed by configuration ID to return first trip first, the ObjItem object returned can be converted to other base types
ObjItemExecuteScalar(Daodao,stringkey,Dictionary<string,object>param)
Other method is similar, has and returns DataTable, returns Dictionary<string, object>, similar.
Built-in business in Fig. 1 includes the business such as login, form and right assignment.
Claims (9)
1. the quick Development Framework of the mis system based on SAAS pattern, it is characterised in that, this framework comprises:
Operation frame layer, for realizing main interface when program is run and the management to plug-in unit and the loading to master data;
Communication layers, for realizing communicating of client terminal and service end;
Service application layer, distributes for realizing the process to business and realize the Row control to business;
Data access layer, for realize the access to database and to the support of multitype database;
Card i/f layer, for defining the basic interface of system cloud gray model plug-in unit.
2. the quick Development Framework of the mis system based on SAAS pattern according to claim 1, it is characterised in that: this framework also comprises interface control layer, and described interface control layer is for realizing the expansion to the basic control of client terminal.
3. the quick Development Framework of the mis system based on SAAS pattern according to claim 1 and 2, it is characterised in that, this framework works in the steps below:
A, operation frame layer are after loading master data, then define corresponding client plug-in interface by card i/f layer, and client terminal can be loaded;
After b, client terminal are loaded, client terminal is by communication layers access services end, and now the access request of client terminal is distributed to corresponding service end by service application layer;
C, service end access corresponding database according to the access request of service end through data access layer, and after access, the data of access are fed back to client terminal by service end again.
4. the quick Development Framework of the mis system based on SAAS pattern according to claim 3, it is characterised in that: described service end realizes the database that class can access respective type through accordingly.
5. the quick Development Framework of the mis system based on SAAS pattern according to claim 3, it is characterized in that: the client terminal interface specification that first described client terminal realizes under card i/f layer before being loaded, under the dynamic base generated is put into the plugins catalogue of master routine, client terminal can be loaded automatically when master routine runs.
6. the quick Development Framework of the mis system based on SAAS pattern according to claim 3, it is characterised in that: when described client terminal is by communication layers access services end, conducted interviews by the static method under communication layers.
7. the quick Development Framework of the mis system based on SAAS pattern according to claim 6, it is characterised in that: when described client terminal is by static method access services end, after static method operate services end, return an information object ServiceMsg.
8. the quick Development Framework of the mis system based on SAAS pattern according to claim 3, it is characterized in that: when described service end is by client-access, service end by realize service end interface specification then according to the access request of client terminal by client call.
9. the quick Development Framework of the mis system based on SAAS pattern according to claim 3, it is characterised in that: the described Dao object under service end accessing database data access layer and DaoTool object accesses.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201511027295.2A CN105653334B (en) | 2015-12-31 | 2015-12-31 | MIS system rapid development framework based on SAAS mode |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201511027295.2A CN105653334B (en) | 2015-12-31 | 2015-12-31 | MIS system rapid development framework based on SAAS mode |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105653334A true CN105653334A (en) | 2016-06-08 |
| CN105653334B CN105653334B (en) | 2020-02-18 |
Family
ID=56490125
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201511027295.2A Active CN105653334B (en) | 2015-12-31 | 2015-12-31 | MIS system rapid development framework based on SAAS mode |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105653334B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110633163A (en) * | 2019-09-26 | 2019-12-31 | 深圳市七星石科技有限公司 | Development method for preventing application program from crashing based on multi-process server |
| CN111399943A (en) * | 2020-03-12 | 2020-07-10 | 网易（杭州）网络有限公司 | Data processing method, device, storage medium and electronic device |
| CN112860346A (en) * | 2021-03-05 | 2021-05-28 | 成都智造天下科技有限公司 | Plug-in type desktop client system and access method thereof |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103002034A (en) * | 2012-12-03 | 2013-03-27 | 华中科技大学 | Application QoS (Quality of Service) management system based on cloud service bus and operation method thereof |
| CN104866976A (en) * | 2015-06-01 | 2015-08-26 | 北京圆通慧达管理软件开发有限公司 | Multi-tenant-oriented information managing system |
| CN104991760A (en) * | 2014-12-23 | 2015-10-21 | 广州亦云信息技术有限公司 | PaaS platform service management system based on distributed modular technology and realization method |
-
2015
- 2015-12-31 CN CN201511027295.2A patent/CN105653334B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103002034A (en) * | 2012-12-03 | 2013-03-27 | 华中科技大学 | Application QoS (Quality of Service) management system based on cloud service bus and operation method thereof |
| CN104991760A (en) * | 2014-12-23 | 2015-10-21 | 广州亦云信息技术有限公司 | PaaS platform service management system based on distributed modular technology and realization method |
| CN104866976A (en) * | 2015-06-01 | 2015-08-26 | 北京圆通慧达管理软件开发有限公司 | Multi-tenant-oriented information managing system |
Non-Patent Citations (2)
| Title |
|---|
| 张燕妮: "基于SaaS平台及通用数据交换的业务协同售后配件管理系统设计与实现", 《中国优秀硕士学位论文全文数据库 信息科技辑》 * |
| 罗日新: "面向SAAS应用的多租户数据管理系统研究与实现", 《中国优秀硕士学位论文全文数据库 信息科技辑》 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110633163A (en) * | 2019-09-26 | 2019-12-31 | 深圳市七星石科技有限公司 | Development method for preventing application program from crashing based on multi-process server |
| CN110633163B (en) * | 2019-09-26 | 2022-12-09 | 深圳市七星石科技有限公司 | Development method for preventing application program from crashing based on multi-process server |
| CN111399943A (en) * | 2020-03-12 | 2020-07-10 | 网易（杭州）网络有限公司 | Data processing method, device, storage medium and electronic device |
| CN111399943B (en) * | 2020-03-12 | 2022-11-22 | 网易（杭州）网络有限公司 | Data processing method, device, storage medium and electronic device |
| CN112860346A (en) * | 2021-03-05 | 2021-05-28 | 成都智造天下科技有限公司 | Plug-in type desktop client system and access method thereof |
| CN112860346B (en) * | 2021-03-05 | 2023-04-28 | 成都云隆科技有限公司 | Plug-in desktop client system and access method thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105653334B (en) | 2020-02-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20200334248A1 (en) | Background format optimization for enhanced queries in a distributed computing cluster | |
| KR101621137B1 (en) | Low latency query engine for apache hadoop | |
| US10275278B2 (en) | Stream processing task deployment using precompiled libraries | |
| US9690822B2 (en) | System and method for metadata level validation of custom setup objects | |
| CN109857755B (en) | Rule checking method and device | |
| US20200019552A1 (en) | Query optimization method and related apparatus | |
| CN105630488A (en) | Docker container technology-based continuous integration realizing method | |
| JP2021513694A (en) | Dark Roch Realization Method, Equipment, Computational Nodes and Systems | |
| CN104781809A (en) | Container database | |
| US10394805B2 (en) | Database management for mobile devices | |
| US11086841B1 (en) | Streams on shared database objects | |
| CN104572122A (en) | Software application data generating device and method | |
| US20120158453A1 (en) | Workflow processing system for supporting multi-tenant, and method thereof | |
| CN101248416A (en) | Component architecture | |
| CN108536778A (en) | A kind of data application shared platform and method | |
| Valvåg et al. | Cogset: a high performance MapReduce engine | |
| CN106020847A (en) | Method and device for configuring SQL for persistent layer development framework | |
| CN105653334A (en) | Rapid development framework for MIS system based on SAAS mode | |
| CN103678591A (en) | Device and method for automatically executing multi-service receipt statistical treatment | |
| CN113010561B (en) | Data acquisition method and device based on super account book and computer system | |
| CA3193213A1 (en) | Analytics platform for federated private data | |
| KR20210040322A (en) | Scheduling method and apparatus, device and storage medium | |
| US9779177B1 (en) | Service generation based on profiled data objects | |
| CN109067558A (en) | data service method and system | |
| CN105208095A (en) | Filtering service deployment recommendation device and method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |