You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
Go to file
Caj Larsson 8cc8e6a464
ci/woodpecker/push/woodpecker Pipeline was successful Details
Woodpecker CI badge
2 years ago
dataswamp Formatting with gofmt 3 years ago
doc Added logo 3 years ago
infrastructure Formatting with gofmt 3 years ago
server Renaming SwampfileService -> DataSwampService 3 years ago
util Testing the events on namespace Service 3 years ago
.dockerignore Fix the dockerfile 3 years ago
.gitignore Fix the dockerfile 3 years ago
.woodpecker.yml Woodpecker CI 2 years ago
Dockerfile Progress on the great event refactoring 3 years ago
Readme.md Woodpecker CI badge 2 years ago
default.toml Separate admin port 3 years ago
go.mod Complete restructure of domain and infra layer 3 years ago
go.sum Complete restructure of domain and infra layer 3 years ago
main.go logger, implements #9 3 years ago
sqlc.yaml Use sqlc to generate typesafe repository tools 3 years ago

Readme.md

status-badge

Bog: The Dataswamp

Logo

Is the warehouse too strict? Maybe you don't know the schema yet. And you know your lake is already full with a bunch of stuff that should have been deleted long ago?

Maybe it's time for the dataswamp, just POST your data in and fetch it later, maybe. Either way it will be deleted eventually.

Don't worry about access credentials, the datasawmp does authorization without authentication the old school way: encryption. Pass a password when you create your data and if you pass the same when you retrieve it, you get the same bits back.