cmullaparthi

FWIW, we've been working on building a chat application. Still very much in beta stage, but trying to build something useful.

https://joinbackchannel.chat

Not sure which telco that is - but in the UK, impact on emergency calls is taken into account for every change that happens. This was non-negotiable in the 15 years I spent at a telco.

I agree with this sentiment. I programmed in Erlang for more than a decade before Elixir came along and I couldn't see the point of it. When I first picked up Erlang in '99 it was a breath of fresh air. The simplicity of the language blew me away (or maybe I just had a very good tutor).

Waitrose in the UK is like that. They seem to place trust in the customer which feels nice. I don't know if they have some clever ways of monitoring customers, but it feels good not to be treated with suspicion. I've never had anyone check my bags.

Sainsburys annoys me every time. The slightest delay in putting the scanned item on the scale and it starts nagging you, very loudly. I avoid them as far as possible. M&S is the same - nice place to shop in, but self checkout is unpleasant.

Tehelka is one of the few publications in India I would trust.

Just saw this. We use Erlang extensively within T-Mobile UK - have been doing so for the past 11 years. A lot of our core network systems are built using this and it is rock solid. Can't recommend it enough!

Yes, I agree. There are a few ways around that:

- Some out of band signalling between the edge and the core to indicate current load levels at the core.

- Implement similar form of overload protection at the core. You might now say, "Aha! But you're throwing away messages you've accepted". The answer is no: the edge nodes are typically just relaying messages after some checks, application layer processing is typically done in the core.

This thread is becoming slightly hand-wavy but I hope you get the gist of what I'm saying :)

Yes, it is possible. You have to ensure that every edge node is configured in such a way that it allows only a certain amount of traffic to a "inner" node. And if it finds that the inner node isn't as responsive as it should be, it has to scale back how much traffic it will accept.

For real time traffic, where queuing doesn't make sense, there isn't anything else you can do really.

The idea is that there is something very wrong with your design if you allow that to happen. In telco networks, once a message is accepted into a system, it is expected to be processed. You should throw away any messages you can't handle (because of overload) at the edge of the system. The same principle can be applied for any system which is serving any sort of network traffic.

If this unbounded message generation is happening within the system, again there is something wrong. You shouldn't be in a situation where a process is producing messages which other parts of the system cannot consume.

C++ > Erlang

Yes, I hadn't thought of that! Thanks for the suggestion.

Thanks for the suggestion. I'll take a look.

Thanks all for the comments. I've tried all those approaches, but failed so far. I'll keep trying.

How do people deal with staff who are quite clever, but write very complex code? I know a person who is a very good engineer in that he understands the underlying principles, but writes horribly complicated code. I'm trying to get him to write simpler code, but haven't succeeded so far.

Everything Everywhere Ltd. Two permanent "Senior Designer" positions based in Hatfield, UK. Looking for solid Erlang programming skills. Knowledge of IN/SS7 a bonus.

http://www.orangejobs.co.uk/fe/tpl_orange01.asp?newms=jj&...

Please ignore the C++/Java in the description. I'm looking for people who are currently programming in Erlang.