Embedded & Distributed System

The  Architecting on AWS course  has 13 modules (as marked as  mx  below). Each module builds on previous one, either adding functionality or improving the architecture characteristics laid out by the  5 pillar well-architected framework . Below is the summary of each modules, and notice how they build on progressively. As an exercise, following on the text description, you can draw out an "well-architected" architecture diagram for an typical 3 tie application. The corresponding components and concepts (show as  components/concept  below ) involved are fundamentals for building IT infrastructure on AWS services. Mastering them is critical for building a "best-practices-followed" cloud solution, or passing your AWS exam, for that matter. use  s3  to host static website create an  ec2  and mount  efs  ( m3  add computer layer) add  rds  primary and allow ec2 connection ( m4  adding database layer) segregate the 3 tiers into different  subset s, use  internet gateway

I was organising and cleaning up my Google Drive and found this pdf file about Android Graphic System I wrote back in 2014. It is 62 pages. I will never be able to update it and make it better and/or up to date, since I have moved to other area recently. I'm not not sure how useful it is now, but anyway I will share it here. https://drive.google.com/file/d/0BxzOKllGjbpdOVd4UlpOWUlxM2c/view?usp=sharing

The  index page of understand container    had a very good page view after being created. Then I was thinking if anyone would be interested in a more polished, extended, and easier to read version. So I started a book called "understand container".  Let me know if you will be interested in the work by subscribing  here  and I'll send the first draft version which will include all the 8 articles here. The free subscription will end at 31th, Oct, 2018. * Remember to click  " Share email with author (optional)", so that I can send the book to your email directly. 

This is an index page to a series of 8 articles on container implementation. OCI Specification Linux Namespaces Linux Cgroup Linux Capability Mount and Jail User and Root Network and Hook Network and CNI Update: This page has a very good page view after being created. Then I was thinking if anyone would be interested in a more polished, extended, and easier to read version. So I started a book called "understand container".  Let me know if you will be interested in the work by subscribing here  and I'll send the first draft version which will include all the 8 articles here. The free subscription will end at 31th, Oct, 2018. * Remember to click " Share email with author (optional)", so that I can send the book to your email directly.  Cheers,

Controllers  in k8s assumes the same role and responsibility as the Controller in the classic  Model-View-Controller （whereras the  Model  are the various API objects stored in the  etcd ） architecture. What's kind of unique about the controller in k8s is will  constantly  reconcile the system desired state to current state, not just a one time task.

The most known job of a container orchestration is to "Assign Pods to Nodes", or so-called  scheduling . If all the Pods and Nodes are the same, it becomes a trivial problem to solve - a round robin policy would do the job. In practice, However, Pods have different resource requirements, and less obvious that the nodes may have different capabilities - thinking machines purchased 5 years ago and brand new ones.

In the last article, we said there was a  statetore  in the master node; in practice, it is implemented using  etcd .  etcd  is open source distributed key-value store (from coreOs) using the  raft  consensus algorithm. You can find a good introduction of etcd  here .  k8s  use  etcd  to store all the cluster information and is the only stateful component in the whole k8s (we don't count in the stateful components of the application itself).