Erlang Live Text Replacement
Budget: $10 – $30 CAD
I need an experienced Erlang/OTP developer to extend an already-running application by adding a brand-new feature focused on improved data handling—specifically, real-time text replacement. The current codebase is stable but offers only limited, batch-style substitution; I now want replacements to happen on the fly as data moves through the system so downstream processes always receive the updated stream without noticeable latency.
The job involves diving into the existing OTP supervision tree, identifying the modules that touch the data pipeline, and rewriting or adding functions so dynamic replacement rules can be injected, updated, and applied immediately. Concurrency, hot-code upgrades, and fault tolerance all matter here, so I am looking for someone genuinely comfortable with gen_server, gen_stage (where applicable), and ETS/Mnesia for quick look-ups.
Deliverables I expect:
• Updated .erl/.hrl files with the new replacement logic integrated
• Unit tests that clearly demonstrate correct behaviour under load
• Brief deployment notes covering any schema or config changes
I keep the source on Git and use rebar3 for builds; push requests and concise commit messages will be part of the review. This is purely a feature addition—no bug fixing or cosmetic refactors required—so you can stay laser-focused on performance and correctness. If this sounds like your kind of challenge, let’s talk details.
The job involves diving into the existing OTP supervision tree, identifying the modules that touch the data pipeline, and rewriting or adding functions so dynamic replacement rules can be injected, updated, and applied immediately. Concurrency, hot-code upgrades, and fault tolerance all matter here, so I am looking for someone genuinely comfortable with gen_server, gen_stage (where applicable), and ETS/Mnesia for quick look-ups.
Deliverables I expect:
• Updated .erl/.hrl files with the new replacement logic integrated
• Unit tests that clearly demonstrate correct behaviour under load
• Brief deployment notes covering any schema or config changes
I keep the source on Git and use rebar3 for builds; push requests and concise commit messages will be part of the review. This is purely a feature addition—no bug fixing or cosmetic refactors required—so you can stay laser-focused on performance and correctness. If this sounds like your kind of challenge, let’s talk details.