[图解]领域驱动设计伪创新-为什么互联网是重灾区-01

0
00:00:00,840 --> 00:00:03,270
今天我们来说一下

1
00:00:03,650 --> 00:00:06,255
领域驱动设计伪创新

2
00:00:06,255 --> 00:00:08,860
为什么互联网是重灾区

3
00:00:09,500 --> 00:00:12,610
这个我们分几个视频来讲

4
00:00:15,620 --> 00:00:17,550
那这是来自于

5
00:00:18,270 --> 00:00:20,920
以前的一个答疑

6
00:00:21,200 --> 00:00:23,240
这个同学问

7
00:00:23,550 --> 00:00:26,171
看我发的软件方法

8
00:00:26,171 --> 00:00:28,315
第八章,有一篇文章

9
00:00:28,315 --> 00:00:29,745
有一个调查

10
00:00:29,745 --> 00:00:30,937
调查什么呀

11
00:00:30,937 --> 00:00:33,081
提到几个类

12
00:00:33,081 --> 00:00:34,750
然后他就发现

13
00:00:36,970 --> 00:00:38,900
谈论DDD的

14
00:00:39,820 --> 00:00:40,103


15
00:00:40,103 --> 00:00:43,500
除了tw公司的人

16
00:00:45,260 --> 00:00:48,580
还有呢,大部分是互联网公司的

17
00:00:49,740 --> 00:00:52,440
而且都会提到微服务等等

18
00:00:53,330 --> 00:00:54,332
他问的问题

19
00:00:54,332 --> 00:00:55,670
是不是互联网

20
00:00:56,010 --> 00:00:57,690
更适合用DDD

21
00:01:02,190 --> 00:01:02,434


22
00:01:02,434 --> 00:01:04,631
那个调查是这样的

23
00:01:04,631 --> 00:01:08,050
就是写在软件方法那个书上

24
00:01:09,350 --> 00:01:12,438
你看过的以领域驱动设计为名的文章

25
00:01:12,438 --> 00:01:13,790
里面有几个领域类

26
00:01:14,100 --> 00:01:14,325


27
00:01:14,325 --> 00:01:16,580
一般都是五个以下的

28
00:01:17,870 --> 00:01:18,610
注意

29
00:01:18,890 --> 00:01:20,120
领域类

30
00:01:20,400 --> 00:01:20,575


31
00:01:20,575 --> 00:01:21,801
订单算一个

32
00:01:21,801 --> 00:01:22,853
你不能说,订单

33
00:01:22,853 --> 00:01:24,255
然后这边有个订单工厂

34
00:01:24,255 --> 00:01:26,007
那边有个订单仓储

35
00:01:26,007 --> 00:01:27,760
然后订单service,不是

36
00:01:28,050 --> 00:01:29,575
不是这样的

37
00:01:29,575 --> 00:01:30,490


38
00:01:30,770 --> 00:01:32,128
就一个类叫订单

39
00:01:32,128 --> 00:01:33,875
然后周围围了一圈

40
00:01:33,875 --> 00:01:35,427
实际上就

41
00:01:35,427 --> 00:01:36,980
只有一个订单

42
00:01:42,680 --> 00:01:46,056
那么这个呢,我们要分几点来谈才行

43
00:01:46,056 --> 00:01:50,700
因为要讲的话就会扯到很多其他的问题了

44
00:01:51,660 --> 00:01:53,170
我分几点来谈

45
00:01:55,240 --> 00:01:55,490


46
00:01:55,490 --> 00:01:58,500
第一个巫医特别适合治感冒

47
00:01:59,010 --> 00:01:59,287


48
00:01:59,287 --> 00:02:01,230
这个就是为什么

49
00:02:01,750 --> 00:02:05,660
有些DDD实践为什么喜欢挑互联网来下嘴

50
00:02:07,950 --> 00:02:12,660
那下面就是谈互联网的一些所谓的建模经验的问题了

51
00:02:13,720 --> 00:02:15,368
包括并存不等于因果

52
00:02:15,368 --> 00:02:18,390
纳税不是盈利的原因

53
00:02:19,120 --> 00:02:20,740
最后我们再谈一谈

54
00:02:21,130 --> 00:02:24,610
什么样的人介绍的经验是可以借鉴的

0
00:00:01,560 --> 00:00:03,730
第一个,我们说一下

1
00:00:04,050 --> 00:00:08,400
为什么DDD实践喜欢挑互联网下嘴

2
00:00:11,890 --> 00:00:14,300
互联网,这里也是加引号的

3
00:00:14,300 --> 00:00:15,746
泛指一种什么

4
00:00:15,746 --> 00:00:16,470
就是说

5
00:00:17,450 --> 00:00:18,690
它功能

6
00:00:19,890 --> 00:00:21,170
很简单

7
00:00:21,480 --> 00:00:23,310
但是用的人特别多

8
00:00:24,270 --> 00:00:27,190
这两个是相辅相成的

9
00:00:27,470 --> 00:00:29,030
我们后面会提到

10
00:00:30,540 --> 00:00:32,102
那之前的话

11
00:00:32,102 --> 00:00:34,707
软件是重功能的

12
00:00:34,707 --> 00:00:36,270
就是功能很多

13
00:00:38,920 --> 00:00:41,218
但是,互联网到来之后呢

14
00:00:41,218 --> 00:00:42,890
就会带来一种什么

15
00:00:43,520 --> 00:00:45,070
功能特别少

16
00:00:45,640 --> 00:00:46,560
但是

17
00:00:47,130 --> 00:00:48,600
用的人特别多

18
00:00:49,190 --> 00:00:49,407


19
00:00:49,407 --> 00:00:52,230
其中最典型的就是hotmail

0
00:00:00,340 --> 00:00:03,100
hotmail就是一个电子邮箱嘛

1
00:00:03,100 --> 00:00:03,790
对不对

2
00:00:05,160 --> 00:00:07,200
但是因为它是免费的

3
00:00:08,650 --> 00:00:12,120
所以呢,你看,1996年提出来之后

4
00:00:12,430 --> 00:00:15,303
一年半时间就有1200万的用户

5
00:00:15,303 --> 00:00:17,410
那是1996年的时代

6
00:00:17,690 --> 00:00:18,079
不是

7
00:00:18,079 --> 00:00:19,830
现在的1200万

8
00:00:20,170 --> 00:00:21,890
1996年

9
00:00:24,260 --> 00:00:26,165
然后被微软收购

10
00:00:26,165 --> 00:00:26,880
现在

11
00:00:27,910 --> 00:00:29,338
还存在呢

12
00:00:29,338 --> 00:00:29,950
对不对

13
00:00:31,080 --> 00:00:32,460
hotmail是什么

14
00:00:32,740 --> 00:00:34,900
就是一个基于web的

15
00:00:35,280 --> 00:00:36,680
电子邮件系统

16
00:00:37,390 --> 00:00:38,810
这个东西

17
00:00:40,150 --> 00:00:41,520
大把的人会做

18
00:00:41,520 --> 00:00:42,205
对不对

19
00:00:42,205 --> 00:00:45,630
而且呢,应该有现成很多代码可以抄

20
00:00:47,670 --> 00:00:49,470
问题是,你会做有啥用

21
00:00:51,030 --> 00:00:52,670
你有钱买服务器吗

22
00:00:53,940 --> 00:00:54,933
有钱去烧吗

23
00:00:54,933 --> 00:00:56,523
有钱去做广告吗

24
00:00:56,523 --> 00:00:57,120
对不对

25
00:01:00,820 --> 00:01:01,810
所以呢

26
00:01:02,450 --> 00:01:07,075
很多的开发人员,就跑到这样的公司去了

27
00:01:07,075 --> 00:01:09,850
去开发或者维护这样的系统

28
00:01:10,870 --> 00:01:12,170
这时候显然

29
00:01:14,190 --> 00:01:17,620
这里面需要剖析的领域逻辑

30
00:01:19,320 --> 00:01:21,450
是没有什么太复杂的

31
00:01:21,790 --> 00:01:23,346
即使有复杂的

32
00:01:23,346 --> 00:01:25,680
也已经被人剖析过很多遍了

33
00:01:25,680 --> 00:01:26,070
因为

34
00:01:27,190 --> 00:01:29,202
这些都是一些基础设施

35
00:01:29,202 --> 00:01:30,007


36
00:01:30,007 --> 00:01:31,215
而且大把的

37
00:01:31,215 --> 00:01:32,020
可以借鉴的

0
00:00:00,590 --> 00:00:02,640
那么,对于这样的系统

1
00:00:03,650 --> 00:00:06,330
你用什么开发方法来开发

2
00:00:07,490 --> 00:00:08,983
是无所谓的

3
00:00:08,983 --> 00:00:09,730
对不对

4
00:00:11,000 --> 00:00:11,241


5
00:00:11,241 --> 00:00:13,659
你用很严密的建模推导

6
00:00:13,659 --> 00:00:16,077
你拍脑袋开发,趴着开发

7
00:00:16,077 --> 00:00:17,770
躺着开发,都可以

8
00:00:19,820 --> 00:00:21,310
那既然如此

9
00:00:22,730 --> 00:00:23,680
那我

10
00:00:24,050 --> 00:00:26,590
上一个伪创新的开发方法

11
00:00:27,560 --> 00:00:31,646
也并不妨碍这个网站本身成功还是不成功

12
00:00:31,646 --> 00:00:34,370
因为这个网站成功还是失败

13
00:00:36,050 --> 00:00:37,619
要素根本就不在于

14
00:00:37,619 --> 00:00:39,385
你用什么方法开发

15
00:00:39,385 --> 00:00:41,740
或者说,这个东西会不会开发

16
00:00:41,740 --> 00:00:43,310
开发得怎么样

17
00:00:43,310 --> 00:00:45,076
其实这个都不是问题

18
00:00:45,076 --> 00:00:46,450
因为这个很简单

19
00:00:49,860 --> 00:00:52,710
所以呢,很多伪创新就盯住了

20
00:00:52,990 --> 00:00:55,650
这样的一种系统

21
00:00:56,270 --> 00:00:57,840
那不只是说领域驱动设计

22
00:00:59,920 --> 00:01:04,025
包括敏捷等等

23
00:01:04,025 --> 00:01:05,920
都是挑互联网

24
00:01:06,810 --> 00:01:08,890
喜欢挑互联网来下嘴

25
00:01:11,270 --> 00:01:13,905
以前经常有人跟我说

26
00:01:13,905 --> 00:01:17,260
我以前经常批评敏捷嘛

27
00:01:17,630 --> 00:01:18,308
然后呢

28
00:01:18,308 --> 00:01:19,665
就有人跟我说

29
00:01:19,665 --> 00:01:20,570
潘老师

30
00:01:21,280 --> 00:01:22,045
敏捷

31
00:01:22,045 --> 00:01:23,830
做别的不好说

32
00:01:24,140 --> 00:01:26,360
但是对互联网很管用

33
00:01:27,570 --> 00:01:28,810
当然管用了

34
00:01:28,810 --> 00:01:29,430
对不对

35
00:01:31,200 --> 00:01:33,350
就像这里有一杯白开水

36
00:01:34,350 --> 00:01:35,090


37
00:01:36,170 --> 00:01:38,341
但是我说它不是白开水

38
00:01:38,341 --> 00:01:39,920
它是一瓶灵丹妙药

39
00:01:40,520 --> 00:01:41,810
这个药

40
00:01:42,090 --> 00:01:43,420
癌症治不了

41
00:01:44,220 --> 00:01:45,652
这个我承认

42
00:01:45,652 --> 00:01:46,845
我很诚实

43
00:01:46,845 --> 00:01:48,516
癌症是治不了的

44
00:01:48,516 --> 00:01:49,710
但是治感冒

45
00:01:50,400 --> 00:01:51,240
很管用

46
00:01:51,240 --> 00:01:52,080
你不信

47
00:01:53,200 --> 00:01:54,324
等你感冒的时候

48
00:01:54,324 --> 00:01:55,610
你把这个水给喝了

49
00:01:56,050 --> 00:01:58,360
五天之内我包你好

50
00:01:58,640 --> 00:01:59,436
好了吗

51
00:01:59,436 --> 00:02:00,764
确实好了

52
00:02:00,764 --> 00:02:01,561
为什么

53
00:02:01,561 --> 00:02:04,482
因为感冒本身,你喝白开水

54
00:02:04,482 --> 00:02:05,810
喝可乐,喝粥

55
00:02:06,540 --> 00:02:06,826


56
00:02:06,826 --> 00:02:08,256
都可以

57
00:02:08,256 --> 00:02:08,542


58
00:02:08,542 --> 00:02:10,830
跟那个没有关系的

59
00:02:11,500 --> 00:02:13,340
那既然如此的话

60
00:02:13,620 --> 00:02:14,400
他就

61
00:02:15,720 --> 00:02:17,615
以这个为借口

62
00:02:17,615 --> 00:02:18,970
就把白开水

63
00:02:19,250 --> 00:02:19,634
当成

64
00:02:19,634 --> 00:02:21,750
治感冒的灵药卖给别人了

65
00:02:23,210 --> 00:02:23,428


66
00:02:23,428 --> 00:02:24,740
就跟巫医

67
00:02:25,900 --> 00:02:27,102
治感冒一样

68
00:02:27,102 --> 00:02:27,823
对不对

69
00:02:27,823 --> 00:02:29,025
你感冒了,好

70
00:02:29,025 --> 00:02:29,746
没关系

71
00:02:29,746 --> 00:02:31,670
你躺在供桌上

72
00:02:32,180 --> 00:02:32,546


73
00:02:32,546 --> 00:02:34,010
我找英叔

74
00:02:34,290 --> 00:02:35,790
给你做法

75
00:02:37,520 --> 00:02:38,855
绕着你

76
00:02:38,855 --> 00:02:40,525
脚踏八卦阵

77
00:02:40,525 --> 00:02:43,530
绕着你走八八六十四圈

78
00:02:43,810 --> 00:02:46,632
你看,他也是有一套方法学的

79
00:02:46,632 --> 00:02:46,850


80
00:02:47,640 --> 00:02:49,700
跟那个事件风暴

81
00:02:49,700 --> 00:02:52,997
通用语言这些一样的

82
00:02:52,997 --> 00:02:55,470
他也是编造了一套方法学

83
00:02:55,780 --> 00:02:56,370


84
00:02:57,290 --> 00:02:57,533

85
00:02:57,533 --> 00:02:59,235
他做法做完之后

86
00:02:59,235 --> 00:03:01,181
他就跟那个病人说

87
00:03:01,181 --> 00:03:03,370
你回去躺几天就好了

88
00:03:04,750 --> 00:03:05,720


89
00:03:05,720 --> 00:03:06,690
确实

90
00:03:07,030 --> 00:03:07,820
好了

91
00:03:09,820 --> 00:03:12,458
然后,他就把功劳都归到他的身上

92
00:03:12,458 --> 00:03:13,690
你看,我这套方法

93
00:03:14,000 --> 00:03:15,390
非常适合

94
00:03:16,540 --> 00:03:20,090
互联网,非常适合治感冒,一样的

相关推荐

  1. 领域驱动设计战术设计

    2024-04-28 13:22:01       22 阅读
  2. DDD领域驱动设计(六)

    2024-04-28 13:22:01       39 阅读

最近更新

  1. TCP协议是安全的吗?

    2024-04-28 13:22:01       18 阅读
  2. 阿里云服务器执行yum,一直下载docker-ce-stable失败

    2024-04-28 13:22:01       19 阅读
  3. 【Python教程】压缩PDF文件大小

    2024-04-28 13:22:01       19 阅读
  4. 通过文章id递归查询所有评论(xml)

    2024-04-28 13:22:01       20 阅读

热门阅读

  1. 初次运行TinyWebServer遇到的问题

    2024-04-28 13:22:01       12 阅读
  2. 接口的构成

    2024-04-28 13:22:01       17 阅读
  3. 天星金融倡导智慧投资,共筑群众财富安全防线

    2024-04-28 13:22:01       14 阅读
  4. 【面试题】谈谈你对SpringBoot的理解

    2024-04-28 13:22:01       15 阅读
  5. QT知识体系框架及对应文章汇总

    2024-04-28 13:22:01       14 阅读
  6. Uniapp 点击图片放大

    2024-04-28 13:22:01       16 阅读
  7. uni-app如何监测获取页面视图出现

    2024-04-28 13:22:01       13 阅读
  8. GNU/Linux - tty设备介绍

    2024-04-28 13:22:01       14 阅读
  9. js面试---闭包、作用域及作用域链、执行上下文

    2024-04-28 13:22:01       15 阅读
  10. Python构建学生信息管理系统:需求分析与规划

    2024-04-28 13:22:01       14 阅读
  11. 沪深websocket level2/level1行情推送接入示例

    2024-04-28 13:22:01       9 阅读