Hacker Newsnew | past | comments | ask | show | jobs | submit | animesh371g's commentslogin

1) In-memory execution engine - It uses Redis as the core execution engine and decouples it from the durability layer.

2) Transaction log - It forms the backbone of the durability layer. It handles data replication, leader election, and data recovery.

3) Off-box recovery - It offloads recovery of failed nodes to ephemeral clusters and S3 for performance improvements.


The adoption would be gradual and few years down the line, it would be QUIC. The same was true for HTTP/1 and HTTP/2.


There is no Level 8 as such. Everything happens at the application level i.e Level 7.


I think they meant the person and who they are as "level 8".

In other words, if you have this communication protocol, when it reaches level 8 the message might not be delivered or be misinterpreted based on the person. For example in this thread with some people seeing this as racist, some people see it as nothing.


Level 8 is a joking way of designating the user. Also refered as "the layer between the keyboard and the screen".


Between keyboard and chair, surely?


PEBCAK, "Problem exists between chair and keyboard"


Best opportunity to contribute to a new NPM package for QUIC/HTTP3


Yes, that is what QUIC has done.


QUIC doesn't have a handshake which is another reason for it being fast


The article says this repeatedly, but it's also wrong about that. QUIC doesn't use exactly the same three-way handshake at the beginning of the session -- but it uses a handshake that lasts at least 3 packets.

https://quic.xargs.org/


The paper discusses the fundamental problem with microservices architecture. It solves the fundamental problem by proposing a technique to develop monoliths with logical boundaries.


The post explains in simple words what Vector databases are and their applications.


Technical concepts, distributed systems explained in simple words - https://engineeringatscale.substack.com/ https://medium.com/@animeshgaitonde


I have written an article on Non-Functional Requirements in System Design. I have condensed a decade of an experience and explained each quality attribute with an example. Let me know your thoughts on this.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: