Skip to main content

0G.GhostShip Model

trydoforOriginalWingsGodModelAbout 1 min

0G.GhostShip Model

WingsBoot basic architectural idea is to do the model vertically and overlay the function horizontally. The codename has bean called CruiseModel, later in the Dota series, changed to GhostShip, more wings a little

0G.1.Aboard to the sea (GoSea)

Chinglish says, Go And Sea, Let's Me See Sea

In my experience with startups, almost everything is lacking and nothing is certain. The entire team is in the same boat, trying to survive and explore at sea, while trying not to get lost or sink.

0G.2.Vertical Model (Floor)

The business architecture and model, program architecture and model, have strict boundaries and dependency requirements. Usually, from the bottom to the top like a building floor, they are called Floor-N (N is a natural number)

2a.Unidirectional Call, Avoid Crossing

Usually, the upper layer can invoke the same layer or the lower layer, but not vice versa. For example, in the structure of Dao/Ser/Mvc:

  • Service can call Dao and Service, but should avoid calling back. SHOULD
  • Controller can call Service, but must not be called back. MUST
  • Controller should not call Dao. SHOULD

2b.Unidirectional Flow, Event Sourcing

Data flow and business flow require unidirectional flow. In the case of turbulent flow, unambiguous events should be propagated and tracked.

For example, data flows from the bottom up, while business flows from the top down.

0G.3.Horizontal Functions (Layer)

Functions or modules can combine, inherit, overlay or filter to provide appropriate services to the outside world. Usually, from the inside to the outside, they are called Layer-N (N is a natural number)

  • messages and properties use overlay
  • Servlet and Filter use combine and filter
  • Authn and Authz use combine and inherit

3a.Clear Boundary, Reduce Coupling

Based on business requirements within the domain, define clear boundaries, such as data models, functional modules, etc.

3b.Single Responsibility, Each to Its Own

For a given event, focus on a single task, for a data flow, handle only the current state.

0G.4.Basic Model

  • Presentation - present and interpret user commands, eg. app, web
  • Application - validate and transform data, eg. controller, api
  • Domain/Biz - handle biz concept and logic, eg. service, dao
  • Infrastructure - biz-independent server, eg. db, cache
▲
│ Floor of Abstraction
├──────────────┐
│ Presentation │
├──────────────┴──┬────────┐
│ Application     │ LayerA │
├─────────────────┴──┬─────┴───┬────────┐
│ Domain/Biz         │  LayerB │ LayerD │
├────────────────────┴──┬──────┴─┬──────┴─┬────────┐
│ Infrastructure        │ Layer1 │ Layer2 │ Layer3 │
└───────────────────────┴────────┴────────┴────────┴─────▶
                    Layer of Complexity