投稿時間:2023-07-24 05:16:06 RSSフィード2023-07-24 05:00 分まとめ(22件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
海外TECH	MakeUseOf	How to Fix the “Requested Operation Requires Elevation” Error 740 on Windows 10 & 11	https://www.makeuseof.com/requested-operation-requires-elevation-error-740-windows/	windows	2023-07-23 19:16:22
海外TECH	MakeUseOf	How to Build a Lorem Ipsum Text Generator With JavaScript and Vite	https://www.makeuseof.com/javascript-vite-build-lorem-ipsum-text-generator/	dummy	2023-07-23 19:01:23
海外TECH	DEV Community	Microservice architecture - Benefits, how to implement, challenges, etc.	https://dev.to/ra1nbow1/microservice-architecture-benefits-how-to-implement-challenges-etc-4e8l	Microservice architecture Benefits how to implement challenges etc Microservice ArchitectureMicroservice architecture is an architectural style that structures an application as a collection of loosely coupled services Each service runs in its own processes and communicates through APIs Microservices aim to overcome the limitations of monolithic architecture Benefits of Microservice ArchitectureScalability Since each service is independent they can be scaled horizontally by adding more instances of that service This makes it easy to scale individual components based on demand Agility Services are developed deployed and scaled independently Developers can quickly update or replace a service without affecting others This results in rapid independent development and release cycles Fault isolation Since each service has its own processes and resources a failure in one service does not affect other services This improves fault tolerance and reliability The entire system does not have to be restarted for a single service failure Polyglot persistence Services are not restricted to any specific data store They can use different databases and storage technologies based on their needs This improves flexibility Independence of teams Since each service is independent different teams can work on different services concurrently This allows for separation of concerns and specialized teams How to Implement MicroservicesDefine domain driven services Identify core business capabilities and create independent services around those domains This results in high cohesion within services and loose coupling between services Use lightweight protocols Services should communicate using lightweight protocols like HTTP RESTful APIs and message queues This decouples services and makes them independently deployable Deploy independently Services should be packaged independently so they can be deployed upgraded and scaled independently They should be able to run on any environment or platform Replicate non functional requirements Each service should be self sufficient by replicating non functional requirements like security logging monitoring caching etc Use service discovery A service discovery mechanism is required to dynamically find and register microservices This allows services to locate each other at runtime Plan for failure Failures are inevitable in distributed systems Plan for failure scenarios and implement retries timeouts circuit breakers and fallback mechanisms Challenges of Microservice ArchitectureIncreased complexity Due to the distributed nature microservices introduce operational complexity Managing many independent services requires orchestration discovery monitoring logging etc Orchestration challenges Coordinating and choreographing interactions between independent services can be challenging Service mesh architectures are emerging to simplify service orchestration Testing issues Testing interactions between independently deployed services is hard Test strategies like contract testing chaos testing etc are required Debugging difficulties Distributed tracing and logs correlation techniques are required to effectively debug microservices While microservice architecture brings many benefits it also introduces operational challenges due to its distributed nature A well planned microservices implementation that addresses these challenges can provide an effective architecture for building scalable modular applications	2023-07-23 19:15:27
海外TECH	DEV Community	Kubernetes Monitoring Best Practices	https://dev.to/squadcast/kubernetes-monitoring-best-practices-17f	Kubernetes Monitoring Best PracticesKubernetes can be installed using different tools whether open source third party vendor or in a public cloud In most cases default installations have limited monitoring capabilities Therefore once a Kubernetes cluster is running administrators must implement monitoring solutions to meet their requirements Typical use cases for Kubernetes monitoring include Ensuring workload reliabilityAchieving high level visibility into your workloadAlerting and enabling incident managementEffective Kubernetes monitoring requires a mix of tools strategy and technical expertise To help you get it right this article will explore seven essential Kubernetes monitoring best practices in detail Summary of key Kubernetes monitoring best practices conceptsThe table below summarizes the Kubernetes monitoring best practices we will explore in this article Concept Monitoring vs observabilityDescription Observability means gaining insights into your workload s performance using external indicators Monitoring means checking such indicators over time Concept Determining requirementsDescription Accurately determine your requirements and monitoring goals ConceptIdentify appropriate metricsDescriptionIdentify which metrics you need to achieve your monitoring goals Concept Select the right toolsDescription Selecting the right tools given your requirements is a critical best practice A main decision here is whether to build something in house using open source software or buy a more complete SaaS solution with better support Concept Monitor the monitoring systemDescription In a production workload it is important to monitor the monitoring system itself to ensure it is reliable and highly available Concept Consider data storageDescription Monitoring data must be stored and managed effectively Concept Monitor the control planeDescription Monitoring the Kubernetes control plane is easy to overlook so teams should be intentional about control plane monitoring Concept Account for incident responseDescription Monitoring outputs can enhance incident response coordination which can reduce MTTR mean time to resolve Monitoring vs observabilityBefore we go into more detail let s unpack an often confusing topic monitoring vs observability The term “monitoring is more traditional and covers the collection of metrics and logs used to monitor the application infrastructure components The idea is to “monitor a workload by constantly evaluating the real time performance of its underlying infrastructure Observability is a relatively new concept and even though it overlaps with monitoring its end goal is to isolate a performance bottleneck along a transaction path instead of monitoring the application infrastructure Observability gained traction in application environments designed based on the paradigm of microservices where an application comprises modularized services hosted in ephemeral containers and interacting with each other via application programming interfaces API In such an environment monitoring the servers and containers in isolation isn t meaningful so a new perspective was required giving rise to the notion of observability In addition to metrics and logs observability also includes distributed tracing to follow the path of a transaction through the application infrastructure Distributed tracing enables operation engineers to understand the path a user s request takes including When the workload received the request The stages or microservices it went through andWhen the response was sent to the user Observability allows the operations engineers to quickly understand the upstream and downstream impact of application services on each other Typically observability tools will combine metrics logs and tracing to give engineers a coherent view of the entire transaction path across the infrastructure Read this article if you want to learn more about observability also called “Oy essential Kubernetes monitoring best practicesThe seven Kubernetes monitoring best practices below can help DevOps and SRE site reliability engineering teams achieve SLOs service level objectives and improve overall infrastructure observability Kubernetes monitoring best practice Determine what you want to achieveDetermining business goals is the first and arguably the most important Kubernetes monitoring best practice Examples of such goals are Gain visibility into your cluster s healthGain visibility into the end user s experienceBe alerted when certain events occurAnticipate potential problemsIdentify trends and patterns in the workload utilization such as a steady increase in disk utilization which will lead to the disk being full within a certain period of timeIdentify trends and patterns going out of the ordinary or out of what s expectedScale pods in and out when certain conditions are metEvaluate the reliability of the application against expected criteriaWhile planning is important it s also essential not to overthink it Teams just getting started with monitoring should avoid analysis paralysis and instead take an iterative approach to developing a plan Additional requirements can be added later to address new information and requirements Kubernetes monitoring best practice Identify metrics to monitorOnce you ve identified your business goals you can identify which metrics you need to collect to achieve those goals This step also includes defining related configuration parameters such as the collection rate and how long you need to store the metrics data Some metrics are usually readily available typically system metrics These metrics include CPU utilizationMemory utilizationFree space available on disksDisk input output dataNetwork usageSystem metrics are usually necessary as part of any monitoring strategy and tend to show the overall stress the cluster is under However they are quite basic and usually won t give enough actionable information beyond telling whether the cluster seems healthy Additionally more complex metrics are often required These metrics are often tied to the software you run For example they could measure How responsive is the website or the app How many users are currently logged in What is the average number of concurrent users at am on weekdays How fast does your support team respond to the initial requests What s the rate of xx errors reported by your web server What s the average number of jobs in an input queue per day Kubernetes monitoring best practice Select the right toolsOur next Kubernetes monitoring best practice is selecting the right tools based on the required metrics and achieving your monitoring goals Free and Open Source Software FOSS vs commercial third party software is commonly used to categorize Kubernetes monitoring tools Some examples of FOSS monitoring solutions include Tools to collect metrics e g Prometheus kube metrics Tools to collect logs e g Loki Fluentd Tools to collect traces e g Jaeger Tools for visualization and alerting e g Grafana Alertmanager While plenty of open source options are available you will need in house expertise and a significant amount of DevOps engineers time to build and maintain a FOSS monitoring solution If you don t have in house experts you can hire consultants to build a solution but this will likely be expensive On the other hand developing your own monitoring solution could save you a considerable amount of money in the long run The alternative is to pay for third party software which usually offers turn key software as a service SaaS solutions Commercial options typically have more advanced products such as machine learning to detect suspicious trends and patterns or perform offline data analysis Additionally most commercial solutions come with a level of support that FOSS projects lack When evaluating solutions remember that using third party tools especially SaaS products can create compliance issues such as safeguarding personally identifiable information under HIPAA or GDPR You might also need to open your cluster to allow routes from the internet for the third party SaaS products which increases attack surface and could create other security issues Kubernetes monitoring best practice Monitor your monitoring systemUnless you run a non production workload you probably want every element of your monitoring solution to be highly available and scalable Achieving high availability monitoring requires monitoring of the monitoring system itself At a minimum you must be able to detect critical failures in your monitoring system and send notifications when they occur Ideally you should also configure automated remediation of such problems Generally speaking this extra level of monitoring is required only for in house solutions as third party SaaS vendors usually have monitoring systems for their platforms Some FOSS products incorporate their own monitoring systems For example Loki comes with Loki Canary which regularly sends dummy logs to Loki and reads them back to ensure it works fine Kubernetes monitoring best practice Consider data storageYour monitoring system will accumulate data over time and this data should be managed like any other data You will need to determine how long you need to hold onto it maybe even put it in cold storage after a while Be sure to consider any regulations or legal requirements applicable to your organization so that the data can be accessed and provided quickly if requested Determining your data retention requirements for your monitoring data will be part of your overall requirement gathering exercise and you will then need to implement it accordingly Kubernetes monitoring best practice Monitor the control planeDo not neglect monitoring your control plane as well All the best practices we have listed also apply to the control plane not just the data plane Some Kubernetes managed solutions such as Amazon s EKS will do that automatically for you If not you will need to add the monitoring of the control plane nodes and the various control plane components into your monitoring strategy Kubernetes monitoring best practice Account for incident responseOnce your monitoring system is up and running and able to send alerts to your team you must consider how to respond to such alerts Squadcast can help coordinate incident responses ensuring a very high level of coordination within your team so they can be as efficient as possible while dealing with the problem Integrating monitoring data into a robust incident response strategy helps teams detect and recover from outages and other production disrupting incidents faster As a result MTTR decreases and uptime improves ConclusionMonitoring your production workloads is necessary but working towards true observability across your Kubernetes infrastructure is important If you re just starting the most important of our Kubernetes monitoring best practices is gathering your requirements and defining your business goals Once you have requirements and goals identify which metrics will help fulfill them before you move on to tooling Selecting the right tools is an important step especially choosing between FOSS one consequence being that your team will have to spend time and effort to implement an in house monitoring solution and a paid for third party solution which are usually more exhaustive and come with better support Compliance and security are other considerations you might need to consider when choosing your tools depending on your project s requirements Finally especially after building an in house solution ensure your monitoring system is reliable which would require monitoring it And don t forget that Squadcast can help with the coordination of incident responses within your team	2023-07-23 19:07:18
医療系	医療介護 CBnews	在院日数短縮の競争激化、問われる“善”とは-先が見えない時代の戦略的病院経営（200）	https://www.cbnews.jp/news/entry/20230721083910	入院患者	2023-07-24 05:00:00
ニュース	BBC News - Home	Locals step in to help tourists after Rhodes fires	https://www.bbc.co.uk/news/uk-66284588?at_medium=RSS&at_campaign=KARANGA	bedrooms	2023-07-23 19:01:46
ニュース	BBC News - Home	Vingegaard retains Tour title as Meeus wins final stage	https://www.bbc.co.uk/sport/cycling/66285026?at_medium=RSS&at_campaign=KARANGA	stage	2023-07-23 19:04:17
ビジネス	ダイヤモンド・オンライン - 新着記事	ワグネル反乱でプーチン体制に起きた「2つの初めて」で戦争は泥沼化、防衛研・兵頭氏の展望 - 混迷ロシア	https://diamond.jp/articles/-/326491	防衛研究所	2023-07-24 04:50:00
ビジネス	ダイヤモンド・オンライン - 新着記事	コンビニ3社の最終バトル、総合商社が本格参戦で狙う「ゲームチェンジ」の全貌 - セブンの死角 伊藤忠＆三菱商事の逆襲	https://diamond.jp/articles/-/326446	コンビニ社の最終バトル、総合商社が本格参戦で狙う「ゲームチェンジ」の全貌セブンの死角伊藤忠三菱商事の逆襲コンビニの王者、セブンイレブンには死角がある。	2023-07-24 04:45:00
ビジネス	ダイヤモンド・オンライン - 新着記事	「駆け込み贈与」は年内がラストチャンス！相続＆生前贈与の新ルール徹底解説 - やってはいけない！相続＆生前贈与	https://diamond.jp/articles/-/326429	「駆け込み贈与」は年内がラストチャンス相続生前贈与の新ルール徹底解説やってはいけない相続生前贈与あなたの相続税対策、そのまま続けていても大丈夫年ぶりとなる相続と生前贈与のルール改正まであと半年を切った。	2023-07-24 04:40:00
ビジネス	ダイヤモンド・オンライン - 新着記事	オトコ目線の都市空間からの脱却、ESG時代の商業施設と「列島改造論」とは？ - 政策・マーケットラボ	https://diamond.jp/articles/-/326542		2023-07-24 04:35:00
ビジネス	ダイヤモンド・オンライン - 新着記事	「障害者は不幸」「働かない人を救済するな」…冷酷な“数字の支配”が私たちを苦しめる - 要約の達人　from flier	https://diamond.jp/articles/-/326519	fromflier	2023-07-24 04:30:00
ビジネス	ダイヤモンド・オンライン - 新着記事	ロシアの穀物合意離脱、その狙いは - WSJ PickUp	https://diamond.jp/articles/-/326531	wsjpickup	2023-07-24 04:25:00
ビジネス	ダイヤモンド・オンライン - 新着記事	テスラが誇るAIに現実の壁 - WSJ PickUp	https://diamond.jp/articles/-/326530	wsjpickup	2023-07-24 04:20:00
ビジネス	ダイヤモンド・オンライン - 新着記事	青山学院大学の学生にリアルな就活について話を聞いてみた【学生のコメント付き！】 - 大学図鑑！2024 有名大学82校のすべてがわかる！	https://diamond.jp/articles/-/326509		2023-07-24 04:12:00
ビジネス	ダイヤモンド・オンライン - 新着記事	職場にいる「本当にコミュ力が高い人」と「おしゃべりなだけで浮いてしまっている人」の決定的な差とは - 1秒で答えをつくる力 お笑い芸人が学ぶ「切り返し」のプロになる48の技術	https://diamond.jp/articles/-/326506		2023-07-24 04:09:00
ビジネス	ダイヤモンド・オンライン - 新着記事	会社を変えようとする経営者が「絶対にやってはいけない」たった1つのこと（後編） - 新装版　売上2億円の会社を10億円にする方法	https://diamond.jp/articles/-/325833	会社を変えようとする経営者が「絶対にやってはいけない」たったつのこと後編新装版売上億円の会社を億円にする方法コツコツと業績を伸ばしてきた経営者が直面する「売上の壁」。	2023-07-24 04:06:00
ビジネス	ダイヤモンド・オンライン - 新着記事	【精神科医が教える】 同じような毎日が続いている人、ちょっと読んでみて！ - 精神科医Tomyが教える 40代を後悔せず生きる言葉	https://diamond.jp/articles/-/324869	そんなときの助けになるのが、『精神科医Tomyが教える代を後悔せず生きる言葉』ダイヤモンド社だ。	2023-07-24 04:03:00
ビジネス	不景気.com	青森のパン店「LittlePrincess」の運営会社に破産開始決定 - 不景気com	https://www.fukeiki.com/2023/07/little-princess.html	dreamssquare	2023-07-23 19:05:40
ビジネス	東洋経済オンライン	｢子の反抗的な態度｣に反応する大人のNG行動 夏休み｢よりわかりあえる関係性｣を築くコツ | 自衛隊員も学ぶ！メンタルチューニング | 東洋経済オンライン	https://toyokeizai.net/articles/-/687760?utm_source=rss&utm_medium=http&utm_campaign=link_back	人間関係	2023-07-24 04:50:00
ビジネス	東洋経済オンライン	南阿蘇鉄道､7年ぶり｢全線再開｣までの長い道のり 三陸鉄道の事例を参考に復旧スキームを構築 | ローカル線･公共交通 | 東洋経済オンライン	https://toyokeizai.net/articles/-/688640?utm_source=rss&utm_medium=http&utm_campaign=link_back	三陸鉄道	2023-07-24 04:30:00
海外TECH	reddit	Team BDS vs. Team Heretics / LEC 2023 Summer Groups - Group A Qualification Match / Post-Match Discussion	https://www.reddit.com/r/leagueoflegends/comments/157nx9a/team_bds_vs_team_heretics_lec_2023_summer_groups/	Team BDS vs Team Heretics LEC Summer Groups Group A Qualification Match Post Match DiscussionLEC SUMMER Official page Leaguepedia Liquipedia Live Discussion Eventvods com New to LoL Patch Team Heretics Team BDS Team Heretics advances to playoffs to play Fnatic TH Leaguepedia Liquipedia Website Twitter Facebook YouTube BDS Leaguepedia Liquipedia Website Twitter Facebook MATCH TH vs BDS Winner Team Heretics in m Match History Game Breakdown Bans Bans G K T D B TH azir jayce maokai braum zeri k C H M B BDS rell leblanc rakan viego vi k H I B M M TH vs BDS Evi ornn TOP renekton Adam Jankos trundle JNG ivern Sheo Vetheo kaisa MID cassiopeia nuc Flakked xayah BOT samira Crownie Mersa milio SUP nautilus Labrov MATCH BDS vs TH Winner Team Heretics in m Match History Game Breakdown Bans Bans G K T D B BDS kaisa leblanc xayah braum alistar k M H TH rell maokai ivern varus jinx k I H O O B O BDS vs TH Adam olaf TOP renekton Evi Sheo gragas JNG viego Jankos nuc jayce MID ahri Vetheo Crownie samira BOT aphelios Flakked Labrov nautilus SUP rakan Mersa This thread was created by the Post Match Team submitted by u gandalf to r leagueoflegends link comments	2023-07-23 19:33:48