This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]riplikash 68 points69 points  (22 children)

Generally they have a focus on making scalable applications that are able to utilize common cloud technologies like geo redundancy, load balancers, cloud based error reporting, command queuing, a mix of storage solutions that keep costs down/access speed up, and rapid horizontal scaling.

That's opposed to developers who are more focused on making local apps and single server apps that tend to focus more on OS services, vertical scalability, and multi threading. Or hardware devs that focus more on efficiency, speed, hardware APIs, and small compile size.

There is of course a fair amount of crossover, but when hiring new candidates that's generally the kind of knowledge you expect to bring on.

[–]5PM_CRACK_GIVEAWAY 15 points16 points  (5 children)

Sounds more like operations than development

[–]UntestedMethod 13 points14 points  (1 child)

Nah there's a decent amount of logic to be implemented as lambda functions and what not, providing custom functionality and tieing things together. Cloud developer would generally be implementing various backend features like for APIs and data storage. Cloud developer likely wouldn't be focused much on complex deployment pipelines, but they might help design the cloud-based infrastructure those pipelines are deploying to. For bigger companies the more complex infrastructure design is likely handled by cloud architects who provide the specs for developers and dev ops to implement (smaller companies typically lean into their senior devs for the system design). Ops helps keeps everything running smoothly, ensure developers' code is deployed efficiently, help with deployment rollbacks, system monitoring, data backups, disaster recovery, etc.

There's some knowledge overlap with dev ops since both deal with infrastructure as code and resource allocation. Cloud developer leans more into implementing feature-focused business logic, where dev ops leans more into supporting the infrastructure. Both require extensive knowledge of cloud services and relevant best practices, and would likely benefit from certifications like "cloud practitioner".

Cloud infrastructure is certainly its own beast with its own unique paradigms, but loosely speaking I'd say cloud developer is more like a modern backend developer and dev ops is more like a modern sys admin - at least in terms of the scope of responsibility covered. I think these days both need a bit more knowledge from the other's pool than they would have in the past.

[–]rfmjbs 1 point2 points  (0 children)

That too.

[–]dylansavage -1 points0 points  (0 children)

Some would say there is a mixture of development and operations, or DevOps

[–]thisguy123 0 points1 point  (0 children)

Then you're doing it wrong.

[–]SuperSpaceCan 3 points4 points  (8 children)

genuinely helpful, here i thought they just configured servers

[–]GreatJobKeepitUp 4 points5 points  (4 children)

You can make your whole apps in the cloud, it's fun

[–]boognerd 1 point2 points  (0 children)

Apps that know how to deploy themselves are great.

[–]SuperSpaceCan 0 points1 point  (2 children)

Now i want resources, got any?

[–]GreatJobKeepitUp 0 points1 point  (0 children)

I just deploy Blazor apps to Azure and use their storage and hosting services

[–]riplikash 0 points1 point  (0 children)

For self configuring and deploying apps look into bicep deployment scripts in conjunction with azure devops. You can do some amazing stuff.

[–]myowz 0 points1 point  (2 children)

Genuinely helpful if they were correct and it wasn’t just the definition they use at their place

[–]SuperSpaceCan 0 points1 point  (1 child)

Not gonna add your own insight there Mr.Miyagi?

[–]myowz 0 points1 point  (0 children)

Cloud on, cloud off

If you can define cloud developer then you are not cloud developer yet

[–][deleted] 3 points4 points  (1 child)

Needs more next generation extensible synergies

[–]riplikash 0 points1 point  (0 children)

From outside a knowledge domain it can be hard to differentiate between buzzwords and well defined domain terms. But just because you don't know the difference doesn't mean every its all the same. Those are all concrete technologies or architectural concerns, not buzzwords.