That is 20% of the effort can deliver 80% of the features?
929 karma · joined September 20, 2012
That is 20% of the effort can deliver 80% of the features?
Innovation is NIH somewhat, somehow and that is a Good Thing.
Searching doesn't with keeping a copy of the thing you need around.
0) The most obvious use case is to replace git, because git proper doesn't handle big files very well, let alone bigger than RAM structured data. Mind the fact you might still need an ad-hoc solution for binary data. WT does have a limitation on value size.
1) There is various data science uses cases, like sharing data [0] or A/B testing stuff.
2) Anywhere you need an audit trail .ie you need to look back at previous states, whether it is for debugging purpose or domain logic
versioned datastore is a compromise between event sourcing (pure log) and non-versioned databases.
[0] Collaborative Open Data versioning: A Pragmatic Approach Using Linked Data
[1] https://en.wikipedia.org/wiki/Audit_trail
edit: cosmit.
It seems like you do not rely on range queries at all.
Why are you doing it like that? Does it lead to some limitation of some sort? Like making merge very costly?
In my implementation, the default is to take the records from the "other" branch because you want 'devel' in 'master' not the other way around. Not sure I am clear. LMK.
edit: plural
Myself, I am in the second category. I start but not maintain project.
Here is a list of feature complete repositories:
- https://github.com/amirouche/scheme-todomvc - https://github.com/amirouche/deuspy - http://quicoeur.fr/ - http://sensimark.com
I have other projects like:
- https://framagit.org/a-guile-mind/culturia.next/
- https://framagit.org/a-guile-mind/culturia.one/
- https://github.com/amirouche/zehefyu93
- https://github.com/amirouche/socialite
They are not done because they are more research work on various topics like UI/UX that is more like CLI in the browser this lead to the development of a chatbot like experience in the spirit of ipython. In the database side, I think I will recode culturia.next. Even if I don't know what the future will bring.
Worse, I have two go to stack:
1) Guile + BiwaScheme or simple SXML
2) aiohttp + reactjs like socialite maybe i will move to https://github.com/amirouche/beyondjs/ with https://github.com/amirouche/found
You easier to debug end-to-end tests of a microservice architecture that monolith? That's not my experience. How do you manage to put side by side all the events when they are in dozen of files?
On all the code bases I saw, I never told myself (micro) services are helpful, I will redo that. And if I had to rewrite any of them, I would use a single 'service' that can do everything. IMHO it's more sane to optimize for the developer instead of whatever micro-services try to optimize.
(Sorry HN etiquette)
Mind the fact, that given the database is embedded in the webapp processus, you need some auth machinery to hit the database from the outside world anytime. Which leads to more wheel reinvention like background process scheduling like Celery.
At the end of the day, embedded key-value stores are great because they require _less_ administration and have great performances but the community is fragmented and tooling is not there yet.
I think embedded KV stores have still a chance in niche applications for building expert systems that require persistence but don't change a lot. For a web application which specifications (and schema) change all the time, it's a poor solution.
edit: also, in the context of e.g. wiredtiger having transactions across tables like the full-text search index and plain tables is very great and save quiet a few painful experience of setting up the project.