Why we ask where your data lives
It sounds like a simple question. The answer usually involves a database, object storage, backups, logs, notifications and a search index.
Occasional posts about how this is actually done. No announcements, no industry news, nothing written to rank for a search term.
It sounds like a simple question. The answer usually involves a database, object storage, backups, logs, notifications and a search index.
Technically true and practically incomplete. The useful part is precisely that somebody else owns a great deal of difficult infrastructure.
Reselling someone else’s capacity is cheaper to start and worse to answer questions about. Here is what running the machines ourselves actually changes.
An uncomfortable question to ask a supplier, and a very good one. Designing for departure makes the relationship better while it lasts.
Age is not a defect. A rewrite becomes interesting when the existing system prevents necessary change, which is a different test entirely.
We build in both, so we have no incentive to sell you the wrong one. The choice is usually decided by a single question.
Good infrastructure is not designed to stop servers failing. It is designed around what happens next.
A clever shell script only one person understands is a liability with good intentions. Production should be predictable, replaceable and mostly forgettable.
Every system we have been asked to rescue had backups. The interesting question is never whether they run.
The developer says the server is slow. The hosting provider says the server is fine. Everyone has supplied an answer and nobody has solved anything.
Describe the workload or the system you have in mind and we will tell you what it needs, what it costs, and whether we are the right people for it.