Building software
sari and
Building software
Laurence Tratt: What Factors Explain the Nature of Software?
tratt.netdegree of iteration in software development is inevitable. As soon as one accepts that logic, one must then also accept that software development will be subject to friction (i.e. unexpected inefficiencies). When I plan the future for a piece of software, I expect to encounter ongoing friction, and I try to allow for that. I remain astonished at how many organisations assume that a master plan for their software can be rigidly followed.
I’ve built software that iterates slower than SpaceX is iterating starships.
Between 1 & 2: new actuation, launch pad cooling, hot staging and on and on
“For any given technology development, it’s how many iterations you have and the time between... See more
Patrick OShaughnessyx.com
In Elasticsearch, these partitions are known as shards . Each node of the Elasticsearch cluster can serve queries independently for the partition it manages, thereby increasing query throughput.
Improving query performance in ElasticSearch at scale
The choice of the routing key in our case was a combination of the unique identifier (UUID) and type of the primary participant of each event in a calendar. This choice was made based on the querying patterns of the consuming application and to maintain a degree of uniqueness.
Improving query performance in ElasticSearch at scale
GitHub Copilot Workspace Demo | Transform issues into plans
youtube.comDatabase Partitioning is when you split the data inside the database into smaller "databases". One partition holds a part of your data. All partitions together form the entire database.
Partitioning is often used with replication, which means each partition's data is copied onto multiple nodes. This way, even though each record is in only one partition, it can be stored on different nodes for fault tolerance. A node may hold more than one partition.
When using a leader-follower replication model, the mix of partitioning and replication might look like this:
Software problems tend to evolve over time into philosophy problems, a point that's come up in a few Diff pieces, like the Antithesis writeup and Asana's ontology-as-a-service ($). In this particular category, it's the philosophy of work and vocation: a bond trader, accountant, or social media manager doesn't necessarily have to spend much time... See more