📣 Back to School开学季 - VIP通行证5折优惠!蓝莓、Offer多多同步优惠
12
返回列表 发新帖
楼主: aokise
跳转到指定楼层
上一主题 下一主题
收起左侧

自我督促,看视频记录帖

🔗
 楼主| aokise 2018-7-24 03:06:50 | 只看该作者
全局:
2018.07.20
monolith vs microservice
https://www.youtube.com/watch?v=qYhRvH9tJKw
monolith:
Simple to develop. Simple to test. Simple to deploy. You just have to copy the packaged application to a server.
Simple to scale horizontally by running multiple copies behind a load balancer.
Good for small team.

when package and team go larger and larger, hard to maintain. Need to understand whole application.
The size of the application can slow down the start-up time.
You must redeploy the entire application on each update.
Impact of a change is usually not very well understood which leads to do extensive manual testing.
Continuous deployment is difficult.
Monolithic applications can also be difficult to scale when different modules have conflicting resource requirements.
Another problem with monolithic applications is reliability. Bug in any module (e.g. memory leak) can potentially bring down the entire process. Moreover, since all instances of the application are identical, that bug will impact the availability of the entire application.
Monolithic applications has a barrier to adopting new technologies. Since changes in frameworks or languages will affect an entire application it is extremely expensive in both time and cost.

microservice:
The idea is to split your application into a set of smaller, interconnected services instead of building a single monolithic application. Each microservice is a small application that has its own hexagonal architecture consisting of business logic along with various adapters.

t tackles the problem of complexity by decomposing application into a set of manageable services which are much faster to develop, and much easier to understand and maintain.
It enables each service to be developed independently by a team that is focused on that service.
It reduces barrier of adopting new technologies since the developers are free to choose whatever technologies make sense for their service and not bounded to the choices made at the start of the project.
Microservice architecture enables each microservice to be deployed independently. As a result, it makes continuous deployment possible for complex applications.


How uber changed from monolith to microservice
https://www.youtube.com/watch?v=Zed6udTPGro
回复

使用道具 举报

🔗
 楼主| aokise 2018-8-21 10:11:48 | 只看该作者
全局:
Android activity life cycle      https://youtu.be/UJN3AL4tiqw
回复

使用道具 举报

🔗
 楼主| aokise 2018-8-21 10:12:36 | 只看该作者
全局:
Android activity life cycle 2.       https://youtu.be/aCCpgHrlWwA
回复

使用道具 举报

🔗
 楼主| aokise 2018-8-21 10:13:12 | 只看该作者
全局:
Android instant app.        https://youtu.be/oispNrpGnIY
回复

使用道具 举报

🔗
cynthiazhxu 2018-8-27 11:31:48 | 只看该作者
全局:
有兴趣可以看看这个:
https://www.youtube.com/watch?v=1KsZKRcgmuU
回复

使用道具 举报

🔗
 楼主| aokise 2018-8-27 13:00:38 | 只看该作者
全局:
autumnhu 发表于 2018-8-27 11:31
有兴趣可以看看这个:
https://www.youtube.com/watch?v=1KsZKRcgmuU

多谢,有空看看
回复

使用道具 举报

🔗
 楼主| aokise 2018-9-23 07:46:58 | 只看该作者
全局:
boom filter
https://www.youtube.com/watch?v=bgzUdBVr5tE
回复

使用道具 举报

🔗
Hmoon 2019-12-16 14:49:19 | 只看该作者
全局:
楼主有没有知道有什没比较好的microservice开发的资料吗?
回复

使用道具 举报

🔗
 楼主| aokise 2020-1-17 14:54:27 | 只看该作者
全局:
https://youtu.be/kx-XDoPjoHw
这个大叔英文发音是真的差,但讲的是真的好
top k problem in large scale system
slow  path + fast path
回复

使用道具 举报

🔗
 楼主| aokise 2020-1-20 10:25:23 | 只看该作者
全局:
https://soulmachine.gitbooks.io/ ... /heavy-hitters.html
另外一个讲top k的,和上面大叔讲的差不多,但是文字版+中文
回复

使用道具 举报

您需要登录后才可以回帖 登录 | 注册账号
隐私提醒:
  • ☑ 禁止发布广告,拉群,贴个人联系方式:找人请去🔗同学同事飞友,拉群请去🔗拉群结伴,广告请去🔗跳蚤市场,和 🔗租房广告|找室友
  • ☑ 论坛内容在发帖 30 分钟内可以编辑,过后则不能删帖。为防止被骚扰甚至人肉,不要公开留微信等联系方式,如有需求请以论坛私信方式发送。
  • ☑ 干货版块可免费使用 🔗超级匿名:面经(美国面经、中国面经、数科面经、PM面经),抖包袱(美国、中国)和录取汇报、定位选校版
  • ☑ 查阅全站 🔗各种匿名方法

本版积分规则

>
快速回复 返回顶部 返回列表