Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

WDS Student Guide - Observations #24

Open
venuvedam opened this issue Nov 9, 2018 · 3 comments
Open

WDS Student Guide - Observations #24

venuvedam opened this issue Nov 9, 2018 · 3 comments
Labels
enhancement New feature or request

Comments

@venuvedam
Copy link

MCW-Azure-Blockchain/Whiteboard design session/WDS student guide - Azure Blockchain.md

Abstract and Learning Objectives section - The text in this section needs an overhaul - Same comment as the Readme.MD comment that I raised. Those observations are applicable here too as the text is the same.

@venuvedam
Copy link
Author

Also, there should be some time spent on validating that this is a proper use case for blockchain. The teams should spend five to ten minutes performing the "Validation test" by applying the four basic principles of blockchain use cases ie does the asset cross organizational trust boundaries? do multiple organizations need to access and update data on the ledger independently? Are there multiple, mundane verification steps that can be automated? Is there a requirement for granular audit etc.

While this use case in particular is a textbook blockchain use case, I believe the students need to still undertake this thought experiment so that they can do it for the other supposedly "blockchain" use cases that come their way.

@crpietschmann
Copy link
Collaborator

This change would need to be assessed as a bigger change to the MCW.

@venuvedam
Copy link
Author

This is specific to blockchain because of the nature of this workload. I don't think it applies to the other workloads on Azure. Do you think we should treat this suggestion at MCW level?

@DawnmarieDesJardins DawnmarieDesJardins added the enhancement New feature or request label Jan 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants