The Reason
Impressive to observer today how can be simple and efficient a deployment. Previous technologies cycle we abstract some resources other became commodities and we can see some movements very consistent became more and more ready and improve to became more enterprise grade.
Remember what occur with the explosion of virtualization that brings important drivers like simplification and speed today we move some steps forward and is even simpler and faster. Architect for cloud relay on compose with existing services, the choice in this composition will drive:
- Avoidance of lock in
- Better usage of the cloud service target to use
- Clear definition of availability scenarios
- Better definition of communication scenario
- Initial definition on security strategy and controls
Focus on service
Using a practical approach and simple application like WordPress, we can consider the following major initial modules:
- Name Domain Server – DNS
- Filter – First the rule for traffic acceptance from internet than protocol specific like reverse proxy
- HTTP – Application to serve the content – WordPress specific (static + dynamic)
- Data – Database repository (metadata and service specific.
Define the criteria
At this point we have an initial understanding of requirements, communication, minimum security services also what can be improved in terms of security, responsiveness that will bring in the end qualities that will make possible a better transition to production.
And what we will define as relevant on selection ?
- Exercise bring the data and how to take data
- Design for failure, ask hat happens when the service dies
- When use different services investigate on how you will be affected by DRs events
- Even when backup destination has durability check what happens on restore cases, what billing tigers are activate, transport, or other cost increases.
- If you don’t require the control make an analyzes if make sense insists normally when you add more flexibility to control all modules also brings responsibilities to manage and maintain.
- Forgot security… Cloud providers has responsibilities this don’t justify an direct reason to abdicate of security and compliance.
- SLAs, don’t use as justification to add readability to your architecture, when design use failure coverage strategies
- An Single Point of failure or broke code will continue stop does not matter if runs faster or with more capacity
- The tool or service can’t be the gist. Focus what you really most to proper spent.