4 ms·
One of the questions I've been asking is we've basically had physical servers -> VM -> cloud -> container orchestration on about a decade long cadence. So what'
by ghaff 4y ago
One of the questions I've been asking is we've basically had physical servers -> VM -> cloud -> container orchestration on about a decade long cadence. So what's next--especially considering you can argue a lot of the low-level architectural things haven't really changed during that period. But, then, perhaps architectural details don't matter a lot at this point relative to things like AI/ML. Even WASM is mostly in the weeds.
- riskable 4y agoPhysical servers (or devices) are next, obviously! IT is cyclical.
- theRealMe 4y agoSpeaking of cyclical IT, my estimate is going “forward” to the terminal/mainframe-esque concept of simple and cheap “terminals” aka laptops that you use to log into a much beefier “mainframe” aka cloud workstation. I’m at a FAANGMULA and I’ve been using a cloud workstation from my cheap laptop as my daily driver for months now. The VM is so much higher-spec’d than what they would have bought me for a desktop. Just don’t look at the price if you plan to run it 24/7…
- ghaff 4y agoAnd for the mostly browser-based stuff I do, outside of multimedia and some development, I'm pretty much on a terminal (except we call it a browser) which I run from 2015-vintage Macs.
- deleted 4y ago[deleted]
- cranberryturkey 4y ago> FAANGMULA killin' me smalls.
- jadtz 4y ago> FAANGMULA Only somebody who does not work at FAANG uses FAANGMULA, so why not just go with MULA.
- MaanuAir 4y agoThey already are: with these on-prem versions of the common public clouds.
- RobotToaster 4y agoWouldn't surprise me if RPi style single board computers do start making headway as "microservers". Instead of renting a VM or running docker containers you rent a small physical server for each service.
- herbst 4y agoJust recently moved all my services that don't need a 100% to a dedicated server instead of several cloud VMS running containers. It's cheaper, less overhead, simpler to configure and works just as well (so far)
- ianai 4y agoClearly riscv servers you design from the CPU up (with some very helpful software). Only to be replaced by the N types of computers that typically wind up being designed somewhere around years 3-5. To later be replaced by those same systems in the cloud. Or of course world war 3 happens and the latest, greatest thing going in IT is “I mean I’m still alive, whatever that’s worth.” And making anything usable from whatever is found. Even a blinking LED becomes either neat or a way for a roving warboy to find/kill you.
- Calamitous 4y ago“Locally hosted cloud infrastructure!”
- screwturner68 4y agoGreenlake?
- mabbo 4y agoI'm excited by the idea of WASM being 'the thing' because it basically boils down to passing raw executables around, and running them in trusted contexts. It's the ultimate end to the cycle of removing all operating systems.
- loxias 4y agoI'm excited too, but be advised, people said the same thing about the revolutionary "write once, run anywhere" programing language and platform coming out from Sun Microsystems in the 90s... "All of this has happened before, and it will all happen again." ;-)
- Waterluvian 4y agoNow that SharedArrayBuffer is back (for a while now), we have everything we need to do parallel programming in a browser. I feel like that unlocks enormous opportunities that weren’t previously realized with WASM.
- revelio 4y agoIt doesn't remove the OS, it "just" requires all C/C++ to be ported to the new WASM/Browser OS. Which isn't very exciting. The browser isn't meant to be an OS.
- ElevenLathe 4y agoThe trendy (meaning both that it is hyped and that it follows the trajectory of the trend you identified) answer is serverless/scale-to-zero (Lambda, Cloud Run, etc.). That said, Lambda has been out for a while and seems to have avoided taking over the world. Generic vCPU-hours are so cheap now though that it isn't compelling from a a cost perspective (serverless will either cost you more at the high end of the scale, or else save you a few bucks a month on your idle instances at the low end). Also, the developer experience isn't as good yet IMO. Thinks like LocalStack help, but it's still not natural-feeling to deploy a big application this way. (scale-to-zero it's great for small side projects though -- I have a few apps in Cloud Run that cost me like a nickel a month, a few dollars if I have a good month in terms of traffic).
- ghaff 4y agoAnd serverless isn't even all that distinct from containers, see e.g. Knative. You're mostly still doing stuff around a Unix process model.
- ashrafulla 4y agoThis is a fantastic take (seriously, no sarcasm here). I'll add that serverless platforms have not actually shown the ability to scale _efficiently_. It feels like every software architect has been talking about the 2023 March post^ from Amazon Prime Video on migrating from serverless to serverful. That is a direct response to the inability of serverless to scale because under the hood it is serverful but limited. Besides AWS Lambda and Google Cloud Run others have tried OpenFaaS and Cloudflare Workers. I think only Cloudflare Workers have "scaled" but that's because it's limited scale for each service at the edge with lots of edge devices. I do not know if this is solvable: a permanent service with light autoscaling handles even inconsistent load so well and reduces operational complexity so much that I don't know if serverless will be anything more than toys. It is no coincidence that AWS Lambda's first language was a frontend language* (Node.js). Those use cases have low to moderate scale (because after that you split frontend and backend). ^Amazon Prime Video post: https://www.primevideotech.com/video-streaming/scaling-up-the-prime-video-audio-video-monitoring-service-and-reducing-costs-by-90 https://www.primevideotech.com/video-streaming/scaling-up-th.... *First mention of AWS Lambda languages in AWS Compute Blog only mentioned nodejs: https://aws.amazon.com/blogs/compute/container-reuse-in-lambda/ https://aws.amazon.com/blogs/compute/container-reuse-in-lamb...
- samstave 4y agoThis is off-the-cuff, so forgive me if it sounds dumb ; What about 'AI Tendrils' <-- tiny AI workers on little devices that feed the Mother AI - like an agent would monitor, but you tell it what info or behaviours are allowed and have that securly streamed back to the AI/model/LLM? (I dont know where the data would go) but then when you run your query/prompt youre running it against a much closer-to-processing-power than if you had to go query each device on a request? -- I thought this output from GPT was interesting for thinking of the above: https://i.imgur.com/WsxwuJh.png https://i.imgur.com/WsxwuJh.png and a BOM https://i.imgur.com/5g1mXfp.png https://i.imgur.com/5g1mXfp.png https://i.imgur.com/MdbQKx1.png https://i.imgur.com/MdbQKx1.png https://i.imgur.com/Bi0PRTQ.png https://i.imgur.com/Bi0PRTQ.png -- Actually, I asked gpt to recommend additional columns, here is the result User what columns would you suggest to add ChatGPT Here are some additional columns that you may consider adding to the HN table: * Display type: OLED, LCD, AMOLED, etc. * Display resolution: the number of pixels on the screen. * Water resistance: the level of protection against water damage. * Heart rate monitor: whether the wearable device has a built-in heart rate monitor. * Sleep tracking: whether the wearable device can track your sleep patterns. * Music playback: whether the wearable device can play music and if it has built-in storage. * NFC: whether the wearable device supports near-field communication for contactless payments. * Voice assistant: whether the wearable device has a built-in voice assistant like Siri, Google Assistant, or Alexa. * Other sensors: such as an accelerometer, gyroscope, barometer, altimeter, or compass. Keep in mind that the more columns you add, the wider the table becomes, which may make it more difficult to view or analyze. So, you may want to choose the most important columns for your specific use case and audience.