This is the
evict installment of the Crux tutorial.
You arrive at the comet 'Oumuamua and pull along side, asking for permission to land. A voice comes over the communications system
"" How did you find us? Who sent you?? ""
You land on the space port and are ushered inside. The ships captain, Ilex, greets you.
"" Hello, it’s good to have you with us.
We are set to leave the solar system right away and as part of our service we offer people the right to be forgotten. Some are not worried that their information is kept here, however others want there to be no personal data left behind.
You may not have been told this yet, but this comet is actually a transportation vessel. It will take us to the star system Gilese 667C which is home to intelligent life far superior to our own. We all are hoping to find opportunities beyond our wildest dreams. All records of this transportation vessel and any life outside of the solar system are heavily monitored and wiped in the interest of preserving the normal technological advancement of the Human race. This means we know little of the beings we are going to meet.
Our task for you is to remove the records of the people who have chosen to be forgotten here. ""
You are excited by the prospect and agree to help.
First you read the manual entry for
evict as this will be the perfect tool.
There are only four transaction operations in Crux:
Writes a version of a document
Deletes a version of a document
Stops a transaction if the precondition is not met.
Removes a document entirely
Crux supports eviction of active and historical data to assist with technical compliance for information privacy regulations.
The main transaction log contains only hashes and is immutable. All document content is stored in a dedicated document log that can be evicted by compaction.
- A complete
evicttransaction has the form:
You are given the data for the people on the ship and sync up your Crux node. You decide that you are going to embark on this adventure along with them so you add your name to the list.
Before you start the eviction process you make a query function so you can see the full results of anything stored in Crux:
You show the others the result:
The Crux manual said that the
evict operation will remove a document entirely.
Ilex tells you the only person who whishes to exercise their right to be forgotten is Kaarlang.
You use your function and see that the transaction was a success.
All the data associated with the specified
:crux.db/id has been removed from the Crux along with the eid itself.
The transaction history is immutable.
This means the transactions will never be removed.
You assure Ilex that the documents are completely removed from Crux, you can show this by looking at the
history-descending information for each person.
You show the results to Kaarlang who is happy that there his details are no longer a part of the ships logs.
The ship starts to shake as the engines are fired up.
Ilex thanks you and takes you to the Cryogenics department. You must be put into stasis as the journey will take around 25 years, even at the near light speeds of the ship.
You are astonished with the amount that you have done in one short week. How did little old you end up with an opportunity as big as this?
Your eyes get heavy as the cryogenicist initiates the hibernation process. As they do, you wonder if you’ll ever come back to the solar system.
I hope you enjoyed learning about the basics of Crux. Although this is the final installment for the main tutorial series it is not the end of the Crux tutorial. Watch this space for more tutorial releases of the tutorial where you will be sent on assignments to solve more specific and complex tasks using Crux.
I’d love to hear any ideas for enhancements so don’t hesitate to get in touch.