Today we continue discussing the best practice from storage engineering :
517) Customers also prefer ability to switch products and stacks. They are willing to try out new solutions but have become increasingly wary of tying to any one product or the increasing encumbrances
518) Customers have a genuine problem with data being sticky. They cannot keep up with data transfers
519) Customers want the expedient solution first but they are not willing to pay for re- architectures
520) Customers need to evaluate the cost of even data transfer over the network. Their priority and severity is most important to them.
521) Customers have concerns with the $/resource whether it is network, compute or storage. They have to secure ownership of data and yet have it spread out between geographical regions. This means they have trade-offs from the business perspectives rather than the technical perspectives
522) Sometimes the trade-offs are not even from the business but more so from the compliance and regulatory considerations around housing and securing data. Public cloud is great to harness traffic to the data stores but there are considerations when data has to be on-premise.
523) Customers have a genuine problem with anticipating growth and planning for capacity. The success of an implementation done right enables future prospect but implementations don’t always follow the design and it is also hard to get the design right.
524) Similarly, customers cannot predict what technology will hold up and what won’t in the near and long term. They are more concerned about the investments they make and the choices they have to face.
525) Traffic, usage and patterns are good indicators for prediction once the implementations is ready to scale.
517) Customers also prefer ability to switch products and stacks. They are willing to try out new solutions but have become increasingly wary of tying to any one product or the increasing encumbrances
518) Customers have a genuine problem with data being sticky. They cannot keep up with data transfers
519) Customers want the expedient solution first but they are not willing to pay for re- architectures
520) Customers need to evaluate the cost of even data transfer over the network. Their priority and severity is most important to them.
521) Customers have concerns with the $/resource whether it is network, compute or storage. They have to secure ownership of data and yet have it spread out between geographical regions. This means they have trade-offs from the business perspectives rather than the technical perspectives
522) Sometimes the trade-offs are not even from the business but more so from the compliance and regulatory considerations around housing and securing data. Public cloud is great to harness traffic to the data stores but there are considerations when data has to be on-premise.
523) Customers have a genuine problem with anticipating growth and planning for capacity. The success of an implementation done right enables future prospect but implementations don’t always follow the design and it is also hard to get the design right.
524) Similarly, customers cannot predict what technology will hold up and what won’t in the near and long term. They are more concerned about the investments they make and the choices they have to face.
525) Traffic, usage and patterns are good indicators for prediction once the implementations is ready to scale.
No comments:
Post a Comment