Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DigitalOcean’s quarterly report on developer trends in the cloud

digitalocean.com

Post reply on HN
Print view View original

21–30 of 94 posts

Re: DigitalOcean’s quarterly report on developer trends in the cloud

#21

Post by digi_owl »

weberc2 wrote: post #14
sandGorgon wrote: post #6

Here's the interesting learning for me: While Kubernetes was most popular overall, the smallest companies (1-5 employees) use Docker Swarm more often (41 percent use Swarm vs. 31 percent that use Kubernetes). Did not know Swarm was this popular. Even overall Swarm is 35% to K8s 42% However, there is a huge proliferation of hosted K8s services - AWS, GCP, Azure, Digitalocean, tons of others. Nobody seems to be making…

Swarm is dead simple to get up and running; it's baked into Docker. Maybe k8s is easy too, but I've always run into issues and the value proposition for pushing past them was never clear to me. There's no doubt in my mind that there are very good reasons to use k8s, I just haven't found them (nor looked especially hard).

And 1-5 employees sounds like the kind of business that would just as well stack a few gray boxes in a room and call it a day.

Re: DigitalOcean’s quarterly report on developer trends in the cloud

#22

Post by moduspwnens14 »

brightball wrote: post #3

> Serverless computing is in a much earlier stage of adoption, with nearly half of developers failing to clearly understand what it is. I've seen this called Function as a Service and honestly I think using that term instead of Serverless would go a long way to fixing this issue because 1) it clearly communicates what it is 2) there's not actually such thing as serverless since the functions are still running on serv…

> I've seen this called Function as a Service and honestly I think using that term instead of Serverless would go a long way to fixing this issue

But "Functions as a Service" doesn't cover what it is, though.

The following AWS services are "serverless" but would not be "function as a service:"

* S3

* API Gateway

* SQS

* SNS

* Cognito

* DynamoDB

* CloudWatch (logs and metrics)

* Step Functions

In all cases, you are not provisioning or managing servers. Scaling is linear and costs are linear based on how much you use them, and typically based on what's actually being used (bytes stored, requests made, etc.) and not per-node. Because they're all hugely multi-tenant, they also cost almost nothing to use at low scale.

"Functions as a service" covers serverless compute, but it doesn't cover the huge architectural difference (from the developer's perspective) between the services above and rolling your own (for example) S3.

Re: DigitalOcean’s quarterly report on developer trends in the cloud

#23

Post by Kurtz79 »

codingdave wrote: post #8

I find it interesting (and perhaps predictable) that while only 11% of people had a top consideration when taking a job of "Quality of manager or management", 47% of people cited "Leadership / management was bad" as a reason for leaving a job.

I find 11% a surprisingly high percentage, since I would think "Quality of manager or management" is something very hard to assess during a selection process.

Re: DigitalOcean’s quarterly report on developer trends in the cloud

#24

Post by fhood »

codingdave wrote: post #8

I find it interesting (and perhaps predictable) that while only 11% of people had a top consideration when taking a job of "Quality of manager or management", 47% of people cited "Leadership / management was bad" as a reason for leaving a job.

Pretty hard to gauge the quality of management from the outset though.

Re: DigitalOcean’s quarterly report on developer trends in the cloud

#25

Post by yani »

abledon wrote: post #9

Has anyone chosen digital ocean over aws/gcp/aZure when building a scalable setup (for pricing reasons). Eg setting up your own load balancers/ private master slave dB machines / bunch of ansible to organize it all.

Yes. We are using DO over AWS. Our bill is $120/month. We serve 21m web requests per month for that amount.

Re: DigitalOcean’s quarterly report on developer trends in the cloud

#26

Post by brightball »

moduspwnens14 wrote: post #22
brightball wrote: post #3

> Serverless computing is in a much earlier stage of adoption, with nearly half of developers failing to clearly understand what it is. I've seen this called Function as a Service and honestly I think using that term instead of Serverless would go a long way to fixing this issue because 1) it clearly communicates what it is 2) there's not actually such thing as serverless since the functions are still running on serv…

> I've seen this called Function as a Service and honestly I think using that term instead of Serverless would go a long way to fixing this issue But "Functions as a Service" doesn't cover what it is, though. The following AWS services are "serverless" but would not be "function as a service:" * S3 * API Gateway * SQS * SNS * Cognito * DynamoDB * CloudWatch (logs and metrics) * Step Functions In all cases, you are no…

All of those would fall under IaaS/PaaS.

If we're qualifying anything on a server that developers don't have to manage themselves as serverless than anything with an API becomes serverless...despite all of them actually running on servers.

Re: DigitalOcean’s quarterly report on developer trends in the cloud

#27

Post by DannyB2 »

peterwwillis wrote: post #19

I realized recently that Serverless is to developers as credit cards are to college students. Remember when VMs came out, and people were like, great! Now I can constrain the resources of my OS! I can run 10 OSes on one machine! I'll save so much money ! Then we gave individual teams access to create as many VMs as they wanted, and suddenly all the hardware was used up. Now do that, but in the cloud, with unlimited r…

But Moooooooom! It's all virtual! There are no hardware resources being used up!

(until the bill comes)

Re: DigitalOcean’s quarterly report on developer trends in the cloud

#28

Post by Steltek »

peterwwillis wrote: post #19

I realized recently that Serverless is to developers as credit cards are to college students. Remember when VMs came out, and people were like, great! Now I can constrain the resources of my OS! I can run 10 OSes on one machine! I'll save so much money ! Then we gave individual teams access to create as many VMs as they wanted, and suddenly all the hardware was used up. Now do that, but in the cloud, with unlimited r…

In my experience, those VMs were used briefly then left to rot. Consuming a large reserve of resources while doing nothing. Serverless should at least reduce the overhead of orphaned projects out there.

Re: DigitalOcean’s quarterly report on developer trends in the cloud

#29

Post by codingdave »

fhood wrote: post #24
codingdave wrote: post #8

I find it interesting (and perhaps predictable) that while only 11% of people had a top consideration when taking a job of "Quality of manager or management", 47% of people cited "Leadership / management was bad" as a reason for leaving a job.

Pretty hard to gauge the quality of management from the outset though.

I'm curious why you think so?

I normally ask questions about various non-tech topics including conflict resolution, team makeup, strategy, product management priorities, how they mentor junior team members, etc. Those discussions may not be able to tell the difference between a good vs. great leader, but they absolutely will raise red flags from a bad leader.

Re: DigitalOcean’s quarterly report on developer trends in the cloud

#30

Post by manigandham »

moduspwnens14 wrote: post #22
brightball wrote: post #3

> Serverless computing is in a much earlier stage of adoption, with nearly half of developers failing to clearly understand what it is. I've seen this called Function as a Service and honestly I think using that term instead of Serverless would go a long way to fixing this issue because 1) it clearly communicates what it is 2) there's not actually such thing as serverless since the functions are still running on serv…

> I've seen this called Function as a Service and honestly I think using that term instead of Serverless would go a long way to fixing this issue But "Functions as a Service" doesn't cover what it is, though. The following AWS services are "serverless" but would not be "function as a service:" * S3 * API Gateway * SQS * SNS * Cognito * DynamoDB * CloudWatch (logs and metrics) * Step Functions In all cases, you are no…

Those are just managed services, as in managed versions of I/P/F/S-aaS.

"Serverless" can be applied to every SaaS product ever made and is just an all-around meaningless and dumb-sounding term.

Post reply on HN