Max,<br><br>Yes, different operators have different cultures. Some like to just buy stuff off the shelf, and some have the bravado to roll their own. We've been doing it in this organisation for the past 12 years now, and having our own internal dev team enables a lot of stuff. We still buy a lot of kit from vendors, and I probably wouldn't want to do all of that myself, but Erlang is perfect in integrating systems together.<br>
<br>Regarding patches, yes, it would be great if each of the OTP libraries could be forked on its own. It would be a bit less daunting to supply patches.<br><br>Chandru<br><div class="gmail_extra"><br><br><div class="gmail_quote">
On 26 November 2012 08:56, Max Lapshin <span dir="ltr"><<a href="mailto:max.lapshin@gmail.com" target="_blank">max.lapshin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It is a wonderful story! Usually such big guys love software, that is buggy, slow, costs several megabuck and is written in Java by thousands of low-cost developers, but your story is like a fairy tale about good world, where operator can switch to a 20K LOC simple working software written by small couple of engineers!<br>
<br>Thank you for this story.<br><br>Also I want to mention what you've told about OTP patch. It is a good argument in discussion: monolithic distribution vs many packages. If eldap was a project on github, you could just fork it. But currently it is not very convenient to compile and launch tests in single subfolder in otp/lib/...<br>
But I think it should be a separate topic <br><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Nov 26, 2012 at 11:27 AM, Chandru <span dir="ltr"><<a href="mailto:chandrashekhar.mullaparthi@gmail.com" target="_blank">chandrashekhar.mullaparthi@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Max, I work for EE which owns the Orange, T-Mobile and EE brands in the UK. And yes, we are migrating an online charging mediator to an in-house solution.<br>
<br>cheers<span><font color="#888888"><br>Chandru</font></span><div><div><br><div class="gmail_extra"><br><br><div class="gmail_quote">
On 26 November 2012 04:11, Max Lapshin <span dir="ltr"><<a href="mailto:max.lapshin@gmail.com" target="_blank">max.lapshin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Chandru, have I understood properly: you are working at Orange and you are migrating your own charging subsystem from external many-mega-bucks system to your own solution?<div><div><span></span><br>
<br>On Monday, November 26, 2012, Chandru wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br><br>I've recently worked on improving the performance of an erlang system we've developed which I've written up here --> <a href="http://chandrusoft.wordpress.com/2012/11/25/performance-tuning-of-dmc/" target="_blank">http://chandrusoft.wordpress.com/2012/11/25/performance-tuning-of-dmc/</a><br>
<br>Hopefully it will be of some use to someone.<br><br>cheers<br>Chandru<br><br>
</blockquote>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>