"Erlang vs OTP: Still Relevant in Today's Cloud-Based Landscape?"

[JALBA]

Title: Erlang vs OTP: Still Relevant in Today's Cloud-Based Landscape?

Hey guys, thought it was time to revisit this age-old debate. Erlang and OTP have been staples in the world of concurrent systems for decades, but as we shift more towards cloud-based infrastructures, I'm wondering if they're still worth the hype. Has anyone had experience implementing Erlang in modern cloud environments, or do you think it's time to look elsewhere?

 

[Prohor557]

"Erlang's still got its use cases, but for a lot of cloud-based projects, you can get similar results with other languages and tools. OTP's concurrency model is a beast, but sometimes it's overkill for smaller apps. I've seen more developers opt for Elixir nowadays due to its more modern approach."

 

[BonS]

Honestly, I think Erlang and OTP still bring their own unique value props to the table, especially for high-availability and fault-tolerant systems. The built-in support for distributed programming and hot code swapping is still unmatched by many other langs, if you ask me.

 

[DDR111]

"Dude, OTP (Erlang's standard library) still holds a special place in my heart. Its concurrency and scalability features make it perfect for building distributed systems that can handle massive traffic, which is super relevant in today's cloud-based landscape."

 

[AcidOverdose]

"OTP is still a beast when it comes to distributed systems, but Erlang can be a bit overkill for smaller projects. I'd say it's still relevant, but more in the context of building fault-tolerant systems rather than your average web app. Has anyone here used the newer languages like Rust with async/await?"

 

[glashev]

I still think OTP is a solid choice for building robust distributed systems. Yeah, it's not as sexy as some of the newer options out there, but its fault-tolerant design and supervision trees still hold up pretty well to scrutiny. Anyone have experience putting Erlang to work in a cloud-based setup?

 

[Necko]

market updates - let's talk

 

[Raquel26022000]

"Imho, OTP is still a beast when it comes to building fault-tolerant systems. Its built-in supervision and process management features make it a no-brainer for cloud-based workloads. Anyone using Erlang + OTP in production?"

 

[borisx00]

"Erlang's lightweight concurrency model still has its uses, but IMO OTP can feel like a double-edged sword - it's robust, but can be a pain to work with if you're not familiar with its quirks. I've seen it shine in high-traffic systems, though. Not a fan of OTP, personally."

 

[Vibesounds]

"Erlang and OTP are still super relevant imo, especially for building distributed systems and fault-tolerant apps. The language's built-in concurrency features and robust supervision trees are still unmatched. Anyone using Erlang for their projects, I'd love to hear about your experiences!"

 

[Todayweplay]

"Erlang's concurrency model is still unmatched for real-time systems and distributed apps, but OTP's complexity might be overkill for smaller projects. For cloud-based apps, I'd recommend a more modern and flexible approach like async-python or node.js. Has anyone explored using Erlang for microservices?"