CS Infostructure Library
Understand the question before choosing the answer.
Clear explanations of cloud infrastructure questions, choices and consequences. Written to be useful whether or not you ever need our help.
In-depth
Understand the components and consequences.
Cloud fundamentals
Is the cloud just another kind of hosting?
How cloud services differ from dedicated servers, virtual servers and colocation—and when the traditional answer may still fit.
Read the article →Cloud fundamentals
What does the cloud actually do?
What changes when infrastructure becomes a service—and what still remains for your organization to decide, design and operate.
Read the article →Architecture and complexity
When good architecture becomes too much architecture
How to meet present needs without carrying the cost and complexity of every imaginable future.
Read the article →Definition and perspective
What is infostructure?
How infrastructure, applications, data, connections and operational choices form one working whole.
Read the article →Resilience and recovery
The cloud can fail. What happens to your service and data?
What the provider protects, what remains your responsibility, and why redundancy, backup and recovery solve different problems.
Read the article →Patching and responsibility
Who patches what in the cloud?
Where the provider’s responsibility ends, what remains yours, and how managed services move that boundary.
Read the article →Security and recovery
Recovery is not the same as rebuilding
How to rebuild from controlled sources when the existing infrastructure can no longer be trusted.
Read the article →Perspectives
Start with what you observe.
Shorter explorations of questions that do not always look like infrastructure questions at first.
Performance and geography
Could poor regional conversion have a technical cause?
Why commercial performance and technical performance can sometimes be connected.
Read the perspective →Cost and value
When is a cloud environment actually too expensive?
Cost only makes sense in relation to what the environment needs to achieve.
Read the perspective →Performance
What does “the application is slow” actually tell you?
Performance depends on who experiences it, from where, and what they are trying to do.
Read the perspective →