It's not so much that Elastic is saying it as a lot of people doing the supposed wrong the advert-article describes.
I've seen some examples of people using ES as a database, which I'd advise against for pretty much the reasons TFA brings up, unless I can get by on just a YAGNI reasoning.
It will also depend a lot on the type of data: Logs are an easy yes. Something that required multi-document transactions (unless you're able to structure it differently) is a harder tradeoff. Though loss of ACKed documents shouldn't really be a thing any more.
Even most toy databases "built in a weekend" can be very stable for years if:
- No edge-case is thrown at them
- No part of the system is stressed ( software modules, OS,firmware, hardware )
- No plug is pulled
Crank the requests to 11 or import a billion rows of data with another billion relations and watch what happens. The main problem isn't the system refusing to serve a request or throwing "No soup for you!" errors, it's data corruption and/or wrong responses.
To be fair, I think it is chronically underprovisioned clusters that get overwhelmed by log forwarding. I wasn't on the team that managed the ELK stack a decade ago, but I remember our SOC having two people whose full time job was curating the infrastructure to keep it afloat.
Now I work for a company whose log storage product has ES inside, and it seems to shit the bed more often than it should - again, could be bugs, could be running "clusters" of 1 or 2 instead of 3.
We have an ongoing war in Europe because one President tried to remove the President of another country. You can perform all sorts of mental gymnastics to justify military actions, and depending on who you ask you will always get the answers you want.
I'm not arguing the point you're making. I'm saying that these discussions on these sorts of things on chat boards populated by privileged western nerds and conspicuous progressives have little merit and are merely a reflection of biases/ego of the privileged western nerd when put up against the lived experiences of people in Venezuela and neighboring states.
You're not really saying anything, in fact, just bashing everyone else's opinion.
And note that we can look at history and see that, sometimes, people's honest opinions about their own country and what is best for it happen to be wrong. Libyans were extremely happy when Gaddafi was killed - and now they're living in much worse conditions than when he was alive. Many Afghans welcomed the US toppling of the brutal taliban regime, and now after twenty years of brutal war, the taliban are back in power as if nothing happened.
It would be absolutely wonderful if the same fate doesn't happen to Venezuela. I sincerely wish and hope that they will have a provisional government which quickly organizes free and fair elections and that a much better leader is elected who can start reversing the damage Maduro did. I don't think this is particularly likely to happen, sadly, looking at the history and track-record of violent regime change by foreign powers. This observation remains true regardless of what the people of Venezuela think and hope, sadly.
That is not a reason why there is a war. The Ukrainian war is an existential one, a continuation of multiple acts of genocide performed by russians for centuries.
That is a big difference between war in Ukraine and war in Iraq or Venezuela.
Russia has unlimited objectives: destroy Ukrainian identity and sovereignty. Annex the country.
While USA has limited objectives, like to overthrow the government.
Russia would be very happy to install a puppet regime in Ukraine, as long as they had some certainty this regime would be stable and subservient to their interests. We know for a fact that they don't care about necessarily invading other countries as long as those countries are subservient: they are not planning to annex Belarus, nor did they have any real problems with Ukraine as long as it was led by their preferred leaders and it was not making any overtures to NATO or the EU.
The exact same thing will happen in Venezuela: the USA will be happy with any leader that they have confidence will represent US interests, stop doing any business with Russia or Iran, and that they think will last. If instead another member of Maduro's party looks likely to win power, either now or in the near future, they will certainly not allow that to happen, even if it were to happen as a result of free elections.
Yes, they did, and there was no attempt to annex Ukraine before that regime fell, I said as much in my comment.
Note that this is not in any way an attempt to justify Russia's actions, quite the contrary. I'm using the comparison to Russia's obviously horrible actions in Ukraine to condemn the USA's equally horrible actions in Venezuela.
In the 90s, the status of Crimea was an internal dispute in the newly-formed Ukrainian state. The status of Crimea as a part of the new Ukrainian state at this time was not yet settled in any way. The territory only became firmly a part of Ukraine in 1995.
The 2003 dispute over the island of Tuzla - whose status had not been clearly settled during the independence of Ukraine from the USSR - was settled diplomatically. If you call this occasion an "attempt to annex Ukraine", then we could equally say that "Romania attempted to annex Ukraine" when the countries had several rounds of negotiation and arbitration for control of Snake Island in the Black Sea.
The only reason Russia has been reluctant to formally annex territories it broke away from other countries until 2022 was minimizing economic damage to itself. They knew how sensitive the western countries were to forceful changes of the world map, and felt no need to inflict economic sanctions on themselves for a mere symbolic act of annexing a territory they already fully controlled.
Once that Rubicon was crossed (sanctions were in place and there was nothing to lose), they annexed the four regions of Ukraine that they partially controlled.
>> Russia stood by while everything Russian, including the Russian language which is the native language of millions of Ukrainians, was facing many restrictions
You think Ukrainians shouldn't decide which language to use? Also russian is native for millions of Ukrainians due to ethnic cleansing done by russians for centuries.
Well behaved governments will provide national minorities with everything they need to feel at home. Bilingual street signs, schools in minority's native language, churches, radio and TV broadcasts in minority's native language etc.
Any government who denies this to their national minorities should be promptly replaced as this kind of disrespect to other peoples' culture, religion and national identity inevitably leads to bad outcomes.
The speed is nice, but I switched because uv supports "pip compile" from pip-tools, and it is better at resolving dependencies. Also pip-tools uses (used?) internal pip methods and breaks frequently because of that, uv doesn't.
Luckily commonly used forges for collaboration have the ability to make tags immutable. Any repository where multiple people collaborate on a project should have that feature enabled by default. I'm still waiting for the day where tags are immutable by default with no option exposed to change it.
I'm sure that would cause problems for some, but transitive labels already exist in Git: branches.
I dont find the idea of a immutable "descriptive" tag or branch to be that useful (I also dont find the differentiation of tags and branches to be useful either) I've seen plenty of repositories where tags end up being pretty ambiguous compared to each other or where "release-20xx" does not actually point to the official 20xx release. Immutable references are more typically handled by builders and lockfiles to which Git already has a superior immutable reference system, the commit hash.
I 100% agree on the latter (the tag != release is more of a project management issue), and the same concept applies to containers and their digest hashes. The main issue at the end of the day is the human one: most people don't like looking at hashes, nor do they provide context of progression. I would say "give both" and make sure they match on the end user side of things, but tags are the most common way (open source) software releases are denoted.
The purpose of the forge is to be able to prevent this. Protected tags are usually a feature which provides a way to mark tags as untouchable, so removal would require a minimum level of trust to the repository on the platform. Otherwise, attempts to push tag deletions or changes for tags matching the protected pattern would be rejected/ignored.
Of course, the repository owner has unlimited privilege here, hence the last part of my prior comment.
Tags are just a text file with a name and the sha of the tag object (with the commit and some metadata/signatures as contents), last I checked. It's deliberately simple and thus almost impossible to actually lock it down in concrete terms.
Packed refs are a little more complicated but all of the storage formats in git are trivial to manually edit or write a tool to handle, in extremis.
That's the purpose of the forge platform, to provide a way to prevent changes to these files from being accept into the source repository. For example:
That's true for local hooks, but neither a dishonest person nor an LLM can bypass a pre-receive hook on the server (as long as they don't have admin access).
reply