CN109408067A - A kind of data managing method and server based on monomer applications - Google Patents
A kind of data managing method and server based on monomer applications Download PDFInfo
- Publication number
- CN109408067A CN109408067A CN201811227103.6A CN201811227103A CN109408067A CN 109408067 A CN109408067 A CN 109408067A CN 201811227103 A CN201811227103 A CN 201811227103A CN 109408067 A CN109408067 A CN 109408067A
- Authority
- CN
- China
- Prior art keywords
- module
- tenant
- deployment
- rented
- module release
- 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
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- 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/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a kind of data managing methods based on monomer applications, the logging request sent including receiving tenant's equipment, include tenant's identity information in the logging request；The corresponding tenant of tenant's identity information is inquired in tenant's information database and rents module release list, and it includes but is not limited to rented monomer applications module id and module release information that the tenant, which rents module release list,；Module release list, which is rented, according to the tenant loads respective modules version set；Object instance is chosen from deployment examples according to default deployment rule, the module release set rented is deployed to the object instance by incremental deploying mode.By supporting incremental deploying mode to realize, the discrepant tenant of multiple code releases still is able to share a deployment examples, so that existing software architecture assets are made full use of, the higher resource sharing capability of available resource utilization rate.
Description
Technical field
The present invention relates to computer application technology more particularly to a kind of data managing method based on monomer applications and
Server
Background technique
Conventional monomer application is typically deployed at user place, therefore substantially a user once disposes implementation.In order to
Reduce customized development cost, it will usually the customization demand of different user be abstracted, functional configuration is formed, in this way may be used
To guarantee different user as far as possible using a edition code, to reduce Maintenance Development cost.Customized demand abundant is carried out
It is abstract to require monomer applications that have good modularized design with functional configurationization.Nonetheless, conventional monomer, which is applied, is rising
Grade service, strange land deployment maintenance and implementation encounter many difficulties, for example upgrade not in time, and strange land deployment maintenance cost is too high.Institute
With, it is universal with cloud computing and Internet technology, SaaSization is carried out to the monomer applications towards medium-sized and small enterprises, it has also become IT clothes
One strategic direction of business company.
Currently, for conventional monomer application SaaSization there are several types of schemes: (1) monomer applications are deployed to cloud merely
End, a tenant dispose an application example.The advantages of this scheme is software architecture almost without that must be transformed, the disadvantage is that hardware resource
Utilization rate is low, and each enterprise disposes an application example, and resources costs are high.(2) application example is shared by multiple enterprises, each
Enterprise uses disparate databases.The advantages of such scheme is that software architecture transformation cost is low, the disadvantage is that requiring what tenant shared to answer
It must be consistent with example code version.If tenant has customization to require, need to dispose individual application example, due in
The business customizing demand multiplicity of small enterprise, so the program is often degenerated to scheme 1.It (3), will on the basis of scheme 2
Software function customizes code and transform function configurableization as, and configuration information is stored in the respective database of tenant, Zu Hu
Respective service function configuration information is read when using application function, to reach functional configuration purpose.The advantages of this scheme
It is that multiple tenants can share a deployment examples, the disadvantage is that software function configurationization transformation cost is higher, with configurableization
More and more, software is more and more abstract, becomes increasingly complex, higher to the skill requirement of exploitation, and remains that tenant shared
Application example code release must be consistent.(4) monomer applications micro services are transformed, i.e., split monomer applications, and to tearing open
Branching away micro services can independently dispose.The advantages of this scheme is that deployment and customization are very flexible, can both pass through code development
Mode the customization demand of tenant can also be realized by way of functional configuration.The disadvantage is that Software adapting cost is high, people
Force request is high, and needs to introduce the related infrastructures such as service improvement, increases the deployment and maintenance difficulties of system.Micro servicesization are another
One purpose is to meet high concurrent, but most of medium-sized and small enterprises are applied unlike Internet application has very high high concurrent to want
It asks.
For the application of most of medium-sized and small enterprises, the good monomer applications of traditional modular can be with cost
Telescopic SaaS shown in lesser above scheme 2, but greatest problem existing for such scheme be cannot be by increment type portion
Administration, reaches different code version and shares identical deployment running example.Therefore it when two edition code difference very littles, services simultaneously
Tenant it is few when, also have to redeploy an example, result in waste of resources.
Summary of the invention
The present invention aiming at the shortcomings in the prior art, provide it is a kind of making full use of existing software architecture simultaneously, obtain
The data managing method based on monomer applications of the higher resource sharing capability of resource utilization is obtained, shown method specifically includes:
The logging request that tenant's equipment is sent is received, includes tenant's identity information in the logging request；
The corresponding tenant of tenant's identity information is inquired in tenant's information database rents module release list, it is described
It includes but is not limited to rented monomer applications module id and module release information that tenant, which rents module release list,；
Module release list, which is rented, according to the tenant loads respective modules version set；
Object instance is chosen from deployment examples according to default deployment rule, the module release set rented is passed through
Incremental deploying mode is deployed to the object instance.
Preferably, the step chooses object instance from deployment examples according to default deployment rule, by what is rented
Module release set is deployed to the object instance by incremental deploying mode, further includes: when the loading index of deployment examples
When being more than respective instance threshold value, according to the independent deployment examples of module release set rented；Otherwise according to default deployment rule
Object instance then is chosen from the deployment examples that loading index is less than respective instance threshold value, the module release collection that will be rented
It closes and the object instance is deployed to by incremental deploying mode.
Preferably, the deployment rule is chooses identical molds block number in the module release set rented with tenant at most
Deployment examples are chosen when matched deployment examples have multiple and possess the least deployment examples of number of modules.
Preferably, the tenant rent module release list include but is not limited to tenant's identity information, rent application message,
The application module mark and module release information rented.
It preferably, include multiple versions of the same module of the monomer applications in the object instance.
Preferably, the data managing method further include:, will be each according to the ratio of each module request quantity and tenant's quantity
The module that ratio described in deployment examples has been greater than threshold value two, which pulls out, carrys out independent deployment examples.
The invention also discloses the methods that a kind of pair of monomer applications carry out SaaS transformation, specifically include:
According to each version information of monomer applications, to each module adding module version number in monomer applications；
When tenant rents, the rental module release list of tenant is recorded, the user rents module release list and includes
But it is not limited to rented application module mark and module release information；
After being connected to tenant's logging request, corresponding rental module release list is obtained according to tenant's identity information, according to institute
It states and rents module release list load respective modules version set；
Object instance is chosen from deployment examples according to default deployment rule, the module release set rented is passed through
Incremental deploying mode is deployed to the object instance.
Preferably, the method that SaaS transformation is carried out to monomer applications further include: obtain each module in specific time
The request processing cumulative time account for the ratio of all module total processing times, when the sum of preceding specific quantity module accounting of ranking
When more than threshold value two, micro services are converted into after being iterated deconsolidation process to the specific quantity module.
The invention also discloses a kind of server, including memory, processor and storage are in the memory and can
The computer program run on the processor, wherein the processor realizes such as aforementioned base when executing the computer program
In the data managing method of monomer applications the step of.
The invention also discloses a kind of computer readable storage medium, the computer-readable recording medium storage has calculating
Machine program realizes the step such as the aforementioned data managing method based on monomer applications when the computer program is executed by processor
Suddenly.
The present invention is by adding version number to module identification to monomer applications, so that the equal modules of different editions will be made
It is identified for disparate modules, then by incremental deployment, reaches different code version and share identical deployment running example.
Although solving traditional modularization monomer applications support module upgrading load function, the difference of equal modules is not supported
Version load causes after a certain tenant only customizes a certain module in monomer applications, even if two edition codes
Difference very little and when few service tenant, also have to individually to dispose and run again an example and caused by resource it is greatly unrestrained
The problem of taking.By the further transformations to monomer applications, low-cost monomer applications are transform as and have incremental deploying ability,
So that making full use of existing software architecture assets simultaneously, the higher resource sharing capability of available resource utilization rate has
Software adapting cost is low, and by supporting incremental deploying mode to realize, the discrepant tenant of multiple code releases still is able to shared one
A deployment examples obtain the higher SaaS ability of resource utilization to make full use of existing software architecture assets, can be extensively
The monomer applications good and with plug-in unit ability suitable for modularization.
Additional aspect and advantage of the invention will be set forth in part in the description, and will partially become from the following description
Obviously, or practice through the invention is recognized.
Detailed description of the invention
The drawings described herein are used to provide a further understanding of the present invention, constitutes part of this application, this hair
Bright illustrative embodiments and their description are used to explain the present invention, and are not constituted improper limitations of the present invention.In the accompanying drawings:
Fig. 1 is the flow diagram of the data managing method based on monomer applications disclosed in one embodiment of the invention.
Fig. 2 is the partial schematic diagram for the step S103 that one embodiment of the invention discloses.
Fig. 3 is the flow diagram of the disclosed method that monomer applications are carried out with SaaS transformation of one embodiment of the invention.
Fig. 4 is the deployment running example schematic diagram of monomer applications in the prior art.
Fig. 5, which is that one embodiment of the invention is disclosed, carries out the improved deployment running example signal of SaaS to monomer applications
Figure.
Fig. 6 is server architecture schematic diagram disclosed in one embodiment of the invention.
Specific embodiment
In order to make the object, technical scheme and advantages of the embodiment of the invention clearer, below in conjunction with the embodiment of the present invention
Attached drawing, the technical solution of the embodiment of the present invention is clearly and completely described.Obviously, described embodiment is this hair
Bright a part of the embodiment, instead of all the embodiments.Based on described the embodiment of the present invention, ordinary skill
Personnel's every other embodiment obtained under the premise of being not necessarily to creative work, shall fall within the protection scope of the present invention.
In the present invention unless specifically defined or limited otherwise, term " installation ", " connected ", " connection ", " fixation " etc.
Term shall be understood in a broad sense, for example, it may be being fixedly connected, may be a detachable connection, or be integrally connected；It can be machine
Tool connection, is also possible to be electrically connected；It can be directly connected, two members can also be can be indirectly connected through an intermediary
Connection inside part.For the ordinary skill in the art, above-mentioned term can be understood in this hair as the case may be
Concrete meaning in bright.
In the present invention unless specifically defined or limited otherwise, fisrt feature second feature "upper" or "lower"
It may include that the first and second features directly contact, also may include that the first and second features are not direct contacts but pass through it
Between other characterisation contact.Moreover, fisrt feature includes the first spy above the second feature " above ", " above " and " above "
Sign is right above second feature and oblique upper, or is merely representative of first feature horizontal height higher than second feature.Fisrt feature exists
Second feature " under ", " lower section " and " following " include that fisrt feature is directly below and diagonally below the second feature, or is merely representative of
First feature horizontal height is less than second feature.
Unless otherwise defined, the technical term or scientific term used herein should be in fields of the present invention and has
The ordinary meaning that the personage of general technical ability is understood.Used in present patent application specification and claims " the
One ", " second " and similar word are not offered as any sequence, quantity or importance, and are used only to distinguish different
Component part.Equally, the similar word such as "one" or " one " does not indicate that quantity limits yet, but indicates that there are at least one.
Attached drawing 1 is a kind of data managing method based on monomer applications disclosed in an embodiment, and this method is suitable for module
Change good, stateless monomer applications, wherein stateless application refers to that service condition is stored in database instance, rather than saves
It in application server, is such as applied based on the ERP of web, WMS, MES etc., the data method specifically comprises the following steps.
Step S101 receives the logging request that tenant's equipment is sent, believes in the logging request comprising tenant's identity
Breath.
Step S102 inquires the corresponding tenant of tenant's identity information in tenant's information database and rents module release
List, it includes but is not limited to rented monomer applications module id and module release letter that the tenant, which rents module release list,
Breath.
Specifically, increasing module release management to monomer applications, increase version number, specific monomer applications pair for each module
" module I D+ module release number " can be used in the identification of module, that is, uses format Mn.vn, wherein Mn represents module I D, and vn represents mould
Block version number, such as M1.v1, the v1 version of representation module 1.Wherein monomer applications version number be variation with module release and
Variation, so module release number can be with a certain edition code of unique identification module.When tenant rents, record the tenant's
Rent module release list.It includes but is not limited to rented monomer applications module that the tenant, which rents module release list,
Mark and module release information, the monomer applications module id can be module I D.In further embodiments, the tenant
Renting module release list may include but be not limited to tenant's identity information, the application module renting application message, being rented mark
With module release information, such as: tenant A rent monomer application version be r1 and rent module be M1.v1, M2.v1；Tenant B
It is identical with tenant A to rent module, but needs to be customized M2 module, it is version evolving for M2.v2 so as to cause M2.v1, due to
It is monomer applications so monomer applications are version evolving for R2.Thus our available tenant A, the rental list of B are respectively as follows:
(A, R1, (M1.v1, M2.v1))
(B, R2, (M1.v1, M2.v2))
Wherein A and B includes tenant's identity information.
Although not supporting equal modules due to traditional modularization monomer applications support module upgrading load function
Different editions load, cause after a certain tenant customizes a certain module in monomer applications, for the tenant
It is also required to individually dispose and run an example.But if tenant A and tenant B have rented many equal modules, and only M2
There is customization, then one similar example of independent deployment and operation will waste very much.To solve these problems, logical first
It crosses to monomer applications to module I D identification plus version number, so that the equal modules of different editions will be carried out as disparate modules
Identification, to facilitate subsequent load.
Step S103 rents module release list according to the tenant and loads respective modules version set.
As shown in Fig. 2, when tenant request arrives, the monomer applications are rented to obtain in relation list from tenant and be corresponded to
The rental relation list of tenant needs to include described on calling routing according to the corresponding rental module release list of the tenant
Tenant with the module I D and module release number in module release list, call the interface of corresponding Version module to complete at request
Reason.
Step S104 chooses object instance from deployment examples according to default deployment rule, the module version that will be rented
This set is deployed to the object instance by incremental deploying mode.
Specifically, the deployment rule can for choose and the module release set that be rented of tenant in identical molds block number most
More deployment examples are chosen when matched deployment examples have multiple and possess the least deployment examples of number of modules.Wherein,
If matching deployment examples have it is multiple, also can use first matched deployment examples.Wherein in one embodiment, institute
It is specific as follows to state step S104:
If newly renting module collection is N；K1, K2 ..., Kn are the example disposed, and Mkn indicates deployment examples Kn's
Rent module collection.Also, the element of all set does not repeat.
N^Mkn indicates the intersection of N and Mkn；
N+Mkn indicates the union of N and MKn；
N-Mkn indicates N to the difference set of Mkn；
Card indicates to take the element number of set；
1) search the example collection that Card (Nm^Mkn) is maximum Mkn, be denoted as SM, the element of SM be Mkx (1≤x≤
n)。
2) Card (Mkx) the smallest example collection to be searched, SN is denoted as, the element of SN is Mky (1≤y≤x),
If 3) SN is empty set, the deployment examples of newly-generated one empty module collection are denoted as Mks (s=1)；Else if
Card (SN) >=1 then takes out least first set of tenant's number from set SN, is denoted as Mks (1≤s≤y)；
4) set I is created, wherein I=N-Mks
5) set I is deployed to Mks example
In some embodiments, it is real to choose target according to default deployment rule from deployment examples by the step S104
Example, is deployed to the object instance by incremental deploying mode for the module release set rented, further includes:
When the loading index of deployment examples is more than respective instance threshold value, according to the module release set list rented
Only deployment examples；
Otherwise mesh is chosen from the deployment examples that loading index is less than respective instance threshold value according to default deployment rule
Example is marked, the module release set rented is deployed to the object instance by incremental deploying mode.
Wherein, the loading index can be tenant's quantity of each deployment examples, corresponding respective instance threshold value
It can be maximum tenant's quantity of deployment examples limitation.The restricted maximum tenant's quantity of each deployment examples, this be because
The tenant's quantity serviced by a deployment examples has the upper limit.This upper limit value depends on business and the user of actual software
Target is experienced, acquirement can be tested according to the actual situation, be exemplified below:
If having disposed following 3 examples, and set the upper limit of an example service as Tk, tenant's number Tk1=5 of K1；K2
Tenant's number be Tk2=8；Tenant's number of K3 is Tk3=10；It is another:
K1={ M1.v1, M2.v1, M4.v1, M4.v2 }
K2={ M1.v1, M2.v1, M5.v1, M6.v1, M7.v1 }
K3={ M1.v1, M2.v1, M9.v1 }
Rental module list now with new tenant is N={ M1.v1, M2.v1, M8.v1 }
According to above-mentioned default deployment rule N and K1, the intersection of K2, K3 are the same, but because of K1, the module of K3
Quantity is less than K2, and tenant number Tk1 < Tk3 of K1, so N will be deployed to K1.After deployment:
K1={ M1.v1, M2.v1, M4.v1, M4.v2, M8.v1 }.
It simultaneously from the foregoing, in the object instance may include multiple versions of the same module of the monomer applications, with
It is called for different tenants, without individually disposing a new example, provides resource utilization.
In further embodiments, the data managing method, further includes: according to each module request quantity and tenant's number
The module that respectively ratio described in deployment examples is greater than threshold value two is pulled out and carrys out independent deployment examples by the ratio of amount.The threshold
Value two can carry out using determination according to the actual situation.By setting up the ratio of module request quantity and tenant's quantity come contrast module
Utilization rate high utilization rate and the higher module of load can be pulled out and carry out independent deployment examples, to realize that satisfaction is single
The high scalability of body application.
The present embodiment is by adding version number to module I D identification to monomer applications, so that by the equal modules of different editions
It to be identified as disparate modules, then by incremental deployment, reach different code version and share identical deployment operation
Example.Although solving traditional modularization monomer applications support module upgrading load function, equal modules are not supported
Different editions load, cause after a certain tenant customizes a certain module in monomer applications, even if two versions
When the tenant of this code difference very little and service is few, also have to individually to dispose and run again an example and caused by money
The problem of source significant wastage.By the further transformation to monomer applications, low-cost monomer applications are transform as and have Leve
The incremental deploying ability of l4, so that available resource utilization rate is higher making full use of existing software architecture assets simultaneously
Resource sharing capability, it is low to have a Software adapting cost, by supporting incremental deploying mode to realize that multiple code releases are discrepant
Tenant still is able to share a deployment examples, to make full use of existing software architecture assets, obtain resource utilization compared with
High SaaS ability can be widely used in modularization well and the monomer applications with plug-in unit ability.
Attached drawing 3 is the method that a kind of pair of monomer applications carry out SaaS transformation disclosed in an embodiment, for good to modularization
Good monomer applications carry out low cost S aaS transformation, are suitble to towards enterprise's application more than medium-sized and small enterprises' personalized customization, such as
ERP, MES, WMS etc., the specific steps are as follows:
Step S201, according to each version information of monomer applications, to each module adding module version number in monomer applications.
Since traditional usual support module of modularization monomer applications upgrades replacement function, but do not support equal modules
Different editions load simultaneously.Therefore, it is necessary to be transformed to monomer applications, so that monomer applications use the identification of module
" module I D+ module release number ".And there are two types of modes when the monomer applications loading module of current SaaSization, one is upgradings to replace
It changes, another kind is newly-increased load.Obviously device resource will more effectively be saved using newly-increased loading method for multi-tenant,
Resource utilization is provided.And load while monomer applications can not support the equal modules of different editions at present, limit increment
The application of formula deployment.Therefore in the present embodiment, module release management first is increased to monomer applications, increases version for each module
Number, " module I D+ module release number " can be used to the identification of module in specific monomer applications, that is, uses format Mn.vn, wherein Mn generation
Table module I D, vn represent module release number, such as M1.v1, the v1 version of representation module 1.Wherein monomer applications version number be with
The variation of module release and change, so module release number can be with a certain edition code of unique identification module.
Step S202 records the rental module release list of tenant when tenant rents, and the user rents module release
List includes but is not limited to rented application module mark and module release information.
When tenant rents, the rental module release list of tenant A and tenant B are recorded.In some embodiments, such as tenant
A rental monomer application version is r1 and the module of rental is M1.v1, M2.v1；It is identical as tenant A that tenant B rents module, but needs
M2 module is customized, so as to cause M2.v1 it is version evolving be M2.v2, due to being monomer applications so monomer applications version
Originally it is evolved into r2.Thus our available tenant A, the rental list L of B:
(A, r1, (M1.v1, M2.v1))
(B, r2, (M1.v1, M2.v2))
Step S203 obtains corresponding module release of renting according to tenant's identity information and arranges after being connected to tenant's logging request
Table loads respective modules version set according to the rental module release list.
When tenant request arrives, the monomer applications rent in relation list the rental pass for obtaining corresponding tenant from tenant
Series of tables needs on calling routing to include that the tenant uses module according to the corresponding rental module release list of the tenant
Module I D and module release number in version list call the interface of corresponding Version module to complete request processing.
Step S204 chooses object instance from deployment examples according to default deployment rule, the module version that will be rented
This set is deployed to the object instance by incremental deploying mode.
Specifically, the deployment rule can for choose and the module release set that be rented of tenant in identical molds block number most
More deployment examples are chosen when matched deployment examples have multiple and possess the least deployment examples of number of modules.Wherein,
If matching deployment examples have it is multiple, also can use first matched deployment examples.
In further embodiments, the step further include ought the loading index of deployment examples be more than respective instance threshold
When value, according to the independent deployment examples of module release set rented；Otherwise do not surpassed according to default deployment rule from loading index
It crosses in the deployment examples of respective instance threshold value and chooses object instance, the module release set rented is passed through into incremental deploying side
Formula is deployed to the object instance.
The present embodiment adds version to module I D identification by increasing module release management to monomer applications, to monomer applications
Number, so that the equal modules of different editions will be identified as disparate modules, then by incremental deployment, reach different
Code release shares identical deployment running example.Although solving traditional modular monomer applications as shown in Fig. 4 to support
Module upgrade loads function, but does not support the different editions load of equal modules, causes only to answer monomer as a certain tenant
After a certain module in is customized, even if the tenant of two edition code difference very littles and service is few, also must not
Again individually deployment and operation one example and caused by resource significant wastage the problem of.By to the further of monomer applications
Monomer applications, are transform to low-cost as the incremental deploying ability for having Level4 by transformation, so that existing soft making full use of
Simultaneously, it is low to have Software adapting cost to part framework assets for the higher resource sharing capability of available resource utilization rate.Such as attached drawing 5
It is shown, by the improved monomer applications of SaaS described in the present embodiment, by supporting incremental deploying mode to realize multiple codes
The discrepant tenant of version still is able to share a deployment examples, to make full use of existing software architecture assets, obtains
The higher SaaS ability of resource utilization can be widely used in modularization well and the monomer applications with plug-in unit ability.
In further embodiments, the method that SaaS transformation is carried out to monomer applications further include: obtain each module
The request processing cumulative time in specific time accounts for the ratio of all module total processing times, when the preceding specific quantity of ranking
When the sum of module accounting is more than threshold value two, micro services are converted into after being iterated deconsolidation process to the specific quantity module.
Specifically, request processing load statistics can be added for each module of monomer applications, load statistics method: set
The request of MnT representation module n whithin a period of time handles cumulative time MnT, when MnS is request processing total in a period of time
Between, remember MnR=(MnT/MnS) * 100, take MnR in the top 3 and the sum of accounting be more than 50% these modules carry out split with
Micro services, the threshold value two has chosen 50% in this embodiment, and certain threshold value two can be tested according to practical business and be determined.
Assessment and iteration deconsolidation process are carried out in this manner, monomer applications gradually, reliably can be evolved into micro services.
In further embodiments, after carrying out SaaS transformation to monomer applications, when finding there is part of module in monomer applications
Utilization rate and request rate when being significantly higher than other modules, can by set up the ratio of module request quantity and tenant's quantity come pair
Than the utilization rate of module.For high utilization rate and the higher module of load, it can pull out and carry out independent deployment examples.Specifically,
The number of requests and total tenant's quantity for obtaining each module of monomer applications in certain time, according to each module request quantity and whole
The module that respectively ratio described in deployment examples is greater than threshold value two is pulled out and carrys out independent deployment examples by the ratio of tenant's quantity.
The threshold value two can carry out using determination according to the actual situation.By set up the ratio of module request quantity and tenant's quantity come pair
High utilization rate and the higher module of load can be pulled out and carry out independent deployment examples, to realize than the utilization rate of module
Meet the high scalability of monomer applications, both protected existing software architecture assets value, also provides and develop toward micro services
High value, highly reliable path.
It should be noted that foregoing individual embodiments are described in a progressive manner in this specification, each embodiment weight
Point explanation is the difference from other embodiments, and the same or similar parts in each embodiment may refer to each other.It is right
For monomer applications are carried out with the related embodiment of method of SaaS transformation, as its with partial content disclosed in embodiment with
Data managing method above-mentioned based on monomer applications is similar, so being described relatively simple, related place is referring to data pipe
Manage method part illustration.
Attached drawing 6 is a kind of schematic diagram of server disclosed in embodiment.The server is answered for providing monomer for tenant
With service, the server of the embodiment include memory 32, processor 31 and storage in the memory and can be described
The computer program run on processor, such as the data administrator based on monomer applications.The processor executes the meter
The step in above-mentioned each data managing method embodiment based on monomer applications is realized when calculation machine program.
Illustratively, the computer program can be divided into one or more module/units, one or more
A module/unit is stored in the memory, and is executed by the processor, to complete the present invention.It is one or more
A module/unit can be the series of computation machine program instruction section that can complete specific function, and the instruction segment is for describing institute
State implementation procedure of the computer program in the server.
The server may include, but be not limited only to processor, memory.It will be understood by those skilled in the art that described
Schematic diagram is only the example of server, does not constitute the restriction to server apparatus, may include more more or less than illustrating
Component, perhaps combine certain components or different components, such as the server apparatus can also be set including input and output
Standby, network access equipment, bus etc..
Alleged processor can be central processing unit (Central Processing Unit, CPU), can also be it
His general processor, digital signal processor (Digital Signal Processor, DSP), specific integrated circuit
(Application Specific Integrated Circuit, ASIC), ready-made programmable gate array (Field-
Programmable Gate Array, FPGA) either other programmable logic device, discrete gate or transistor logic,
Discrete hardware components etc..General processor can be microprocessor or the processor is also possible to any conventional processor
Deng the processor is the control centre of the server apparatus, utilizes various interfaces and the entire server apparatus of connection
Various pieces.
The memory can be used for storing the computer program and/or module, and the processor is by operation or executes
Computer program in the memory and/or module are stored, and calls the data being stored in memory, described in realization
The various functions of server apparatus.The memory can mainly include storing program area and storage data area, wherein storage program
Area can application program needed for storage program area, at least one function etc. in addition, memory may include high random access
Memory can also include nonvolatile memory, such as hard disk, memory, plug-in type hard disk, intelligent memory card (Smart
Media Card, SMC), secure digital (Secure Digital, SD) card, flash card (Flash Card), at least one disk
Memory device, flush memory device or other volatile solid-state parts.
If the data managing method based on monomer applications is realized in the form of SFU software functional unit and as independence
Product when selling or using, can store in a computer readable storage medium.Based on this understanding, of the invention
It realizes all or part of the process in above-described embodiment method, can also instruct relevant hardware come complete by computer program
At the computer program can be stored in a computer readable storage medium, which is being executed by processor
When, it can be achieved that the step of above-mentioned each embodiment of the method.Wherein, the computer program includes computer program code, described
Computer program code can be source code form, object identification code form, executable file or certain intermediate forms etc..The meter
Calculation machine readable medium may include: can carry the computer program code any entity or device, recording medium, USB flash disk,
Mobile hard disk, magnetic disk, CD, computer storage, read-only memory (ROM, Read-Only Memory), random access memory
Device (RAM, Random Access Memory), electric carrier signal, telecommunication signal and software distribution medium etc..It needs to illustrate
It is that the content that the computer-readable medium includes can be fitted according to the requirement made laws in jurisdiction with patent practice
When increase and decrease, such as in certain jurisdictions, according to legislation and patent practice, computer-readable medium does not include electric carrier wave letter
Number and telecommunication signal.
Finally, it should be noted that the above embodiments are merely illustrative of the technical solutions of the present invention, rather than its limitations；Although
Present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that: it still may be used
To modify the technical solutions described in the foregoing embodiments or equivalent replacement of some of the technical features；
And these are modified or replaceed, the range for technical solution of various embodiments of the present invention that it does not separate the essence of the corresponding technical solution.
In short, the foregoing is merely presently preferred embodiments of the present invention, it is all according to equalization made by scope of the present invention patent
Variation and modification, shall all be covered by the patent of the invention.
Claims (10)
1. a kind of data managing method based on monomer applications, it is characterised in that:
The logging request that tenant's equipment is sent is received, includes tenant's identity information in the logging request；
The corresponding tenant of tenant's identity information is inquired in tenant's information database rents module release list, the tenant
Renting module release list includes but is not limited to rented monomer applications module id and module release information；
Module release list, which is rented, according to the tenant loads respective modules version set；
Object instance is chosen from deployment examples according to default deployment rule, the module release set rented is passed through into increment
Deployment way is deployed to the object instance.
2. data managing method according to claim 1, which is characterized in that the step is according to default deployment rule from
Object instance is chosen in deployment examples, and the module release set rented is deployed to the target reality by incremental deploying mode
Example, further includes:
When the loading index of deployment examples is more than respective instance threshold value, according to the independent portion of module release set rented
Affix one's name to example；
Otherwise it is real selection target in the deployment examples of respective instance threshold value to be less than from loading index according to default deployment rule
Example, is deployed to the object instance by incremental deploying mode for the module release set rented.
3. data managing method according to claim 1 or 2, it is characterised in that:
The most deployment examples of identical molds block number in the module release set that the deployment rule is rented for selection with tenant,
It is chosen when matched deployment examples have multiple and possesses the least deployment examples of number of modules.
4. data managing method according to claim 1 to 3, it is characterised in that: the tenant rents module release column
Table includes but is not limited to tenant's identity information, the application module renting application message, being rented mark and module release information.
5. data managing method according to claim 4, it is characterised in that: answered in the object instance comprising the monomer
With multiple versions of same module.
6. data managing method according to claim 5, which is characterized in that further include:
According to the ratio of each module request quantity and tenant's quantity, by respectively ratio described in deployment examples is greater than the mould of threshold value two
Block, which pulls out, carrys out independent deployment examples.
7. the method that a kind of pair of monomer applications carry out SaaS transformation, it is characterised in that:
According to each version information of monomer applications, to each module adding module version number in monomer applications；
When tenant rents, the rental module release list of tenant is recorded, the user rents module release list and includes but not
It is limited to rented application module mark and module release information；
After being connected to tenant's logging request, corresponding rental module release list is obtained according to tenant's identity information, according to the rent
Respective modules version set is loaded with module release list；
Object instance is chosen from deployment examples according to default deployment rule, the module release set rented is passed through into increment
Deployment way is deployed to the object instance.
8. the method according to claim 7 for carrying out SaaS transformation to monomer applications, it is characterised in that:
It obtains request of each module in specific time and handles the ratio that the cumulative time accounts for all module total processing times, work as ranking
When the sum of preceding specific quantity module accounting is more than threshold value two, turn after being iterated deconsolidation process to the specific quantity module
Turn to micro services.
9. a kind of server, including memory, processor and storage can transport in the memory and on the processor
Capable computer program, it is characterised in that: the processor is realized when executing the computer program as claim 1-6 is any
The step of the method.
10. a kind of computer readable storage medium, the computer-readable recording medium storage has computer program, and feature exists
In: the step of the method as any such as claim 1-6 is realized when the computer program is executed by processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811227103.6A CN109408067B (en) | 2018-10-22 | 2018-10-22 | Data management method and server based on single application |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811227103.6A CN109408067B (en) | 2018-10-22 | 2018-10-22 | Data management method and server based on single application |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109408067A true CN109408067A (en) | 2019-03-01 |
| CN109408067B CN109408067B (en) | 2021-10-22 |
Family
ID=65468723
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811227103.6A Active CN109408067B (en) | 2018-10-22 | 2018-10-22 | Data management method and server based on single application |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109408067B (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111143033A (en) * | 2019-12-20 | 2020-05-12 | 青岛海尔科技有限公司 | Operation execution method and device based on scalable operating system |
| CN111158749A (en) * | 2019-12-23 | 2020-05-15 | 杭州安恒信息技术股份有限公司 | Software version replacing method, device, equipment and readable storage medium |
| CN111158752A (en) * | 2019-12-30 | 2020-05-15 | 南京天溯自动化控制系统有限公司 | SAAS multi-version control system and use method thereof |
| CN111641675A (en) * | 2020-04-28 | 2020-09-08 | 深圳壹账通智能科技有限公司 | Multi-tenant access service implementation method, device, equipment and storage medium |
| CN112579099A (en) * | 2019-09-30 | 2021-03-30 | 北京国双科技有限公司 | Code deployment method and device, storage medium and electronic equipment |
| CN116932091A (en) * | 2023-09-15 | 2023-10-24 | 畅捷通信息技术股份有限公司 | Configuration file generation method and device during credential generation and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100293537A1 (en) * | 2009-05-13 | 2010-11-18 | International Business Machines Corporation | System and Method for Enabling Parallel Websphere Runtime Versions |
| CN103853535A (en) * | 2012-11-30 | 2014-06-11 | 国际商业机器公司 | Method and device for modifying middleware |
| US20150261518A1 (en) * | 2014-03-17 | 2015-09-17 | Successfactors, Inc. | Recommending Updates to an Instance in a SaaS Model |
| CN107038036A (en) * | 2017-05-02 | 2017-08-11 | 山东浪潮通软信息科技有限公司 | A kind of implementation method of SaaS delivery of services platform |
| CN108279923A (en) * | 2018-01-04 | 2018-07-13 | 辽宁畅通数据通信有限公司 | Program tenant management method and system can be read and deposit medium |
-
2018
- 2018-10-22 CN CN201811227103.6A patent/CN109408067B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100293537A1 (en) * | 2009-05-13 | 2010-11-18 | International Business Machines Corporation | System and Method for Enabling Parallel Websphere Runtime Versions |
| CN103853535A (en) * | 2012-11-30 | 2014-06-11 | 国际商业机器公司 | Method and device for modifying middleware |
| US20150261518A1 (en) * | 2014-03-17 | 2015-09-17 | Successfactors, Inc. | Recommending Updates to an Instance in a SaaS Model |
| CN107038036A (en) * | 2017-05-02 | 2017-08-11 | 山东浪潮通软信息科技有限公司 | A kind of implementation method of SaaS delivery of services platform |
| CN108279923A (en) * | 2018-01-04 | 2018-07-13 | 辽宁畅通数据通信有限公司 | Program tenant management method and system can be read and deposit medium |
Non-Patent Citations (2)
| Title |
|---|
| CONTINUOUS EVOLUTION OF MULTI-TENANT SAAS APPLICATIONS: A CUSTOM: "Continuous Evolution of Multi-tenant SaaS Applications: A Customizable Dynamic Adaptation Approach", 《2015 IEEE/ACM 7TH INTERNATIONAL WORKSHOP ON PRINCIPLES OF ENGINEERING SERVICE-ORIENTED AND CLOUD SYSTEMS》 * |
| 顾平莉: "SaaS应用中多租户若干关键技术研究", 《中国博士学位论文全文数据库 信息科技辑》 * |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112579099A (en) * | 2019-09-30 | 2021-03-30 | 北京国双科技有限公司 | Code deployment method and device, storage medium and electronic equipment |
| CN111143033A (en) * | 2019-12-20 | 2020-05-12 | 青岛海尔科技有限公司 | Operation execution method and device based on scalable operating system |
| CN111143033B (en) * | 2019-12-20 | 2024-03-22 | 青岛海尔科技有限公司 | Operation execution method and device based on scalable operation system |
| CN111158749A (en) * | 2019-12-23 | 2020-05-15 | 杭州安恒信息技术股份有限公司 | Software version replacing method, device, equipment and readable storage medium |
| CN111158749B (en) * | 2019-12-23 | 2023-12-01 | 杭州安恒信息技术股份有限公司 | Software version replacement method, device, equipment and readable storage medium |
| CN111158752A (en) * | 2019-12-30 | 2020-05-15 | 南京天溯自动化控制系统有限公司 | SAAS multi-version control system and use method thereof |
| CN111641675A (en) * | 2020-04-28 | 2020-09-08 | 深圳壹账通智能科技有限公司 | Multi-tenant access service implementation method, device, equipment and storage medium |
| WO2021218328A1 (en) * | 2020-04-28 | 2021-11-04 | 深圳壹账通智能科技有限公司 | Multi-tenant access service implementation method, apparatus and device, and storage medium |
| CN116932091A (en) * | 2023-09-15 | 2023-10-24 | 畅捷通信息技术股份有限公司 | Configuration file generation method and device during credential generation and storage medium |
| CN116932091B (en) * | 2023-09-15 | 2023-12-26 | 畅捷通信息技术股份有限公司 | Configuration file generation method and device during credential generation and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109408067B (en) | 2021-10-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109408067A (en) | A kind of data managing method and server based on monomer applications | |
| US7848970B2 (en) | System and method for synchronizing ledger accounts by company group | |
| CN105069686A (en) | Case automatic detection method and system | |
| CN112685391B (en) | Service data migration method and device, computer equipment and storage medium | |
| CN102760096A (en) | Test data generation method, unit testing method and unit testing system | |
| CN101727648A (en) | Overtime control method in service system and service system | |
| CN108632047A (en) | A kind of determination method and device of tariff data | |
| CN110737425A (en) | billing platform system application program establishing method and device | |
| CN109359938A (en) | A kind of optimization method of flow chart of data processing, device and terminal device | |
| CN112258306B (en) | Account information checking method, device, electronic equipment and storage medium | |
| CN112015826B (en) | Intelligent contract security detection method based on block chain and related equipment | |
| CN111429125B (en) | Account management method and device, storage medium and electronic equipment | |
| CN109828904A (en) | System Authentication method, device, electronic equipment and storage medium | |
| US8538993B2 (en) | Outsourced options management | |
| CN101765078A (en) | Method, device and system for telecommunication service settlement | |
| WO2022178421A1 (en) | Method and apparatus for decentralized management of trusted data on trustless networks | |
| CN114756224A (en) | Activity execution method and device | |
| CN114663177A (en) | State change control method, device, electronic equipment and storage medium | |
| CN110457332B (en) | Information processing method and related equipment | |
| CN106201606A (en) | software distribution method and system | |
| CN109636324B (en) | Electronic service contract processing method and device | |
| CN114970477A (en) | Report generation method, device, equipment and storage medium | |
| US20220138339A1 (en) | Computer system and data access control method | |
| CN114880387A (en) | Data integration script generation method and device, storage medium and electronic equipment | |
| CN118139007A (en) | Method and device for determining settlement result, storage medium and electronic equipment |
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 | ||
| CB02 | Change of applicant information |
Address after: 310056 room 1701, 17th floor, building 3, No. 316, Jianghong South Road, Changhe street, Binjiang District, Hangzhou, Zhejiang Applicant after: Mingdu Zhiyun (Zhejiang) Technology Co.,Ltd. Address before: 310000 1, 3 building, No. 316 Jianghong Road, Changhe street, Binjiang District, Hangzhou, Zhejiang. Applicant before: ZHEJIANG MINGDU INTELLIGENT CONTROL TECHNOLOGY Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |