Definition: Hybrid If some applications are run on-premise whereas other applications are run on-demand then we call this operational model “hybrid”. This definition is perfectly aligned with article #15 on the meaning of “hybrid”. This definition should not be mistaken with the one of “mixed” applications where the same applications run partially on-premise and partially on-demand. |
Definition: Dynamics In general, dynamics means alteration from what has been and what will be. The more need or wish for alteration, the more dynamics. In this interpretation dynamics can be seen as a driving force for alteration. The bigger the system landscape of a company is (no matter whether on-premise or on-demand), the more expensive is each single alteration if it is of a general kind. Hence, the desire for change becomes smaller and smaller. So is the dynamics. This conception is surely not valid for all kinds of alterations, but for many of them. |
Criterion | “On-demand” | “On-premise” |
Backend Connectivity | To be compensated by a peer-to-peer communication technology from on-demand to on-premise (see 13) and possibly further infrastructures built on top of this basis | Datacenter Local Area Network and internal local application middleware. |
Control | ||
Costs | Up-front costs for hardware, maintenance, software licensing, datacenter facility, etc. | |
Customization | Limited (see 3) | Possible in wide ranges (see 9) |
Infrastructure: Sizing, Updates, Add-ons | Provided by the cloud offering, priced-in, limited capabilities (see 4) | Rather complex and expensive |
Integration with existing or 3rd party software | ||
Mobile access | Authorizations are taken care of effortlessly (see 7) | Most companies have “build-your-own“ mobile connectivity infrastructure (see 3, 7) |
Network Costs | Very high because of increased investment needs in WAN communication reliability, security and performance investments | Very low costs: Local Area Network |
Reliability | Central back-up systems are available in case a server crashes or power goes out. Duplicate or redundant systems replace in case of serious failures | Usually, there are no back-up or duplicate/redundant servers available except you are dealing with very sensitive data (e.g. banking sector) |
Security | A2A data transfer via internet creating security risks; compensated by high security efforts of the provider (see 14) | A2A data transfer via internal datacenter environment creating lower risks (see 9) |
Support of proprietary software processes | Only standard API’s and scenarios are supported by a SaaS provider. But through the APIs you can build custom extensions and support them on your own. | Easily possible (see 9) |
Time-to-market | Joint development of software, infrastructure and operational processes (see 4, 7, 9) | Separation of software development and infrastructure / operations yielding a TCO disadvantage |
Legend | |
· means to be the better solution for the according criterion | |
· means to be an equivalent or almost equivalent solution in regards to the better one | |
· means to be the disadvantaged solution for the according criterion |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
21 | |
16 | |
13 | |
12 | |
11 | |
10 | |
7 | |
7 | |
7 | |
7 |