Skip to main content

· One min read
James Moore

When you're at the beginning of a new software project, there's a question you should ask yourself, which is:

What architecture should you use for your application?
client/server or local or ...

Odds are, you probably don't explicitly ask this architecture question anymore, because you intuitively know the answer, which is almost always client/server right?

· 5 min read
Michael Tanenbaum

Compute needs are rapidly growing, and individual CPU speeds have not kept pace with that increase. The simple fact is they aren’t ever going to be able to - we face the everpresent constraint of the speed of light, regardless of how many transistors we can cram onto a chip. Sure, stacking CPU cores solves the raw processing needs, but just cobbling more cores into a single server can’t provide the redundancy for zero-downtime or the scale for massive computing jobs.

· 5 min read
Michael Tanenbaum

When we consider “the Edge,” it can be easy to forget that the edge is you. It’s your data. It’s your phone, your laptop, your wireless headphones, your smart tv, your browser tab.