i think more than half the websites on the internet can run on serverless platform and that makes the web more secure and faster.
Serverless, Inc. lands $10M Series A to build serverless dev platform
131–140 of 204 posts
Re: Serverless, Inc. lands $10M Series A to build serverless dev platform
#132Earlier quoted context omitted.
Except there literally isn't any wires in WiFi. Unless you're talking about power cables on access points or other unrelated tech used on devices that have ethernet / whatever AS WELL AS WiFi?
Except there literally isn't any wires in WiFi. You think WiFi connects your laptop directly to the server in the datacentre? Interesting.
> Except there literally isn't any wires in WiFi.
> You think WiFi connects your laptop directly to the server in the datacentre? Interesting.
The way you've selectively quoted one sentence out of what is a very short post anyway just so you can imply that I'm oblivious to other infrastructure - even when my very next sentence describes other infrastructure - is in very poor taste.
Plus you're still failed to prove point. Yes ethernet over cat5e/6 cables and fibre exist, but they're not WiFi. Neither is 4G, Bluetooth, nor FM radio despite actually being wireless (unlike cat6 / fibre).
What you're arguing is beyond nonsensical; it's like saying "I drive to the railway station every morning therefore the train I then catch is also classified as a car."
The daft thing is if you'd talked about the wireless radio's antenna then you might have had a genuine point. Yet you went the "network cables are WiFi as well" argument instead. Go figure.
Re: Serverless, Inc. lands $10M Series A to build serverless dev platform
#133I don't understand the knee-jerk opposition people have to serverless architectures. I recently developed a service[1] with the serverless framework and it was the first time I enjoyed developing server-side code since the era of PHP on shared hosts, where you could just upload code and refresh the page. There's something freeing about never having to think about the server process or what happens if the server is po…
I help run a Node server, and we have some jobs that aren't run through CRON, but instead are set up using in-memory intervals. So I'm considering using a serverless setup to offload the work.
In your opinion, it easy to differentiate between dev/prod environments for development? How about logging?
Re: Serverless, Inc. lands $10M Series A to build serverless dev platform
#134Earlier quoted context omitted.
As far as I know, serverless isn't just FaaS. As you pointed out FaaS is to connect things, nothing more. For me serverless is pay-as-you go pricing, no over- or under-provisioning and last but not least, no server-management. Lambda, DynamoDB, S3, AppSync, Device Farm, Aurora, etc. are all serverless.
How would you distinguish it from "PaaS"?
The "serverless" model frees you of more tasks than PaaS, like capacity planning and scaling, also it's more flexible and fault tolerant.
Re: Serverless, Inc. lands $10M Series A to build serverless dev platform
#135Earlier quoted context omitted.
Except there literally isn't any wires in WiFi. You think WiFi connects your laptop directly to the server in the datacentre? Interesting.
> Except there literally isn't any wires in WiFi. > You think WiFi connects your laptop directly to the server in the datacentre? Interesting. The way you've selectively quoted one sentence out of what is a very short post anyway just so you can imply that I'm oblivious to other infrastructure - even when my very next sentence describes other infrastructure - is in very poor taste. Plus you're still failed to prove p…
is in very poor taste.
I believe my analogy to be a sound one, in that all wireless does is insulate the end user from mile upon mile of wiring, just as serverless insulated the user from racks upon racks of servers, and that you were - and are - being needlessly pedantic.
Re: Serverless, Inc. lands $10M Series A to build serverless dev platform
#136Earlier quoted context omitted.
I've read this analogy before, but it's weak enough to be inapplicable. With wireless networking and even phones, the wires have actually been eliminated, replaced wholesale by something else, radio. A better analogy would be something like the powerline ethernet systems, but nobody is calling them something controversial like "wireless" or "cableless". Put another way, I've seen cloud computing (of which "serverless…
the wires have actually been eliminated I guess you don’t understand WiFi then, it’s wireless between you and the basestation (say 10m) then all wired from there to the server (which might be thousands of miles). You just don’t see those wires - and the proof is you don’t even realise they exist
I've wired data centres so I'm aware wires exist. However wires are not WiFi. The WiFi in your example ends at the base station. Everything thereafter is still infrastructure but it's not WiFi.
Re: Serverless, Inc. lands $10M Series A to build serverless dev platform
#137Earlier quoted context omitted.
> Except there literally isn't any wires in WiFi. > You think WiFi connects your laptop directly to the server in the datacentre? Interesting. The way you've selectively quoted one sentence out of what is a very short post anyway just so you can imply that I'm oblivious to other infrastructure - even when my very next sentence describes other infrastructure - is in very poor taste. Plus you're still failed to prove p…
is in very poor taste. I believe my analogy to be a sound one, in that all wireless does is insulate the end user from mile upon mile of wiring, just as serverless insulated the user from racks upon racks of servers, and that you were - and are - being needlessly pedantic.
I don't think it's being pedantic if your analogy is based on a basic premise that is fundamentally untrue. I get there is no such thing as a perfect analogy but I'd at least expect the subject to be factually acuate even if the comparison is subjective.
Re: Serverless, Inc. lands $10M Series A to build serverless dev platform
#138Earlier quoted context omitted.
NoSQL has been and continues to be hugely influential. All major cloud players provide document/object based storage, as well as other NoSQL Solutions. The term "NoSQL" was dumb and overhyped... But I think it's really about using the correct storage solution for the job. Non relational data should be stored in a non rdbms. Key-Value stores like Redis are immensely useful as caching layers (but they offer so many mor…
> The reason "NoSQL" dbs got popular are because in my experience Monolithic large relational databases are hard to scale. I've met a lot of people whomst thought they had to scale that big. Very few handled anything that couldn't run off a beefy postgres installation. The purpose of a system is what it does. People don't use nosql to scale because they don't need to scale, so what does it do? People use nosql to not…
> Very few handled anything that couldn't run off a beefy postgres installation.
My impression, from attempting to evangelize scaling "up" before scaling "out" (because it's both cheaper and much lower effort/labor/time) is that vanishingly few programmers have any idea what a "beefy" installation would even look like.
I routinely encounter implicit assumptions (partially driven, these days, anyway, by what VPS and cloud providers off) that the "largest" servers 2U (or 4U, if I'm lucky) and are I/O limited by the number of disks they an hold in their chassis.
Similarly, there seems to be a lack of awareness of just how big main memory can be on a single server, even before paying a price premium for higher-density modules.
Not knowing where the price-performance curve inflection points (for memory and/or CPU) happen to be also seems to be associated with not knowing where the price tops out. It's as if they fear the biggest server they can (and will be forced to) buy will cost a million bucks, rather than $100k.
Re: Serverless, Inc. lands $10M Series A to build serverless dev platform
#139Earlier quoted context omitted.
> The reason "NoSQL" dbs got popular are because in my experience Monolithic large relational databases are hard to scale. I've met a lot of people whomst thought they had to scale that big. Very few handled anything that couldn't run off a beefy postgres installation. The purpose of a system is what it does. People don't use nosql to scale because they don't need to scale, so what does it do? People use nosql to not…
Very much this. Sooooo many times I hear the cry of "does it scale?" To which I reply, "Does it need to?!" At my last company we had a developer question scalability constantly despite the fact that the average customer of an instance of our product had about 200 users.
I like to add, "does it need to beyond what's delivered by Moore's Law?" (which I use a metaphor for all increases in computing performance, including I/O, which has, of course, increased at a much slower, but far from zero, pace).
If your CPU utilization from user growth is doubling every 2 years, but so is CPU capacity, then don't worry about it.
Re: Serverless, Inc. lands $10M Series A to build serverless dev platform
#140Earlier quoted context omitted.
That assumes that a local function call has the same failure rate as a remote function call to a microservice, which in my experience is very much not true. If I have a local function in the same language I can pretty much assume that a call to that function will actually call that function. With a remote call over HTTP or whatever I can't, so that is an additional failure I need to handle.
I'm not sure I understand. Why would an RPC call a different function than what you expect? I'll grant you that there is more complexity in this approach, but I believe that fault tolerance is something you improve with microservices, not something you regress on.
It's not that it would call a different function, but that sometimes the RPC will fail to call the function. You can't get a network error calling a function which is in memory on the same process.