4 ms·
> It's really important to know what the most difficult problem you will encounter when solving a problem. If you can't solve the most difficult problem you'll
by rdtsc 10y ago
> It's really important to know what the most difficult problem you will encounter when solving a problem. If you can't solve the most difficult problem you'll be stuck when you get to it.
That is very true and is hard to do. I have seen people (including me in the past) pick fun, easy to understnad, easy to iterate on pieces first. And often push the harder things further down the road.
> The problem with this method is that you probably don't know what the most difficult problem is when you start.
Often in distributed systems it is fault scenarios, how it handles partitioning, network errors and other funkiness like that.
Security is like that as well. Bolting those on at the end / later often doesn't work very well.
> Erlang was designed for building fault-tolerant systems
I like to often say that highly concurrent and distributed systems without fault tolerance become useless as the concurrency or scale increases.
If some service segfaults and if it handles millions of transaction now all those transactions stop and service become unavailable. Don't need Erlang for that of course, can use containers, monitoring systems, consistent key-value stores and such.
The use case for Erlang is also a business use case -- it means saving money on having a smaller ops team and having a smaller development team. Developers are expensive, 24/7 ops are expensive. If your code is lines and lines of low level code, in language not designed for fault tolerance -- means weeks and months debugging and developing issues where in Erlang the problems can be expressed a lot more concisely.
I have seen subsystems crash and restart without affecting the core of the service. Nobody had to get up at 4am, can wait till morning.
Hot code updates may sound like a gimmick but combined with dynamic tracing it can save the day, helps find and fix problem quickers with often 0 downtime (I have seen it happen).
- kumartanmay 10y agoThe idea is to solve the hardest problem and most of us will get stuck to it because it won't be easy to find the beginning of the problem. So, it's imperative to decide the origin of the problem. The origin of the problem might look very basic, but that is where you got to start. It's very important to go in the direction of solving the hardest problem than going in the direction that makes money.