[Intro] Starting my Own Blog



Never thought I'd start my own blog. Thought it was time-consuming and only what show-offs would be doing, but I realized that I have many notes myself, and starting a blog will, in a way, force me to organize my notes better since I know anyone might be reading this.

Comments

Post a Comment

Popular posts from this blog

[Distributed File System] Introduction to Ceph

Image
Ceph 1. Preface This blog focuses on the paper, Ceph: A Scalable High-Performance Distributed File System. Note that this paper was written in 2006 and the implementation of it might be different from what is described in the paper (and here). Details on more in-depth concepts, such as CRUSH, Metadata Server and Object Storage Device cluster are skipped in this blog (might include it in future blogs). 2. Introduction Ceph is distributed file system that builds on several philosophical and design principles. 2.1. Philosophical Principles Starting with philosophical principles, Ceph is open source . This means that it is free to use, free from being vendor specific, free to modify and free to share. Secondly, Ceph is Community-focused means that anybody can decide future step, anybody can fix a bug and update the documentation because all of us as a whole are smarter than some of us, so we can end up with better product. 2.2. Design Principles First, Ceph is Scalable . ...
Read more

[Java] Servlets

A servlet is a class which responds to a particular type of network request (most commonly an HTTP request). Servlets are usually used to implement web applications. Servlets run in a servlet container, which handles the network side (eg. parsing HTTP request, connection handling.etc). One of the best-known source servlet containers is Tomcat. Flow of Request Client sends HTTP request to Web Server Web Server forwards HTTP request to Web Container Web Container converts request into valid request object (because servlet cannot understand HTTP; only understands objects) Web container spins a thread for each request. All the business logic goes inside doGet() and doPost() methods inside the servlets. Servlet builds a Java response object and sends it to the container. It converts that to HTTP response again and send it to the client.
Read more

[Node.js] Web Architecture Design

1) Traditional Web Application Processing Model - Multi-Threaded Request-Response Any Web Application developed without NodeJS typically follows the "Multi-Threaded Request-Response model" (or just "Request/Response Model"). This differs from the NodeJS way in that it uses multiple threads to handle concurrent client requests. Under the hood, server waits in infinite loop and creates one thread per client request. If the server gets many client requests that require long blocking I/O operations, then more threads become 'busy'. As a result, the remaining clients requests have to wait longer due to core-thread resources. 1.1) Detailed Flow Ahead of time: Web Server is in infinite loop and waiting for Client Incoming Requests. Web Server internally maintains a Limited Thread pool to provide services to Client Requests. Once threads free up in thread pool, server pick up those threads and assign them to remaining client requests. Clients send re...
Read more