3 ms·

Kind of? How many servers did the average app depend on in 1998? 1? Get dual HD and you were in decent shape. Compare to a modern microservice app, that mayb

Kind of? How many servers did the average app depend on in 1998? 1? Get dual HD and you were in decent shape. Compare to a modern microservice app, that maybe depends on 100 internal services and 4-5 external services. A lot of things need to go right or mostly right for things to function.

ProAm 9y ago
Sounds like an argument against micro services?
- jameskegel 9y ago
  I'd give a dollar to hear how you arrived at this conclusion.
- stouset 9y ago
  Only if you don't stop to consider the alternative.
  - ProAm 9y ago
    "The Wheel of Time turns, and Ages come and pass, leaving memories that become legend. Legend fades to myth, and even myth is long forgotten when the Age that gave it birth comes again."
Xeoncross 9y ago
I think you both have a point. The tools are mostly all here now (some in primitive forms), but no one person on earth knows how to use them all. From netfilter to kubernetes to sharded redis instances to nginx RTMP to embeded golang structs and git commit hooks. It takes an amazing team to cover all the bases.
cat199 9y ago
You are thinking small scale, and public web. The fact that VAXClusters were already going out of fashion by that time, and the fact of IBM's parallel sysplex existing by that time already negate your point. previous $employer had built a globally distributed multisite c&c processing system twice by then and were in the process of revamping it for a 3rd.. 1st on mainframes & remote serial compute devices in the 80s, then on unix workstations in the early-mid 90s. They were by far not alone in dealing with this level of complexity for the time.
myrandomcomment 9y ago
My ISP? 5 racks in 32 cities as POP. Each POP had 10 Sun Netra T1 1RU boxes behind SLB. All those were a service cache to offload the main DC which had...hum... ~100 or so Sun E450 (4x480Mhz Usparc3, 4GB RAM, 20x4GB or 9GB UltraSCSI3 drives, 2x1G NICs). There was a cluster filesystem also. We had huge databases, etc. This is just not that hard today.

ProAm 9y ago

Sounds like an argument against micro services?

jameskegel 9y ago
I'd give a dollar to hear how you arrived at this conclusion.
stouset 9y ago
Only if you don't stop to consider the alternative.
- ProAm 9y ago
  "The Wheel of Time turns, and Ages come and pass, leaving memories that become legend. Legend fades to myth, and even myth is long forgotten when the Age that gave it birth comes again."

Xeoncross 9y ago

I think you both have a point. The tools are mostly all here now (some in primitive forms), but no one person on earth knows how to use them all. From netfilter to kubernetes to sharded redis instances to nginx RTMP to embeded golang structs and git commit hooks. It takes an amazing team to cover all the bases.

cat199 9y ago

You are thinking small scale, and public web. The fact that VAXClusters were already going out of fashion by that time, and the fact of IBM's parallel sysplex existing by that time already negate your point. previous $employer had built a globally distributed multisite c&c processing system twice by then and were in the process of revamping it for a 3rd.. 1st on mainframes & remote serial compute devices in the 80s, then on unix workstations in the early-mid 90s. They were by far not alone in dealing with this level of complexity for the time.

myrandomcomment 9y ago

My ISP? 5 racks in 32 cities as POP. Each POP had 10 Sun Netra T1 1RU boxes behind SLB. All those were a service cache to offload the main DC which had...hum... ~100 or so Sun E450 (4x480Mhz Usparc3, 4GB RAM, 20x4GB or 9GB UltraSCSI3 drives, 2x1G NICs). There was a cluster filesystem also. We had huge databases, etc. This is just not that hard today.