epelesis

4 ms·

1.
by epelesis 2y ago
Yep Vite is the way to go, especially if it's a static site. While server side react frameworks like Next may technically support static sites, it feels like an afterthought and IMO it adds too much unnecessary complexity. Here's
2.
by epelesis 4y ago
Here are some popular papers: https://github.com/rxin/db-readings Once you finish the major papers, CMU has a ton of talks from more recent database research projects: https://db.cs.cmu.edu/seminar2020&
3.
by epelesis 4y ago
I agree, Silicon Valley (e.g. Mountain View, Santa Clara) is absolutely full of tech talent but the average engineer is mostly interested in and optimizing for work in big tech companies. SF tends to skew towards smaller tech companies, alo
4.
by epelesis 4y ago
BW Trees are pretty neat [1][2]. Typically BTrees in database engines need latches to prevent concurrent writes messing up the tree but BW Trees conveniently sidestep that requirement by appending all node updates to a linked list (called a
5.
by epelesis 4y ago
IMO if you're working on any non-trivial backend project, then you're already a "distributed systems engineer". Distributed systems problems are everywhere in the software world if you need to manage state and consistenc
6.
by epelesis 4y ago
One reason this is not feasible is that K8s is not designed for secure multitenancy, so for every tenant, you'll need to spin up an entire K8s control plane, which includes a database and several services - this is what's driving
7.
by epelesis 4y ago
I work at a somewhat well-known unicorn in the data space that has been using this architecture for a while. In fact I'd wager that any (non-cloud-provider) company that provides any significant amount of compute or storage in their pr
8.
by epelesis 5y ago
You might be interested in this table table mapping internal tools/technology at Google to public equivalents: https://github.com/jhuangtw/xg2xg
9.
by epelesis 5y ago
I've had my eye on this autoscaler for a while now, has anyone had experience running it in production with a large rate of node churn? I think combining the scheduler and the autoscaler into a single entity makes a lot of sense, both
10.
by epelesis 5y ago
The keyword you're looking for here is Operator [1]. Kubernetes Operators are custom resources (e.g. Database, Load Balancer, ACME Certificate Entry) that manage themselves via a reconciliation loop. If you're looking for a specif
11.
by epelesis 6y ago
Since no one has mentioned it so far, I'll go ahead and link a very insightful paper that the creator of Erlang actually wrote about how fault tolerance from the actor model make concurrent programming a breeze: https://erla
12.
by epelesis 6y ago
The guy [1] who runs this project is super nice, about a year ago I was working on my own Rust based VM and he dropped in with a couple of helpful tips and ideas. [1]: https://github.com/lpil
13.
The Death of Hype: What's Next for Scala(lihaoyi.com)
13 points by epelesis 6y ago|2 comments
14.
by epelesis 7y ago
I'm taking Jeff's 473 class right now and if you like his writing style, all of his lectures for both algorithms classes he teaches are online as videos - it can be a good companion to the textbook if you want worked examples. [my