This document summarizes a microservices meetup hosted by @mosa_siru. Key points include:
1. @mosa_siru is an engineer at DeNA and CTO of Gunosy.
2. The meetup covered Gunosy's architecture with over 45 GitHub repositories, 30 stacks, 10 Go APIs, and 10 Python batch processes using AWS services like Kinesis, Lambda, SQS and API Gateway.
3. Challenges discussed were managing 30 microservices, ensuring API latency below 50ms across availability zones, and handling 10 requests per second with nginx load balancing across 20 servers.
This document summarizes a microservices meetup hosted by @mosa_siru. Key points include:
1. @mosa_siru is an engineer at DeNA and CTO of Gunosy.
2. The meetup covered Gunosy's architecture with over 45 GitHub repositories, 30 stacks, 10 Go APIs, and 10 Python batch processes using AWS services like Kinesis, Lambda, SQS and API Gateway.
3. Challenges discussed were managing 30 microservices, ensuring API latency below 50ms across availability zones, and handling 10 requests per second with nginx load balancing across 20 servers.
This document discusses Yarn and its advantages over npm. It notes that Yarn uses yarn.lock files instead of npm-shrinkwrap.json files to lock down dependency versions. Yarn is also described as being faster, able to work offline by caching dependencies, and potentially more secure than npm with features like flat mode and module folders. The document suggests Yarn may handle dependencies and devDependencies differently than npm, and questions whether the yarn.lock file should be committed to source control.
This document discusses Yarn and its advantages over npm. It notes that Yarn uses yarn.lock files instead of npm-shrinkwrap.json files to lock down dependency versions. Yarn is also described as being faster, able to work offline by caching dependencies, and potentially more secure than npm with features like flat mode and module folders. The document suggests Yarn may handle dependencies and devDependencies differently than npm, and questions whether the yarn.lock file should be committed to source control.
Toru Yoshikawa highlights 10 awesome features of Chrome DevTools including the ability to pick colors from the screen in Elements, adjust animation speed in Elements, define animation timing in Elements, search by selector in Elements, take timeline screenshots in Timeline, show layers in Layout, enable network throttling in Network, display variable values inline in Sources, store variables as globals in Sources, manage framework blackboxing in Sources, and enable remote debugging of WebViews. Yoshikawa also provides links to resources on using Chrome DevTools and its official documentation.
64. ⾒見見た⽬目のカスタマイズ
Custom.cssに任意のスタイルを定義する
Mac
~∼/Library/Application Support/Google/Chrome/Default/
User StyleSheets/Custom.css
Windows
C:UsersYourUsernameAppDataLocalGoogleChrome
User DataDefaultUser StyleSheetsCustom.css
⼤大本のスタイルの確認(DevToolsをデバッグしても良良い)
chrome-‐‑‒devtools://devtools/devTools.css