Line 23: |
Line 23: |
| </th> | | </th> |
| </tr> | | </tr> |
− | <tr><td colspan="2" class="logo">[[KubernetesIMG.png|200px]]</td></tr> | + | <tr><td colspan="2" class="logo">[200px]</td></tr> |
| <tr> | | <tr> |
| <th>Status</th> | | <th>Status</th> |
Line 30: |
Line 30: |
| <tr> | | <tr> |
| <th>Initial release</th> | | <th>Initial release</th> |
− | <td>May 5, 2019</td> | + | <td>July 12, 2019</td> |
| </tr> | | </tr> |
| <tr> | | <tr> |
Line 38: |
Line 38: |
| <tr> | | <tr> |
| <th>Official publication</th> | | <th>Official publication</th> |
− | <td>[[Media:EN_-_Kubernetes_v0.1_EN.pdf|Kubernetes.pdf]]</td> | + | <td>[[Media:EN_-_Datalakes_v0.1_EN_Published.pdf|Datalakes.pdf]]</td> |
| </tr> | | </tr> |
| <tr><td colspan="2" class="disclaimer"><table><tr> | | <tr><td colspan="2" class="disclaimer"><table><tr> |
Line 166: |
Line 166: |
| <p>Design Data Lakes with the elements necessary to deliver reliable analytical results to a variety of data consumers. The goal is to increase cross-business usage in order to deliver advanced analytical insights. Build Data Lakes for specific business units or analytics applications, rather than try to implement some vague notion of a single enterprise Data Lake. However, alternative architectures, like data hubs, are often better fits for sharing data within an organization.</p> | | <p>Design Data Lakes with the elements necessary to deliver reliable analytical results to a variety of data consumers. The goal is to increase cross-business usage in order to deliver advanced analytical insights. Build Data Lakes for specific business units or analytics applications, rather than try to implement some vague notion of a single enterprise Data Lake. However, alternative architectures, like data hubs, are often better fits for sharing data within an organization.</p> |
| <h2>References</h2> | | <h2>References</h2> |
| + | <ref>Dennis, A. L. (2018, October 15). Data Lakes 101: An Overview. Retrieved from <i>[https://www.dataversity.net/data-lakes-101-overview/#]</i></ref> |
| + | <ref>Marvin, R., Marvin, R., & Marvin, R. (2016, August 22). Data Lakes, Explained. Retrieved from <i>[ https://www.pcmag.com/article/347020/data-lakes-explained]</i></ref> |
| + | <ref>The Data Lake journey. (2014, March 15). Retrieved from <i>[https://hortonworks.com/blog/enterprise-hadoop-journey-data-lake/]</i></ref> |
| + | <ref>Google File System. (2019, July 14). Retrieved from <i>[https://en.wikipedia.org/wiki/Google_File_System]</i></ref> |
| + | <ref>Coates, M. (2016, October 02). Data Lake Use Cases and Planning Considerations. Retrieved from <i>[https://www.sqlchick.com/entries/2016/7/31/data-lake-use-cases-and-planning]</i></ref> |
| + | <ref>Bhalchandra, V. (2018, July 23). Six reasons to think twice about your data lake strategy. Retrieved from <i>[https://dataconomy.com/2018/07/six-reasons-to-think-twice-about-your-data-lake-strategy/]</i></ref> |
| + | <ref>Data Lake Expectations: Why Data Lakes Fail. (2018, September 20). Retrieved from <i>[https://www.arcadiadata.com/blog/the-top-six-reasons-data-lakes-have-failed-to-live-up-to-expectations/]</i></ref> |
| + | <ref>Data Lake: AWS Solutions. (n.d.). Retrieved from <i>[https://aws.amazon.com/solutions/data-lake-solution/]</i></ref> |
| | | |
| </div> | | </div> |