Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
C
cmsc818fall2023projects
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Peter Keleher
cmsc818fall2023projects
Commits
bd265364
Commit
bd265364
authored
1 year ago
by
Peter J. Keleher
Browse files
Options
Downloads
Patches
Plain Diff
auto
parent
f765b416
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
p6.md
+15
-13
15 additions, 13 deletions
p6.md
with
15 additions
and
13 deletions
p6.md
+
15
−
13
View file @
bd265364
# Project 6: Supporting High-level Abstractions From a Shared Log
**v1.
0
**
<br>
**v1.
1
**
<br>
**Due Dec 10**
## Setup
...
...
@@ -25,9 +25,7 @@ KV. Like w/ Tango, we expect transactions to support strict
serializability. Writes from transactions that abort do not affect the
KV.
Finally, in the
*tree*
type, you will create a shared tree that
supports concurrent modifications via simple mutations. You build this
entirely from scratch.
Finally, you will build something else. See below.
You will build your tango support in a new
`p6/tango`
module. Your
applications will call the tango module API to access the shared log.
...
...
@@ -162,6 +160,16 @@ non-transactional updates, but *calls for transactional updates are
delayed until a transaction is known to have committed
*
.
## Something Else
Build some other distributed data type on tango. Or do something else cool w/ Raft.
## Points.
-
[
**40 pts**
] intCRED
-
[
**60 pts**
] transactional KV
-
[
**50%**
] of final exam grade: "Something Else". The other 50% will be a take-home exam.
Everything, the "Something Else", should be well-documented in your README.
## Testing.
1.
I will test by running two copies of
`intCRDT.go`
against "scriptInt.1"
concurrently, multiple times. Each time the end result should be the
...
...
@@ -170,16 +178,10 @@ same regardless of interleaving.
"scriptKV.1" with one app. As the third READ is seen, I will start
another instance of
`kv.go`
running "scriptKV.2", which should
cause transaction 2 to abort. Transactions 1 and 3 will commit.
3.
You should come up scripts, similar to the KV scripts, to test your
log-based tree implementation. Details should be in your README.md file.
3.
Your something else should come w/ scripts, similar to the KV scripts, for testing. Details should be in your README.md file.
## Random Details
-
The tree should support mutations such as:
-
add a child
-
move a child
-
delete a child
Transactional semantics allow these to be combined atomically.
## Submitting
Submit by pushing to your repository.
-
DO update the
`README.md`
to
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment