5 ms·

Telna [1] is using Pharo to resolve roaming for an incredible amount of daily network traffic. I'm in their dev team. Here you have may others using it in prod

Telna [1] is using Pharo to resolve roaming for an incredible amount of daily network traffic. I'm in their dev team. Here you have may others using it in production: https://pharo.org/success.html https://pharo.org/success.html [1] https://www.telna.com https://www.telna.com

igouy 5y ago
Curious -- Why not Erlang?
- sebastianconcpt 5y ago
  The GTP client that touches Pharo is done in Erlang.
  - igouy 5y ago
    So Pharo for the front-end?
    - sebastianconcpt 5y ago
      Pharo runs in the backend for resolving roaming for SS7, GTP and DIAMETER. It orchestrates a lot in there in order to provide Network Virtualization [1] [1] https://www.telna.com/blog/why-virtualization-is-critical-to-mobile-networks https://www.telna.com/blog/why-virtualization-is-critical-to...
theamk 5y ago
This is super interesting! Do you have more information about this? - How many developers are working on that codebase simultaneously? - What is your workflow like? Do you have any sort of CI system? How does it work? - How does your deployment works? Is it a single beefy machine or a fleet of smaller ones? - What kind of network protocols do you use? Any code generation? - How do you deal with errors -- are there equivalents of "coredumps" or "logs" in the Pharo world?
- sebastianconcpt 5y ago
  Yes, in the Pharo world there are coredumps, logs, serialization of the context of the exception (so you can open a debugger later from another host and see the messages walkback and inspect the values of all objects and its instvars on any step of that wallback), also I've made a RESTful REPL [1] to interact live with headless images and I'm cough secretly working in websocket based IDE. For the rest I can tell you that: - The CI doens't have anything special in it, just build and delivers, after many categories of tests, a docker image with the app ready for production. - Iceberg for a shared repo. Devs usually use one fresh image per new branch to work on. Flow is reasonably approximated to git-flow. - The app is generally architected as stateless as it can be so it can enjoy undefined horizontal scaling capacity. [1] https://github.com/sebastianconcept/REPLEndpoint https://github.com/sebastianconcept/REPLEndpoint
  - igouy 5y ago
    > websocket based IDE ? Like Resilient Smalltalk https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.84.7354&rep=rep1&type=pdf https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.84...
    - sebastianconcpt 5y ago
      Thanks for the reference I didn't knew about that one! What I'm working on is based on Pharo tho. It's an alternative IDE and accidentally a way to create apps that have multi-platform native look and feel.

igouy 5y ago

Curious -- Why not Erlang?

sebastianconcpt 5y ago
The GTP client that touches Pharo is done in Erlang.
- igouy 5y ago
  So Pharo for the front-end?
  - sebastianconcpt 5y ago
    Pharo runs in the backend for resolving roaming for SS7, GTP and DIAMETER. It orchestrates a lot in there in order to provide Network Virtualization [1] [1] https://www.telna.com/blog/why-virtualization-is-critical-to-mobile-networks https://www.telna.com/blog/why-virtualization-is-critical-to...

theamk 5y ago

This is super interesting! Do you have more information about this? - How many developers are working on that codebase simultaneously? - What is your workflow like? Do you have any sort of CI system? How does it work? - How does your deployment works? Is it a single beefy machine or a fleet of smaller ones? - What kind of network protocols do you use? Any code generation? - How do you deal with errors -- are there equivalents of "coredumps" or "logs" in the Pharo world?

sebastianconcpt 5y ago
Yes, in the Pharo world there are coredumps, logs, serialization of the context of the exception (so you can open a debugger later from another host and see the messages walkback and inspect the values of all objects and its instvars on any step of that wallback), also I've made a RESTful REPL [1] to interact live with headless images and I'm cough secretly working in websocket based IDE. For the rest I can tell you that: - The CI doens't have anything special in it, just build and delivers, after many categories of tests, a docker image with the app ready for production. - Iceberg for a shared repo. Devs usually use one fresh image per new branch to work on. Flow is reasonably approximated to git-flow. - The app is generally architected as stateless as it can be so it can enjoy undefined horizontal scaling capacity. [1] https://github.com/sebastianconcept/REPLEndpoint https://github.com/sebastianconcept/REPLEndpoint
- igouy 5y ago
  > websocket based IDE ? Like Resilient Smalltalk https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.84.7354&rep=rep1&type=pdf https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.84...
  - sebastianconcpt 5y ago
    Thanks for the reference I didn't knew about that one! What I'm working on is based on Pharo tho. It's an alternative IDE and accidentally a way to create apps that have multi-platform native look and feel.