Bending QR to the will of λ
We needed a short-link site for ourselves. Being us, we didn't sign up for one: we built it, at l12.gr. And because a short link wants a QR code, and a QR code wants our logo, we went the ex
Occasional posts about how this is actually done, and the odd piece of news from us. No industry news, nothing written to rank for a search term.
We needed a short-link site for ourselves. Being us, we didn't sign up for one: we built it, at l12.gr. And because a short link wants a QR code, and a QR code wants our logo, we went the ex
It sounds like a simple question. The answer usually involves a database, object storage, backups, logs, notifications and a search index.
An uncomfortable question to ask a supplier, and a very good one. Designing for departure makes the relationship better while it lasts.
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.
When mail stops arriving, the mail server is rarely the thing that broke. Three records decide whether you are believed.
The word describes everything from a fully operated system to a provider who installed the operating system once and will answer an email if it catches fire.
A server advertised at €8 a month costs €8 a month. That is not the same as what running your system on it costs.
New technology is fun. Production systems are not supposed to be fun. What a mature technology has accumulated does not show up in a feature comparison.
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.