Organizational setup for cloud

From: Noveljic Nenad <nenad.noveljic_at_vontobel.com>
Date: Wed, 15 May 2019 08:06:57 +0000
Message-ID: <115468_1557907621_5CDBC8A5_115468_6326_1_ef43493f6b374bd1b38ffe08bd0ca32d_at_vontobel.com>



I'd be grateful if you could share how your organization adapted to cloud services. In particular, I'd like to learn what functions - if any - you've implemented centrally.

These are some of the topics I'd like to address with this question:

- First of all, is there still some minimal central DBA team around? If yes, I assume that they do consulting and performance tuning, but do they have any operational responsibilities as well?
- Do the application teams create and configure cloud services by themselves, or perhaps there's some central team who does that?
- Have you defined some internal limitations and standards on using cloud services? If yes, how do you enforce them?
- How about handling generic outages and problems with a cloud service?
- Who's monitoring and alerting that the costs are within the budget - some central entity or every application team for themselves.

Thanks in advance,

Nenad

https://nenadnoveljic.com/blog/



Please consider the environment before printing this e-mail. Bitte denken Sie an die Umwelt, bevor Sie dieses E-Mail drucken.

<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css">p { font-family: Arial;font-size:9pt }</style>
</head>
<body>
<p>
<br>Important Notice</br>
<br />

This message is intended only for the individual named. It may contain confidential or privileged information. If you are not the named addressee you should in particular not disseminate, distribute, modify or copy this e-mail. Please notify the sender immediately by e-mail, if you have received this message by mistake and delete it from your system.<br /> Without prejudice to any contractual agreements between you and us which shall prevail in any case, we take it as your authorization to correspond with you by e-mail if you send us messages by e-mail. However, we reserve the right not to execute orders and instructions transmitted by e-mail at any time and without further explanation.<br /> E-mail transmission may not be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete. Also processing of incoming e-mails cannot be guaranteed. All liability of Vontobel Holding Ltd. and any of its affiliates (hereinafter collectively referred to as "Vontobel Group") for any damages resulting from e-mail use is excluded. You are advised that urgent and time sensitive messages should not be sent by e-mail and if verification is required please request a printed version.</br> Please note that all e-mail communications to and from the Vontobel Group are subject to electronic storage and review by Vontobel Group. Unless stated to the contrary and without prejudice to any contractual agreements between you and Vontobel Group which shall prevail in any case, e-mail-communication is for informational purposes only and is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction.<br /> The legal basis for the processing of your personal data is the legitimate interest to develop a commercial relationship with you, as well as your consent to forward you commercial communications. You can exercise, at any time and under the terms established under current regulation, your rights. If you prefer not to receive any further communications, please contact your client relationship manager if you are a client of Vontobel Group or notify the sender. Please note for an exact reference to the affected group entity the corporate e-mail signature. For further information about data privacy at Vontobel Group please consult <a href="https://www.vontobel.com">www.vontobel.com</a>.<br />
</p>
</body>
</html>

--
http://www.freelists.org/webpage/oracle-l
Received on Wed May 15 2019 - 10:06:57 CEST

Original text of this message