Hey !! I am actively looking for a remote full time engineer role centered around Backend, Infra or Full Stack.
I have been building and doing backend related paid gigs, projects and also I love to write about terminologies and system around backend and infrastructure. I am very much equipped with Golang and many different tech stacks like PostgreSQL, Redis, Nginx which helps build for the scale and large systems
Few Projects to consider
>> OpenTelemetry Bridge Sidecar : Its transparent reverse proxy that injects distributed tracing into HTTP applications without having some major code changes. Backpressure layer for tcp/upd streams : it adjusts the data flow rate between services based on both network conditions something like RTT and packet loss
Implemented 2 phase commit paper purely in golang
>> Wrote a DAG benchmarking tool something like Netflix/P2pLabs repository wrote different IPLDs and benchmarked their performances
>> Built Analytics Engine using Go, Graphana, Redis and docker
>> Apizy, a visual API builder . One can connect build api's in raw nodeJs and expressJs by just dragging and dropping the code blocks
There are many projects like this which was built with the motive to learn something new and to push me from my comfortable zone. If your team is looking for someone who is building in the same space and you think we are aligning I’d love to connect and talk more about my past work. My DMs are open
wrote a simple and lightweight progressive jpeg protocol for streaming services and multi scan image deliverables in Clojure
- supports configurable scan scripts
- only uses java imageIO
time to hit the dockerimages and try to optimize the image as low as possible >40mb is what I am targeting
Take what I say with a grain of salt, though :D
after spinning up a db in a container I would say
pull up a decently big dataset like StackExchange dumps and start poking into it
> test out some interesting queries
> try to build a buffer pool
> indexes
> WAL intro and then go for the wal internals
> then read some code from duckdb and sqlite and try to implement it on your project
> then benchmark single threaded and concurrent execution
But most of these things won't get used in production or many of us won't be working at such core stuffs until we hit some serious engineering post as senior engineer or L3 engineer
these are just for fun and benchmarking your knowledge graph nothing more than this
@kunalgoesbyken if you dig enough you will get to know that psql works on pull based iterator model and morsels work like push based pipelines
i don't think so its needed their
Favourite things to do is go find out how different databases are implementing terms from research papers to their main production
For now it's duckdb and morsel driven parallelism
database is an interesting rabbit hole to get into, at very first 20 hours of databasemaxxing you will find about LSM trees, WAL, how a db manages buffer pools and everything around lock free data structures
imo the real interesting part of the rabbit hole starts with finding how concurrency changes the shape of an execution engine and how far can you push locality
request everyone to maintain a diary full of logged rabbit holes you have ever explored
wanna play a game but it doesn't exist yet?
meet dreamsy: an all in one open source engine to bring your imagination to life. dream up games, build them with ai, and play them exactly how you imagined. turn your wildest game ideas into something you can actually play.