CN103618762A - System and method for enterprise service bus state pretreatment based on AOP - Google Patents
System and method for enterprise service bus state pretreatment based on AOP Download PDFInfo
- Publication number
- CN103618762A CN103618762A CN201310554404.0A CN201310554404A CN103618762A CN 103618762 A CN103618762 A CN 103618762A CN 201310554404 A CN201310554404 A CN 201310554404A CN 103618762 A CN103618762 A CN 103618762A
- Authority
- CN
- China
- Prior art keywords
- aop
- service
- esb
- tangent plane
- module
- 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
Images
Abstract
The invention relates to a system and method for enterprise service bus state pretreatment based on AOP. According to the system, an AOP module is added to a prior ESB framework system and the AOP aspect treating function is added to services of an ESB server side by the AOP module. An AOP aspect is established in the AOP module in advance and the content such as AOP point cut conditions and advice motions of the AOP module is defined. On the premise that a deployed service code is not changed, a service process is redefined or a new service function is added; meanwhile, when service demands are changed, the AOP aspect just needs to be reestablished in the AOP module by the ESB server side, the AOP point cut conditions and/or the advice motions are defined, so that new service demands are met, the service expansibility is strong, and the flexibility is high.
Description
Technical field
The present invention relates to the software development applied technical field of Service-Oriented Architecture Based, relate in particular to a kind of ESB state pretreatment system and method based on towards tangent plane programming (Aspect Oriented Programming, AOP).
Background technology
At present, in software development applied technical field, Enterprise SOA (Service Oriented Architecture, SOA) is a kind of popular software architecture.It is a kind of based on loose coupling, measured structure system, the different function units of application program (also claiming service) can be connected each other by defining good interface and contract.And ESB (Enterprise Service Bus, ESB) is an architecture of SOA.It is the integration mode of standard between a kind of service in loose coupling and application, for providing a kind of based on information transmission or event driven architecture between different, complicated frameworks.As shown in Figure 1, ESB couples together service and the mode of client by network, and service may operate on one or more ESB node, and each ESB node can be a physical machine or virtual machine, and can move a plurality of Service Instances on a machine.ESB adopts the host-host protocol of standard to connect different FTP client FTPs, for example FTP(file transfer protocol (FTP)), HTTP(HTTP), provide service-oriented application, such as information processing, filtration, data processing, route and information storage etc.Conventionally, ESB also operates in ESB service end with the form of service, and with message, carries out alternately between client, and the information receiving is reasonably sequentially carried out to message reprocessing with one.At present, ESB skeleton can be processed different message or event effectively, but but message or event can not be routed directly to a destination service.In other words, ESB must be in a service processing class judges that by service code message or the entrained condition of event call another one and serve, and its framework itself cannot be routed directly to message or event by condition judgment the destination service of appointment in advance.As shown in Figure 1, be in ESB service end by a message the existing execution mode from a service routing to an other service.In this embodiment, service A and service B need to be responsible for Message Processing fast, and when the size of message is greater than 50KB, service A and service B pass to service D by message; And service C does not have such business demand.In order to realize above-mentioned functions, in the code of service A and service B, add and have following logic, if the size of message is greater than 50KB (if (message_size) >50KB), message is passed to service D.This traditional implementation method has a weakness,, when business demand changes, for example, while needing message capacity extensions to arrive 75KB, the logical code that technical staff need to remodify in service A and service B meets new business demand, correspondingly, the code relevant with service B to service A, and other affected codes all need to recompilate.In like manner, if service C also needs this business function, the code of service C also needs to change and recompilate.This has brought inconvenience to the maintenance and expansion work in later stage.
Summary of the invention
For the problems referred to above, the invention provides a kind of ESB state pretreatment system and method based on towards tangent plane programming (Aspect Oriented Programming, AOP).Based on this system, ESB can be carried out operation bidirectional when not changing the service code of having disposed.
The invention provides a kind of ESB state pretreatment system based on AOP, it is characterized in that, comprising:
ESB service end, itself and client are carried out information interaction, and are deployed with the service that object that described client is sent is processed;
AOP module, its service configuration AOP tangent plane to described ESB service end deploy, for when the service of ESB service end deploy described in the object requests that described client is sent, whether the status attribute that detects described object meets the AOP cutting point condition in described AOP tangent plane, if met, carry out the notification action in described AOP tangent plane.
According to embodiments of the invention, above-mentioned ESB service end and AOP module may operate in an ESB node or operate in different ESB nodes.
In addition, the present invention also provides a kind of method of work of said system, comprises the following steps:
During the service of the object requests ESB service end deploy of sending when client, whether the status attribute of detected object meets the AOP cutting point condition in the AOP tangent plane of AOP module, if met, carries out the notification action in AOP tangent plane.
Particularly, during the service of the object requests ESB service end deploy of sending when client, before ESB enters service processing flow process and/or after ESB enters service processing flow process, whether the status attribute of detected object meets the AOP cutting point condition in AOP tangent plane.
In above-mentioned steps, when business demand changes, ESB service end rebuilds AOP tangent plane in AOP module, definition AOP cutting point condition and/or notification action.
In addition,, after the notification action in carrying out AOP tangent plane, can directly finish or continue to carry out former service processing flow process.
Above-mentioned notification action refers to when AOP cutting point condition meets, and needs the operation bidirectional of carrying out.
Above-mentioned notification action can comprise object is routed to the second service ESB service end from the first service of its request.
Above-mentioned notification action can be included in existing service processing flow process and add operation bidirectional, keeps this to serve original processing simultaneously and moves constant.
Above-mentioned notification action comprises definition and the identical destination service of initial service content, as the backup of initial service.
Above-mentioned AOP cutting point condition can comprise the required time of this object of service processing of object requests.
Above-mentioned AOP cutting point condition can comprise the contained amount of information size of object.
Compared with prior art, the beneficial effect that the present invention brings is:
The present invention integrates AOP module in ESB service end, utilizes the tangent plane processing capacity of AOP module under the prerequisite of not changing the service code of having disposed, redefine operation flow or increase new business function; Simultaneously, when business demand changes, ESB service end only need rebuild AOP tangent plane in AOP module, definition AOP cutting point condition and/or notification action, after revising code, only need recompilate and can meet business change demand the tangent plane code in AOP module, business autgmentability is strong, and flexibility ratio is high.
Object of the present invention and other advantages can also be realized and be obtained by specifically noted structure in specification, claims and accompanying drawing.
Accompanying drawing explanation
Accompanying drawing is used to provide a further understanding of the present invention, and forms a part for specification,, jointly for explaining the present invention, is not construed as limiting the invention with embodiments of the invention.In the accompanying drawings:
Fig. 1 is that in existing ESB structure system, message is transferred to the schematic diagram of another service from a service;
Fig. 2 is a kind of ESB service network structure figure that comprises state pretreatment system provided by the invention;
Fig. 3 is that state pretreatment system provided by the invention is transferred to message the method schematic diagram of another service from a service;
Fig. 4 is the flow chart of the overall work method of state pretreatment system provided by the invention.
Embodiment
As shown in Figure 2, be a kind of ESB service network structure figure that comprises the ESB state pretreatment system based on AOP of the present invention.This network architecture comprises an ESB service end and one or more client:
Unlike the prior art, in the present invention, ESB service end disposes AOP module, can add towards tangent plane programming.In an embodiment of the present invention, the AOP module of ESB service end and configuration preferably operates in an ESB node, or operates in different nodes.This ESB node can be one or many machines, for example server, gateway or other computing systems, and operation has one or more Service Instance.The data that Service Instance, AOP module, ESB service end are required or code storage are in the data storage cell of this ESB node, by ESB service end read access.This data storage cell can comprise one or more memory device, can be both the storage directory that ESB node carries itself, can be to be also independent of ESB node other memory devices in addition.
Client can be computing equipment arbitrarily, as notebook, desktop computer, server, mobile phone or palmtop PC PDA etc.In an embodiment of the present invention, preferably, client is the station server in enterprise.
Between client and ESB service end, by network, be connected, this network can be private network or public network.Private network comprises Local Area Network, outer dimension net (WAN) or corporate intranet (Intranet) etc.Public network can be internet (Internet).In common application, client is generally by standard transmission protocol (FTP, HTTP) and ESB service end exchange message.For example, the application of client running client, initiate HTTP request, and reception represents the result that ESB service end is returned in the mode of user interface (GUI) to ESB service end.The request that ESB service end is sent according to client, calls the service processing action of deployment, and this service can be the function point that or a plurality of method realize, and can be system service and User Defined service.Wherein, system service comprises route, safety management (encrypt, decipher), transaction management, log management etc., and User Defined service comprises that any user is with the code of resource form issue.
In addition, client is also produced such as message or event etc. and is needed the object of the service processing in ESB service end by operation CLIENT PROGRAM.For example, client is moved CLIENT PROGRAM and is produced message, and this message is sent in the message queue in ESB service end.The service being deployed in ESB service end is monitored or detects the message queue in ESB service end, message is made to corresponding processing.And in the present invention, dispose the ESB service end of AOP module before entering this service processing flow processing or after entering this service processing flow processing, status attribute that can detect-message, when the status attribute of message meets certain condition, just then carry out some operation bidirectionals.Here operation bidirectional comprises can not affect existing service processing flow process, extra one or more operations of adding.Embodiment is the main code utilizing towards one or more operation of tangent plane programming AOP technique construction, it not only can not affect the service code of having disposed in the code of client or ESB service end, but also can meet different clients or different ESB service ends, or the identical functional requirement of different service in same ESB service end.In an embodiment of the present invention, can be for system manager provides a control platform in ESB node, for increasing, revise or delete these operation bidirectionals.
Before introducing ESB service end how faying face increases, revises to tangent plane programming AOP technology or deletes operation bidirectional, first introduce briefly towards some Essential Terms and operation principle in tangent plane programming AOP technology.In object based programming (Object Oriented Programming, OOP), as java, c++ etc., a calculation procedure can be divided into separate module, and each module is comprised of one section of code, forms an individuality with standalone feature.And according to the needs of business, some system-level service code need to write in these modules across.These system-level services comprise safety management, data logging, session management and purview certification etc.And be used for exactly managing these system-level service code towards tangent plane programming.In tangent plane programming (Aspect Oriented Programming, AOP), these system-level service code are called tangent plane (aspect), and tangent plane comprises cutting point (pointcut) and notice (advice).Wherein, cutting point (pointcut) is should be cut into which tie point (jointpoint) of application program for defining notice (advice), for example method call, extremely dish out or field is revised, this coupling is accurately that the regular expression by cutting point defines; Notice (advice) is exactly that notification application removes to carry out the action code defining in tangent plane when tie point (jointpoint) arrives.This AOP technology can change the operation of original program or increase operation bidirectional on the basis of original program when not changing the service code of having disposed, and can revise neatly the executive condition of action and carry out content by revising tie point (jointpoint) or tangent plane (aspect).
In sum, the elementary tactics of the ESB state preprocess method based on AOP that the present invention proposes adds AOP module exactly in original ESB structure system, by AOP module, the service in ESB service end is added to tangent plane processing capacity.Specifically, in AOP module, build in advance tangent plane (aspect), comprise the contents such as definition its cutting point (pointcut) condition and notice (advice) action, for example, with when having object (message or event) request unit from client to be deployed in a service of ESB service end, detect the status attribute that this object is held, when the status attribute of object meets AOP cutting point condition, automatically perform the action in notice, thereby reach the technique effect that redefines operation flow or increase new business function under the prerequisite of not changing the service code of having disposed.
Said system can roughly be divided into following several situation when concrete application:
When object requests ESB service end provides a service, and before ESB not yet enters this service processing flow process, detect the status attribute that this object is held, if state information meets AOP cutting point condition, automatically perform the action in notice;
When object requests ESB service end provides a service, and after ESB entered this service processing flow process, detect the status attribute that this object is held, if state information meets AOP cutting point condition, automatically perform the action in notice;
Certainly, above-mentioned two situations also can combine utilization, when object requests ESB service end provides a service, before ESB enters this service processing flow process and all detect afterwards the status attribute that this object is held, if state information meets AOP cutting point condition, automatically perform the action in notice.
In addition, in above-mentioned three kinds of situations, after the action in carrying out notice, both can directly finish, also can return to the subsequent operation that continues to carry out former service processing flow process.
Which kind of situation no matter, a kind of ESB state pretreatment system and method based on AOP provided by the invention all has the following advantages: ESB service end utilizes the tangent plane processing capacity of AOP module under the prerequisite of not changing the service code of having disposed, redefine operation flow or increase new business function; Simultaneously, when business demand changes, for example: the business demand of former definition is for when the size of message is greater than 50KB, message is passed to service D, if new business demand need to be changed into when the size of message is greater than 100KB, message is passed to service D, and now ESB service end only need rebuild AOP tangent plane in AOP module, definition AOP cutting point condition and/or notification action.Be about to the change control of code in AOP inside modules, after modification code, only need recompilate and can meet business change demand the tangent plane code in AOP module, business autgmentability be strong, and flexibility ratio is high.
Below in conjunction with specific embodiment, further introduce the technique effect of technical scheme of the present invention and acquisition.
In an embodiment of the present invention, the cutting point about AOP technology in AOP module needs clear and definite following two contents:
1) initial service of object requests;
2) enter notice, carry out the trigger condition of notification action.
Action in notice refers to when AOP cutting point condition meets, and needs the operation bidirectional of carrying out.It can be by message or event from a service routing of ESB service end to another one service, for example, when AOP cutting point condition meets, message or event are transmitted to second service processing from first service; Also can be in existing service processing flow process, to add operation bidirectional and to keep this to serve original processing action constant simultaneously, for example, when AOP cutting point condition meets, with the mode reporting system keeper of mail.
As shown in Figure 3, the case of describing in background technology of still take is example, based on state pretreatment system provided by the invention, tangent plane program of AOP module compiles is in ESB service, in cutting point, defining initial service is service A and service B, and definition trigger condition is that message size is greater than predetermined threshold value; In notice, definition action is that this message is turned to destination service D.When client sends message to ESB service end, ESB service end can be mated this message with AOP cutting point condition default in AOP module, this message requests service A or service B detected, and when this message size is greater than predetermined threshold value, ESB carries out notification action, and this message is routed in service D and is processed.In service A or service B, do not comprise the above-mentioned logical code that message route is processed to service D, and the service content self providing is only provided.Therefore,, when professional qualification changes, for example, while needing message capacity to extend to 75KB from 50KB, without the code of revising service A and service B, only need in AOP module, reset AOP cutting point condition just can meet new business demand.
Similar with this, typical AOP cutting point condition can also be the required time of this object of service processing of object requests in initial service, or the contained amount of information size of object etc.When this AOP cutting point condition meets, ESB can, by message distribution in the service of appointment, then proceed the operation of original initial service processing flow process.This execution mode can be used for effectively preventing from refusing formula service attack, prevents when having jumbo message requests service, and resource is all occupied to be used for processing this message and without available resources, to process potential user's situation.In addition, in notice, can also define and the identical destination service of initial service content, as the backup of initial service.When message needs long time treatment or the message in message queue when too much, message can be forwarded in the destination service of backup and process.
As shown in Figure 4, be the flow chart of the overall work method of state pretreatment system provided by the invention.In this embodiment, in AOP module, by AOP tangent plane, in service processing flow process, add extra handling process, can keep again original processing action simultaneously:
When ESB service end receives object requests and is deployed in ESB service end one service, first detect this object and whether there is the status attribute conforming to AOP cutting point condition:
If had, AOP module enters AOP tangent plane routine processes flow process, thereby in the situation that not affecting former service code, carries out the action in tangent plane notice, then directly finishes;
If nothing, AOP module enters service processing flow performing and moves accordingly, in the processing procedure of this service, if object detected, there is the status attribute conforming to AOP cutting point condition, enter AOP tangent plane routine processes flow process, carry out the action in tangent plane notice, directly finish, otherwise finish after completing the original operation of service.
This additional act defining by AOP tangent plane can not affect the operation of the original operation of service.
In the above-described embodiments, AOP module preferably operates in ESB node, can adopt the AOP compiler compiling AOP module of JBoss, and for example ajc editing machine or abc editing machine, also can be not limited to this certainly, and conventional AOP compiler can be used at present.In addition, AOP module also may operate in the system platform beyond ESB node, does not also do concrete restriction.
The above; be only preferably embodiment of the present invention, but protection scope of the present invention is not limited to this, any those skilled in the art are in the disclosed technical scope of the present invention; the variation that can expect easily or replacement, within all should being encompassed in protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range of claim.
Claims (12)
1. the ESB state pretreatment system based on AOP, is characterized in that, comprising:
ESB service end, itself and client are carried out information interaction, and are deployed with the service that object that described client is sent is processed;
AOP module, its service configuration AOP tangent plane to described ESB service end deploy, for when the service of ESB service end deploy described in the object requests that described client is sent, whether the status attribute that detects described object meets the AOP cutting point condition in described AOP tangent plane, if met, carry out the notification action in described AOP tangent plane.
2. state pretreatment system as claimed in claim 1, is characterized in that:
Described ESB service end and AOP module operate in an ESB node or operate in different ESB nodes.
3. as a method of work for the ESB state pretreatment system based on AOP of claim 1 or 2, comprise the following steps:
During the service of the object requests ESB service end deploy of sending when client, whether the status attribute of detected object meets the AOP cutting point condition in the AOP tangent plane of AOP module, if met, carries out the notification action in AOP tangent plane.
4. method of work as claimed in claim 3, is characterized in that:
During the service of the object requests ESB service end deploy of sending when client, before ESB enters service processing flow process and/or after ESB enters service processing flow process, whether the status attribute of detected object meets the AOP cutting point condition in AOP tangent plane.
5. method of work as claimed in claim 3, is characterized in that:
When business demand changes, ESB service end rebuilds AOP tangent plane in AOP module, definition AOP cutting point condition and/or notification action.
6. method of work as claimed in claim 4, is characterized in that:
After notification action in carrying out AOP tangent plane, directly finish or continue to carry out former service processing flow process.
7. method of work as claimed in claim 3, is characterized in that:
Described notification action comprises object is routed to the second service ESB service end from the first service of its request.
8. method of work according to claim 3, is characterized in that:
Described notification action is included in and in existing service processing flow process, adds operation bidirectional to keep this to serve original processing action constant simultaneously.
9. method of work according to claim 8, is characterized in that:
Described operation bidirectional comprises does not affect existing service processing flow process, extra one or more operations of adding.
10. method of work according to claim 3, is characterized in that:
Described notification action comprises definition and the identical destination service of initial service content, as the backup of initial service.
11. method of works as claimed in claim 3, is characterized in that:
Described AOP cutting point condition comprises the required time of this object of service processing of object requests.
12. method of works as claimed in claim 3, is characterized in that:
Described AOP cutting point condition comprises the contained amount of information size of object.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310554404.0A CN103618762A (en) | 2013-11-08 | 2013-11-08 | System and method for enterprise service bus state pretreatment based on AOP |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310554404.0A CN103618762A (en) | 2013-11-08 | 2013-11-08 | System and method for enterprise service bus state pretreatment based on AOP |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN103618762A true CN103618762A (en) | 2014-03-05 |
Family
ID=50169466
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310554404.0A Pending CN103618762A (en) | 2013-11-08 | 2013-11-08 | System and method for enterprise service bus state pretreatment based on AOP |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103618762A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106844153A (en) * | 2017-01-20 | 2017-06-13 | 北京奇虎科技有限公司 | Application program operation and monitoring method, device and terminal |
| CN107168757A (en) * | 2017-03-31 | 2017-09-15 | 武汉斗鱼网络科技有限公司 | A kind of Android ends prevent View controls from clicking on the method and device of shake |
| CN107508793A (en) * | 2017-07-13 | 2017-12-22 | 微梦创科网络科技（中国）有限公司 | A kind of method and device based on towards tangent plane programming AOP certifications and mandate |
| CN108170407A (en) * | 2016-12-05 | 2018-06-15 | 中国移动通信有限公司研究院 | A kind of method and device for obtaining target data |
| CN108469979A (en) * | 2018-03-28 | 2018-08-31 | 深圳前海桔子信息技术有限公司 | A kind of method for page jump, device, server and storage medium |
| CN109144534A (en) * | 2017-06-28 | 2019-01-04 | 北京京东尚科信息技术有限公司 | Service module dynamic updating method, device and electronic equipment |
| CN111309409A (en) * | 2020-02-26 | 2020-06-19 | 山东爱城市网信息技术有限公司 | API service call real-time statistical method |
| CN111913813A (en) * | 2020-07-07 | 2020-11-10 | 上海泛微网络科技股份有限公司 | Data interaction processing method, device, equipment and storage medium |
| CN113672205A (en) * | 2021-08-25 | 2021-11-19 | 广州方舟信息科技有限公司 | Workflow framework based on business event driving |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101776995A (en) * | 2010-01-04 | 2010-07-14 | 北京航空航天大学 | Self-adaptive combined service optimization method and device |
| US20110295922A1 (en) * | 2010-05-25 | 2011-12-01 | Martin Vecera | Aspect oriented programming for an enterprise service bus |
| CN102932390A (en) * | 2011-08-11 | 2013-02-13 | 阿里巴巴集团控股有限公司 | Network request processing method and system, and network service providing device |
-
2013
- 2013-11-08 CN CN201310554404.0A patent/CN103618762A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101776995A (en) * | 2010-01-04 | 2010-07-14 | 北京航空航天大学 | Self-adaptive combined service optimization method and device |
| US20110295922A1 (en) * | 2010-05-25 | 2011-12-01 | Martin Vecera | Aspect oriented programming for an enterprise service bus |
| CN102932390A (en) * | 2011-08-11 | 2013-02-13 | 阿里巴巴集团控股有限公司 | Network request processing method and system, and network service providing device |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108170407A (en) * | 2016-12-05 | 2018-06-15 | 中国移动通信有限公司研究院 | A kind of method and device for obtaining target data |
| CN106844153A (en) * | 2017-01-20 | 2017-06-13 | 北京奇虎科技有限公司 | Application program operation and monitoring method, device and terminal |
| CN106844153B (en) * | 2017-01-20 | 2020-02-11 | 北京奇虎科技有限公司 | Application program operation monitoring method and device and terminal |
| CN107168757A (en) * | 2017-03-31 | 2017-09-15 | 武汉斗鱼网络科技有限公司 | A kind of Android ends prevent View controls from clicking on the method and device of shake |
| CN109144534A (en) * | 2017-06-28 | 2019-01-04 | 北京京东尚科信息技术有限公司 | Service module dynamic updating method, device and electronic equipment |
| CN107508793A (en) * | 2017-07-13 | 2017-12-22 | 微梦创科网络科技（中国）有限公司 | A kind of method and device based on towards tangent plane programming AOP certifications and mandate |
| CN108469979A (en) * | 2018-03-28 | 2018-08-31 | 深圳前海桔子信息技术有限公司 | A kind of method for page jump, device, server and storage medium |
| CN111309409A (en) * | 2020-02-26 | 2020-06-19 | 山东爱城市网信息技术有限公司 | API service call real-time statistical method |
| CN111309409B (en) * | 2020-02-26 | 2023-11-28 | 天元大数据信用管理有限公司 | Real-time statistics method for API service call |
| CN111913813A (en) * | 2020-07-07 | 2020-11-10 | 上海泛微网络科技股份有限公司 | Data interaction processing method, device, equipment and storage medium |
| CN113672205A (en) * | 2021-08-25 | 2021-11-19 | 广州方舟信息科技有限公司 | Workflow framework based on business event driving |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103618762A (en) | System and method for enterprise service bus state pretreatment based on AOP | |
| CN110677305B (en) | Automatic scaling method and system in cloud computing environment | |
| Taneja et al. | Resource aware placement of data analytics platform in fog computing | |
| CN105574082A (en) | Storm based stream processing method and system | |
| CN104618693A (en) | Cloud computing based online processing task management method and system for monitoring video | |
| CN104219316A (en) | Method and device for processing call request in distributed system | |
| CN101477386B (en) | Timer implementing method and apparatus | |
| CN106330575A (en) | Safety service platform and safety service deployment method | |
| CN112948063B (en) | Cloud platform creation method and device, cloud platform and cloud platform implementation system | |
| WO2020228063A1 (en) | Method and device for developing service functions | |
| CN103701633A (en) | Setup and maintenance system of visual cluster application for distributed search SolrCloud | |
| Zhang et al. | A survey of computational offloading in mobile cloud computing | |
| CN110210845B (en) | Method, apparatus, medium, and computing device for blockchain data migration | |
| CN103049268A (en) | Naplet based application development and management system | |
| CN111274007B (en) | Terraform-based cloud platform resource elastic expansion implementation method and system | |
| CN110555074A (en) | method for extracting and processing data at fixed time, terminal and computer readable storage medium | |
| CN111985906A (en) | Remote office system, method, device and storage medium | |
| CN103530538A (en) | XML safety view querying method based on Schema | |
| CN110674192A (en) | Redis high-availability VIP (very important person) drifting method, terminal and storage medium | |
| CN103927244A (en) | Plug-in scheduling process monitoring method implemented based on dynamic proxy | |
| CN109063216A (en) | A kind of distributed vertical service search crawler frame | |
| CN104123135A (en) | Method and device for unifying background interfaces | |
| CN108154343B (en) | Emergency processing method and system for enterprise-level information system | |
| CN106789380A (en) | A kind of virtual machine network integration supervisory systems | |
| CN113434268A (en) | Workflow distributed scheduling management system and method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20140305 |
|
| RJ01 | Rejection of invention patent application after publication |