alco
Joined 13 years ago
Joined 13 years ago
Remote: Yes
Willing to relocate: No
Technologies: Elixir, Go, TypeScript, Postgres, SQLite, Docker, AWS, sync engine, containers, distributed systems
Resume: https://sholik.dev/resume/
Email: [email protected]
I build data infrastructure: sync engines, durable streams, and backend systems that must stay correct through load, restarts, and failure. I have expert-level, hands-on knowledge of Postgres logical replication and of the BEAM VM's concurrency and memory model. I'm looking for a remote senior software engineer role in distributed systems, replication, storage, AI agent infrastructure, or performance engineering. I'm deepest in Elixir/OTP and Postgres, productive in Go and TypeScript, and more interested in hard systems problems than any particular language.
> Firebase Data Connect provides you with a local emulator for end-to-end prototyping as well as continuous integration and continuous deployment (CI/CD) flows
Developers at Google have chosen PGLite for those qualities so that users of Firebase Data Connect had better CI/CD workflows. It wouldn't be fair to say this is an insignificant use case.
Location: Kyiv, Ukraine
Remote: Yes
Willing to relocate: planning a move to UTC time zone within the EU
Technologies: Elixir, Go, TypeScript, Python, AWS, GCP, Docker, Kubernetes, PostgreSQL, RabbitMQ
Résumé/CV: https://www.dropbox.com/s/6njitiijrb0gs37/Oleksii%20Sholik%20Resume.pdf?dl=0
Email: [email protected]
Hi, my name is Oleksii. Having worked as a backend engineer for the past almost 10 years, I'm an expert in Elixir/OTP and PostgreSQL, skilled in Go, AWS, and Kubernetes. Looking for new challenges in distributed computing, global data consistency, high scalability, and observability.I actively contributed to the Elixir programming language between 2012 and 2016, developing UX improvements for IEx (colors, history, .iex.exs), implementing core functions in Enum, List, OptionParser, String, System modules.
Chris McCord's keynote was also really interesting, he explained how he implemented Phoenix Presence using a certain kind of CRDT.
And for some laughs I recommend watching Gary Rennie's funny story about achieving 2 million clients simultaneously connected to a single Phoenix server.
The fundamental difference of content-addressed networks is their resiliency in the face a single authority trying to track down all of the sources that have copies of the content.
Even though IPFS is still in its infancy, one of its primary goals is to solve the problem of content suddenly disappearing from the Internet.
Could you please add a field on the site where I could paste the URL of a webpage? That would work for me as a workaround to using the extension.
http://munificent.github.io/wren/qa.html#why-did-you-create-...
By "programming model" I mean things like immutability, concurrency, fault-tolerance, and the way you design systems with OTP.