At least this used to be possible in most hosting plans in old days.
421 karma · joined November 11, 2021
At least this used to be possible in most hosting plans in old days.
For an analogy, one can be given money instead of being invited to a social gathering. One might feel offended, while other may feel happier.
Looks like these recommended practices did not include benchmark the queries and DB for the workload. And 99.99% there was no person with performance engineering mindset was involved (or was/ were completely ignored)
I have known a tech lead, one-self a java developer, who could not compile java code to class/ jar file that could be added to a docker layer in a pipeline.
That 1% of the time software is critital, it is messing too many lives... things like royal mail and what not.
Is it aligned with the incentive digital marketing team has?
I think the most troblesome aspect of Slack is the "highlighting" individuals.
Usually the most productive command during a typical work day is ... `killall slack` :)
Options... use gears at touch points to match speed, or have a robust outer layer to eliminate impact of friction, or Try to control speed to match the system
A combination of these options, may work. Challenge is to identfy the required option and apply what works for a given situation, which is another activity needing quite some brain cycles.
Just an observation...
Hope your upcoming life is pleasant.
Anyone planning to test "YMMV", or full blown follow through, is advised to read that dailywtf.
This is the bitter truth, no one wants to acknowledge.
DBAs and Infra, are in the same boat as QAs. Pendulam will swing back in not so long time frame i hope.
Also my comment was probably incomplete in context... as in how perfectly fine piece of advice could have been abbreviated, misunderstood and became a cult.
> "Show me your [code] and conceal your [data structures], and I shall continue to be mystified. Show me your [data structures], and I won't usually need your [code]; it'll be obvious.''
as DDD.
Unfortunately can't find the original article, may be someone will share a link.
Loosing a few pixels or missing some object updates won't be noticable in high fps games, but where correctness and completeness of data is needed, UDP based applications end up implementing TCP features in application layer.
These application layer implementations can be more performant (low latency and/or high throughput) with UDP, utilizing the special cases, than TCP, which needs to provide generic facilities to every application running on the same host. And then it becomes a question of available resources vs benefits.
Example: DNS started as UDP and later used TCP when expectations on correctness grew.
That said, We have high capacity and high quality backbones that UDP looks right choice for many cases, and should be used where it makes sense.