Building software
sari and
Building software
Database 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:
Kai Krause on how short-lived software is relative to other art forms:
You can hum a tune you once liked, years later. You can read words or look a painting from 300 years ago and still appreciate its truth and beauty today, as if brand new. Software, by that comparison, is more like Soufflé: enjoy it now, today, for... See more
Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions
amazon.com
2019 when we got started with Linear, most SaaS websites at the time seemed to be these "Corporate Memphis" sites with vague benefit statements and weird colorful illustrations. No screenshots of the product and dark sites were very rare in B2B SaaS.
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
Byrne Hobart • Building for Power Users
Fantastic advice, for software builders:
Headline driven development
Here is a simple process for shipping software projects that works. First, decompose the project into a stream1 of headlines. Then pick an aggressive date to ship the first headline and work like hell to meet that date. Have everyone work only on one headline at a time– the
... See more