[erlang-questions] Erlang for Payment Systems

Lee Sylvester lee.sylvester@REDACTED
Sat Apr 30 01:07:14 CEST 2016

Hi Hassan,

String manipulation is potentially Erlang's main weakness. However, there
are ways and means.  Firstly, I would create a simple prototype that
performs the kind of string manipulations you need and testing its speed.
If it is not fast enough, you can always implement the string specific
functionality in a C library and hook into it via Erlang, so that Erlang
handles all your processes and load balancing, but having the string
specific work handled natively.

I hope this makes sense?


On Sat, Apr 30, 2016 at 10:09 AM, Hassan Sowwan <h_sowwan@REDACTED>

>  Hello,
> I am trying to implement payment messaging middleware and would like to
> explore the option of using Erlang/OTP.
> The application will be used in banking industry to interface with EFT
> payment switch/networks and core banking system to process card
> transactions.
> It will be responsible to perform following tasks:
>    - Communicate with external interfaces using ISO 8583 messaging format
>    ( thru TCP/IP)
>    - Receive huge amount of data over the socket ( HEX, BINARY, EBCIDIC),
>    which represents financial transactions.
>    - Parse/decode the received data.
>    - Perform some checking in database for validation
>    - Interface with host security module to validate customer PIN and
>    other security checks.
>    - Sends the request to core banking system via XML or web services call
>    - Respond back to external interfaces by formulating the response
>    message in ISO 8583 format
> Obviously, such applications have to be concurrent and fast enough to
> process transactions within few seconds.
> Now my question here, is Erlang a good choice for implementing this type
> of applications ?
> Can Erlang handle string processing efficiently without impacting the
> system performance?
> As stated before, there will be a lot of string manipulation to decode
> data received over the network, so I am not sure whether erlang fits
> perfectly or not.
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20160430/fc187fe6/attachment.htm>

More information about the erlang-questions mailing list