“Event replay: if we want to adjust a past event, for example because it was incorrect, we can just do that and rebuild the app state.”
Yes, they are. They are as free as adding a new endpoint.
> and for things that were not decided to be an API and or a contract an absolute waste of time.
You're talking about integrating multiple projects. There are always contract. You simply chose to be ignorant of that fact and fail to interpret breaking those contracts as the root cause of all your problems.
You point out anyone lauding monorepos as some kind of solution to any problem and I assure you that we can immediately isolate one or more problems caused by versioning and breaking contracts.
The only reason why we see this nonsense paraded in web services is that they are loosely coupled. When people worked mainly with modules and libraries, compiler and linking errors made this sort of error very obvious. Now people chose to unlearn facts and want to call that operational improvements.
- GitOps is a fancy word recently created by Gitlab or Github to sound cooler
- It means storing your code / services in git and deploying on push
It all seems so weird. We had tools like puppet since ice ages which can, after you push to git, reconfigure and deploy whatever you described in your git. Over all your fleet of machines.Am I missing something?
Does it write synchronously on COMMIT and never lose data? Is it reliable enough to use instead of SQLite?
(edit to add: This is already pretty great, I love curated collections like this, I just also see a way to make it even better!)
One local first that I recently switched to is migrating from ynab.com to my own Libre Calc spreadsheets. It took a few days to figure out all the formulas, but now I have even more control over how I track my budget.
Add-on: https://addons.mozilla.org/en-US/firefox/addon/profile-switc...
Source: https://github.com/null-dev/firefox-profile-switcher