In programming we decompose big things into small, manageable chunks. In algorithms, we solve a small problem, and then use recursion or iteration to solve more complex problems. In software development, we create methods, and interfaces, and classes, and packages with the objective of being more efficient, and letting our code be more maintainable, manageable…so that a change in one part does not require a cascading change in other parts of the application.
Yet, we deploy as a monolith. All the packages run in the same JVM, in the same process. Classic example of this is the Java EE container, where all the wars, jars, and ears are deployed in the same JVM. In this page, I am jotting my notes on micro services, and a high level framework for designing micro services.
Often there would be a need for an ISP to prioritize or delay a set of packets. Sometimes this is done to enhance the user experience, and other times to up-sell a set of their services. For example, VoIP & HTTP data must get priority over FTP & P2P data, so that the user experience is good. ISP’s might want to set hard limits on some applications, for example no more than 5 mbps for FTP data. Some ISP’s would offer differentiated services, and up-sell higher bandwidth for online gaming to their subscribers. And almost always, the ISP’s would limit the bandwidth on a per client basis, based upon the plan sold to the subscriber.Read More