hhow09/blog-old

hhow09.github.io

This website is built using Docusaurus 2, a modern static website generator.

Installation

yarn install

Local Development

yarn start

This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.

Build

yarn build

This command generates static content into the build directory and can be served using any static contents hosting service.

Deployment

• deployment is done by github actions
• Follow the documentation Triggering deployment with GitHub Actions to setup .github/workflows/source.yml
• generate private key ~/.ssh/id_rsa and public key ~/.ssh/id_rsa.pub at local
• pbcopy < ~/.ssh/id_rsa.pub to copy public key
• add public key in Account settings: SSH keys to allow push
• add public key in repo settings: deploy keys
• pbcopy < ~/.ssh/id_rsa to copy private key
• set the secrete variable GH_PAGES_DEPLOY in repo: Actions secrets

blog-old's Issues

Micro Service

Videos

• Mastering Chaos - A Netflix Guide to Microservices

Terms

Self Provisioning

• Self-provisioning, commonly known as the cloud self-service, is a feature among many cloud service providers which allows their end users to provision resources by themselves, and set up or launch a service or application without the intervention of dedicated IT personnel or the service providers themselves. This gives users greater freedom in using services within the bounds set by the provider.
• Self-provisioning can go further than just smarter build automation

Bounded context

• the coupling of a component and its data without many other dependencies — decreasing the need to share components

Micro Services v.s. SOA

• Data model and database per service v.s. Global data model and shared databases
• Smaller service v.s. Larger monolithic application

Topics

Service v.s. Library

• library reduce code duplication, however, whenever library change any service including that needs rebuild and redeploy
• You should strive to use libraries for functionality that’s unlikely to change. For example, a generic Money class that can be shared among different services

Dependency

Cascading Failure

• need some fallback logic: ex. Netflix/Hystrix
• fault injection testing
• define critical services

Client side library

• client side library may return back to monolith problems: process and services hides behind library consuming resources.
• Library vs. bare bone REST call ?

Scaling

CAP Theorem

Auto Scaling

Reference

• Is Microservices the best answer for all Software Problems? Is it still valid in the Post-Covid world?
• The Self Provisioning Runtime
• Cloud Operating Systems

Webpack 5 - Module Federation

Webpack 5 - Module Federation

• It is a webpack 5 feature
• It allows you to dynamically load another JS bundle from another package (from remote).
• It allows you to build then expose a entryPoint to allow others to fetch bundled JS.

Introduction

• Introducing Module Federation in Webpack 5
• Webpack 5 Module Federation — Stitching two simple bundles together

Use Case: Module Federation as a solution of Micro Frontend

• For micro frontend, each frontend project can has its own host/server, framework, render logic ,deploy cycle
• Before module federation, page container can use 1) iframe 2) client side JS module 3) web component to assemble those micro frontend projects into pages. They do not include Webpack process.
• Nowadays most of the frontend framework goes through Webpack process, with this new feature we can

Some concern

1. reliability: when fetch bundle from remote host, you need to ensure that host is live.
2. performance: fetch bundle from remote host may be slow.
3. complexity: need to hard-coded / manage remote host url in the html
4. It's client side rendering, not compatible with SSR.

Example

• https://github.com/kylemocode/micro-frontends-example

Use Case: Module Federation as a substitute of sharing component

• different apps under same host, app A can share a component with app B