Discussion
The principal argument against designing purely for portability between clouds is that
Answer: C
Correct answer: it forfeits the managed services offered
Designing for portability means restricting oneself to the lowest common denominator across providers - usually plain compute and storage - and forgoing the managed databases, queues and serverless platforms that provide most of the operational saving. The cost is paid continuously in engineering effort against a benefit that may never be realised, so the usual advice is to accept the coupling and abstract only where a move is genuinely foreseeable.
No comment is present. Be the first to comment.
Loading…
Post your comment
Please log in or register to post a comment.
Examination Categories
- SSC Exams
- Banking Exams
- Teaching Exams
- Civil Services Exams
- Railways Exams
- Engineering Recruitment Exams
- Defence Exams
- State Government Exams
- Police Exams
- Insurance Exams
- Nursing Exams
- Other Government Exams
- NRA CET
- PG Entrance Exams
- Campus Placement
- MBA Entrance Exams
- CUET and UG Entrance
- Judiciary Exams
- Regulatory Body Exams
- Software Development