Abstract
The most realistic scenario in large enterprises is a mixture of legacy on-premises applications, cloud IaaS or PaaS applications, and SaaS applications. All these applications are likely to need some level of integration with the rest.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsNotes
- 1.
See http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf , accessed August 1, 2015.
- 2.
Exit routines are routines that are coded by the users of an application and linked into the application. They offer a tricky path to integration that tends to expose the internals of the application and result in an inflexible relationship between the integrated applications. They are more commonly used in customizing the kernels of operating systems such as Linux. Installing a new application on Linux occasionally involves relinking the kernel with new or additional code. Applications that offer exit routines frequently need to be relinked when the application is upgraded. Although they are tricky, they are also flexible and powerful, amounting to a do-it-yourself programming interface. The right exit routines can make adding a web service to a legacy application possible, even relatively easy, but some routines seem impossible to work with.
- 3.
Amazon is the retail site that inspired much cloud development. Amazon’s cloud offerings are solutions developed by Amazon to cope with its own difficulty standing up systems to respond to its growing system loads. For some background on Amazon’s development, see www.zdnet.com/article/how-amazon-exposed-its-guts-the-history-of-awss-ec2/ . Accessed July 28, 2015.
- 4.
Google has reinforced the shielding on some undersea fiber-optic cables to prevent damage from shark bites. See www.theguardian.com/technology/2014/aug/14/google-undersea-fibre-optic-cables-shark-attacks , accessed August 5, 2015.
- 5.
A race condition is an error that occurs because messages arrive in an unpredicted order. Usually, this occurs when messages always come in the same order in the development lab, and the developer assumes this is stable activity. If quality assurance testing does not happen to generate an environment that brings out the race condition, the error may not be caught until the application moves to production. Undetected race conditions can appear when a stable on-premises application is moved to a cloud.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2015 Marvin Waschke and CA
About this chapter
Cite this chapter
Waschke, M. (2015). Fish nor Fowl. In: How Clouds Hold IT Together. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-6167-4_14
Download citation
DOI: https://doi.org/10.1007/978-1-4302-6167-4_14
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4302-6166-7
Online ISBN: 978-1-4302-6167-4
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)