投稿時間:2023-03-10 14:31:28 RSSフィード2023-03-10 14:00 分まとめ(36件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
IT	ITmedia 総合記事一覧	[ITmedia ビジネスオンライン] 実はアパレル完全撤退じゃない？　イトーヨーカドー、「肌着」は事業継続へ	https://www.itmedia.co.jp/business/articles/2303/10/news143.html	itmedia	2023-03-10 13:08:00
IT	ITmedia 総合記事一覧	[ITmedia PC USER] デル、第13世代Core i7/i9採用のハイスペック16型/18型ゲーミングノートPC	https://www.itmedia.co.jp/pcuser/articles/2303/10/news149.html	coreii	2023-03-10 13:07:00
AWS	lambdaタグが付けられた新着投稿 - Qiita	AWSサーバーレス環境でのロギング	https://qiita.com/takuto22/items/50316ec77be5d3269167	lambda	2023-03-10 13:17:21
python	Pythonタグが付けられた新着投稿 - Qiita	discord.py チュートリアル	https://qiita.com/TakeMimi/items/1e2d76eecc25e92c93ef	discordpy	2023-03-10 13:04:28
Ruby	Rubyタグが付けられた新着投稿 - Qiita	docker-compose run web rails db:migrateでエラーが出る 100DaysOfQiita　3日目	https://qiita.com/30113011tr/items/5aa8580f2c3558548d97	scantconnecttolocalmysql	2023-03-10 13:32:57
Ruby	Rubyタグが付けられた新着投稿 - Qiita	コンテナ向けデプロイツールmrskを試してみる	https://qiita.com/takahashim/items/a41fa8f40ff4a2396d68	computeinstan	2023-03-10 13:11:44
Linux	Ubuntuタグが付けられた新着投稿 - Qiita	使い古したMacにUbuntu22.04LTSを導入してみた	https://qiita.com/takatakao397/items/fdbe9454754ab50f16ed	corei	2023-03-10 13:18:12
AWS	AWSタグが付けられた新着投稿 - Qiita	AWSにおける監視	https://qiita.com/takuto22/items/cf0f6207c0cc85196a8f	運用	2023-03-10 13:17:42
AWS	AWSタグが付けられた新着投稿 - Qiita	AWSサーバーレス環境でのロギング	https://qiita.com/takuto22/items/50316ec77be5d3269167	lambda	2023-03-10 13:17:21
Docker	dockerタグが付けられた新着投稿 - Qiita	docker-compose down出来ない 100DaysOfQiita　3日目(2)	https://qiita.com/30113011tr/items/94bf8fcc48c0272bdc3c	pleapplocaldefaulterrorr	2023-03-10 13:53:04
Docker	dockerタグが付けられた新着投稿 - Qiita	docker-compose run web rails db:migrateでエラーが出る 100DaysOfQiita　3日目	https://qiita.com/30113011tr/items/5aa8580f2c3558548d97	scantconnecttolocalmysql	2023-03-10 13:32:57
Ruby	Railsタグが付けられた新着投稿 - Qiita	docker-compose down出来ない 100DaysOfQiita　3日目(2)	https://qiita.com/30113011tr/items/94bf8fcc48c0272bdc3c	pleapplocaldefaulterrorr	2023-03-10 13:53:04
Ruby	Railsタグが付けられた新着投稿 - Qiita	docker-compose run web rails db:migrateでエラーが出る 100DaysOfQiita　3日目	https://qiita.com/30113011tr/items/5aa8580f2c3558548d97	scantconnecttolocalmysql	2023-03-10 13:32:57
Ruby	Railsタグが付けられた新着投稿 - Qiita	コンテナ向けデプロイツールmrskを試してみる	https://qiita.com/takahashim/items/a41fa8f40ff4a2396d68	computeinstan	2023-03-10 13:11:44
技術ブログ	Developers.IO	【レポート】気づいたら攻撃されていた…」を防ぐには？ クラウド/テレワーク導入が生んだ新たなサイバー攻撃リスクと対策　＃ Security Days Spring 2023	https://dev.classmethod.jp/articles/securitydays-2023-d403/	securitydaysspring	2023-03-10 04:48:34
技術ブログ	Developers.IO	【レポート】サイバー脅威最新レポートから紐解く ~攻撃者視点で考える最新セキュリティー対策~　＃ Security Days Spring 2023	https://dev.classmethod.jp/articles/securitydays-2023-a402/	securitydaysspring	2023-03-10 04:25:24
海外TECH	DEV Community	Building Resilient Systems: Retry Pattern in Microservices	https://dev.to/apoorvtyagi/building-resilient-systems-retry-pattern-in-microservices-1ngj	Building Resilient Systems Retry Pattern in Microservices IntroductionAny application that communicates with other resources over a network has to be resilient to transient failures These failures are sometimes self correcting For example a service that is processing thousands of concurrent requests can implement an algorithm to temporarily reject any further requests until its load gets reduced An application that is trying to access this service may initially fail to connect but if it tries again it might succeed While designing any system it is essential to make it resilient against such failures In this article we will look at one of the many ways of achieving it using Retries At our current organization we use this mechanism throughout our microservices to make sure that we handle failures and at the same time provide the best of our services to our customers Let s start by first defining what we mean by failures What is a failure Failures can be caused by numerous reasons while our services communicate with each other over a network Some examples of types of failures are A slow response No response at allA response in the incorrect formatA response containing incorrect dataIn planning for failures we should seek to handle each of these errors RetryRetry is a process of automatically repeating a request in case any failure is detected This helps return fewer errors to the users improving the consumer experience on our application The only caveat when it comes to retrying is that multiple requests to the same resource should have the same effect as making a single request i e the resource should be idempotent In REST APIs GET HEAD and OPTIONS methods generally do not change the resource state on the server and hence are mostly retryable When should we retry a request Ideally we should only retry a failed request when we know it has any possibility of succeeding the next time otherwise it will just be a waste of resources CPU Memory and Time For example you might get an error with status code Service unavailable when the server had an unexpected hiccup while connecting to a DB host A retry may work here if the second call to the upstream service gets a DB instance that is available On the other hand retrying for errors with status code Unauthorised or Forbidden may never work because they require changing the request itself The general idea is that if an upstream request fails we immediately try again and probably the second request will succeed However this will not always benefit us The actual implementation should include a delay between the subsequent requests We will discuss that in the next sections Problem with normal retriesConsider what happens when we get concurrent requests amp all hosts of the upstream service are down at that instance If we were to retry immediately these failed requests would retry immediately on a static interval They would also be combined with new requests from the increasing traffic and could make the service down again This creates a cycle that keeps repeating until all the retries are exhausted and will also eventually makes the upstream service overwhelm and might further degrade the service that is already under distress This is a common computer science problem also known as the Thundering Herd problem To tackle this we can introduce some delay in retrying a failed request BackoffThe wait time between a request and its subsequent retry is called the backoff With backoff the amount of time between requests increases exponentially as the number of retry requests increases The scenario we just discussed above is where having a backoff helps it changes the wait time between attempts based on the number of previous failures From the above figure let s say the initial request goes at the th millisecond and fails with a retryable status code Assuming that we have set up the backoff time of ms and neglecting the request response time the first retry attempt happens at th milliseconds ms If this fails again the second retry then happens at ms Similarly the subsequent retry happens at ms till we exhaust all the retries If any of the request failures are caused by the upstream service being overloaded this mechanism of spreading out our requests and retries gives us a better chance of getting a successful response JitterThe Backoff strategy allows us to distribute the load sent to the upstream services Yet turns out it isn t always the wisest decision because all the retries are still going to be in sync which can lead to a spike on the service Jitter is the process of breaking this synchronization by increasing or decreasing the backoff delay to further spread out the load Coming back to our previous example let s say our upstream service is serving the maximum load that it can handle and four new clients send their requests which fail because the server could not handle that amount of concurrent requests With only backoff implementation let s say after milliseconds we retry all failed requests Now these retry requests would also fail again for the same reason To avoid this the retry implementation needs to have randomness ImplementationGoing through this AWS documentation that goes deep into the exponential backoff algorithm we have implemented our retry mechanism using Axios interceptorThe example is written inside of a Nodejs application but the process will be similar regardless of which JavaScript framework you re using In this we expect the following settings Total Retries The number of maximum retries you want before returning a failed response to the client Retry Status Codes The HTTP status codes that you want to retry for By default we have kept it on for all status codes gt Backoff This is the minimum time we have to wait while sending any subsequent retry request axios interceptors response use async error gt const statusCode error response status const currentRetryCount error response config currentRetryCount const totalRetry error response config retryCount const retryStatusCodes error response config retryStatusCodes const backoff error response config backoff if isRetryRequired statusCode retryStatusCodes currentRetryCount totalRetry error config currentRetryCount currentRetryCount currentRetryCount Create a new promise with exponential backoff const backOffWithJitterTime getTimeout currentRetryCount backoff const backoff new Promise function resolve setTimeout function resolve backOffWithJitterTime Return the promise in which recalls Axios to retry the request await backoff return axios error config function isRetryRequired statusCode retryStatusCodes currentRetryCount totalRetry return statusCode gt retryStatusCodes includes statusCode amp amp currentRetryCount lt totalRetry function getTimeout numRetries backoff const waitTime Math min backoff numRetries Multiply waitTime by a random number between and return Math random waitTime While making an Axios request you have to make sure to add the variables in the request configurations const axios require axios const sendRequest async gt const requestConfig method post url api example com headers authorization xxx data payload retryCount retryStatusCodes backoff timeout const response await axios requestConfig return response data When configuring the retry mechanism it is important to tune the total retries and maximum delay together The goal is to tailor these values keeping in mind the worst case response time to our consumers Pictorially this is how it will work For Java based applications the same can be done using resiliencej ConclusionIn this post we looked at one of the many service reliability mechanisms Retries We saw how it works how to configure it and tackle some of the common problems with retries using backoff and jitter I hope you found it helpful Comments or corrections are always welcome GitHub Link for the above source code can be found here	2023-03-10 04:10:00
海外科学	NYT > Science	Cyclone Freddy Lashes Mozambique and Madagascar	https://www.nytimes.com/2023/03/09/world/africa/cyclone-freddy-mozambique-madagascar.html	Cyclone Freddy Lashes Mozambique and MadagascarThe storm which has killed people already has hit several countries in southeastern Africa and is on track to last longer than the record of days	2023-03-10 04:14:42
金融	ニッセイ基礎研究所	2022年に話題となった年金ニュースをTwitterから振り返る－「年金」を含むツイートの投稿契機 （2022年通年）	https://www.nli-research.co.jp/topics_detail1/id=74140?site=nli	月日や月日も、年に公表されていた年金改革案に関するツイートが投稿契機となった図表。	2023-03-10 13:09:25
金融	日本銀行：RSS	総裁記者会見ライブ配信（3月10日15時30分予定）	http://www.boj.or.jp/about/release/sousailive.htm	記者会見	2023-03-10 13:30:00
ニュース	@日本経済新聞 電子版	WBC日本初戦　関東地区の平均視聴率41.9% https://t.co/Zvl9wHxyv2	https://twitter.com/nikkei/statuses/1634055376785281024	平均視聴率	2023-03-10 04:55:35
ニュース	@日本経済新聞 電子版	最後は「静か」に　黒田日銀、サプライズ政策連発の果て https://t.co/Rjg3NyBWda	https://twitter.com/nikkei/statuses/1634043637184221184	黒田	2023-03-10 04:08:56
ニュース	@日本経済新聞 電子版	バフェットの２人目の師匠　フィッシャーの銘柄選定法 https://t.co/d36s7DDB8s	https://twitter.com/nikkei/statuses/1634042867458117635	銘柄	2023-03-10 04:05:53
ニュース	BBC News - Home	Heavy snow and high winds bring treacherous travelling conditions	https://www.bbc.co.uk/news/uk-64904704?at_medium=RSS&at_campaign=KARANGA	motorway	2023-03-10 04:43:33
ニュース	Newsweek	「南進」を始めた中国の隠せない野心──本格的な海外基地の展開をにらむ...長期戦略をひもとく	https://www.newsweekjapan.jp/stories/world/2023/03/post-101064.php		2023-03-10 13:30:00
IT	週刊アスキー	PC『ガンダムネットワーク大戦』でイベントバトル「激突！金色の不死鳥」が開催！	https://weekly.ascii.jp/elem/000/004/128/4128123/	開催	2023-03-10 13:55:00
IT	週刊アスキー	ドミノ・ピザ、3月10日16時まで「マイドミノ」を555円～で販売	https://weekly.ascii.jp/elem/000/004/128/4128115/	gogogo	2023-03-10 13:50:00
IT	週刊アスキー	Switch『ファンタジーライフｉ グルグルの竜と時をぬすむ少女』の最新ティザーPVが公開	https://weekly.ascii.jp/elem/000/004/128/4128125/	nintendo	2023-03-10 13:50:00
IT	週刊アスキー	Apple、クラシック音楽に特化した新アプリ「Apple Music Classical」を発表　日本は後日提供	https://weekly.ascii.jp/elem/000/004/128/4128100/	apple	2023-03-10 13:40:00
IT	週刊アスキー	あの銘店をもう一度第13弾 継ぎ足され続ける秘伝の"築炉窯出し"スープ 博多｢元祖名島亭｣	https://weekly.ascii.jp/elem/000/004/128/4128109/	野方ホープ	2023-03-10 13:30:00
IT	週刊アスキー	「フルーツピークス　横浜ポルタ店」オープン記念！　先着順でオリジナルノベルティー配布やSNSキャンペーンを実施	https://weekly.ascii.jp/elem/000/004/128/4128114/	横浜ポルタ	2023-03-10 13:30:00
IT	週刊アスキー	マランツ、9.4ch対応で音質強化の一体型最上位AVアンプ「CINEMA 40」を発表	https://weekly.ascii.jp/elem/000/004/128/4128118/	cinema	2023-03-10 13:20:00
IT	週刊アスキー	Ring、バッテリー版「Battery Doorbell Plus」を発表	https://weekly.ascii.jp/elem/000/004/128/4128113/	batterydoorbellplus	2023-03-10 13:25:00
IT	週刊アスキー	進撃コラボが来る！『フォートナイト』チャプター4 シーズン2「メガ」の最新トレーラーが公開中	https://weekly.ascii.jp/elem/000/004/128/4128117/	開始予定	2023-03-10 13:20:00
マーケティング	AdverTimes	生活シーン別に生活者のメディア接触を把握できるマップを作成　第4回メディアポジショニング調査	https://www.advertimes.com/20230310/article413488/	音声	2023-03-10 04:54:53
海外TECH	reddit	Counter Logic Gaming vs. Dignitas / LCS 2023 Spring - Week 7 / Post-Match Discussion	https://www.reddit.com/r/leagueoflegends/comments/11ne4dl/counter_logic_gaming_vs_dignitas_lcs_2023_spring/	Counter Logic Gaming vs Dignitas LCS Spring Week Post Match DiscussionLCS SPRING Official page Leaguepedia Liquipedia Eventvods com New to LoL Counter Logic Gaming Dignitas CLG Leaguepedia Liquipedia Website Twitter Facebook YouTube Subreddit DIG Leaguepedia Liquipedia Website Twitter Facebook YouTube Subreddit MATCH CLG vs DIG Winner Dignitas in m Match History Bans Bans G K T D B CLG gnar caitlyn karma taliyah syndra k H HT HT HT DIG elise annie ashe vi sion k I H M HT B HT B CLG vs DIG Dhokla gragas TOP renekton Armut Contractz viego JNG sejuani Santorin Palafox aurelion sol MID cassiopeia Jensen Luger xayah BOT aphelios Tomo Poome rakan SUP thresh IgNar This thread was created by the Post Match Team submitted by u gandalf to r leagueoflegends link comments	2023-03-10 04:03:48