22.9.13

How to not be a supernova in the clouds

In this post I will start a serial of posts about techniques successfully used by me in projects to avoid two mainly things, single component or resource failure and quick request demand increase. I called that a Supernova because the effects are similar (thanks for the brilliant concept Luis Botelho). The idea is to give some ideas in two phases of Exalogic setup, when designing you solution and when using in run time. 

In each phase my idea is to cover some topics that are:
  • Capacity planning
  • Scaling
  • Resiliency planning
  • Managing
  • Throttling
And some components related do Exalogic:
  • Servers
  • Networks
  • Storage volumes 
This is a very simple approach to construct a robust solution using Exalogic, not tight related with what is being installed inside Exalogic (middleware software), but how to define the infrastructure to reach the defined aims. 

No comments:

Post a Comment