投稿時間:2022-08-29 17:27:56 RSSフィード2022-08-29 17:00 分まとめ(34件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
IT	ITmedia 総合記事一覧	[ITmedia PC USER] SUNEAST、アルミ合金筐体を採用したType-C外付けポータブルSSD	https://www.itmedia.co.jp/pcuser/articles/2208/29/news134.html	itmediapcusersuneast	2022-08-29 16:08:00
TECH	Techable（テッカブル）	AIボイスレコーダー「オートメモ」、アプリから録音可能に。デバイス不要で録音・文字起こし	https://techable.jp/archives/184908	automemo	2022-08-29 07:00:07
IT	情報システムリーダーのためのIT情報専門サイト IT Leaders	ブリジストンがAWSと協業、小売やモビリティのサービスメニューを開発して運送業者に提供 | IT Leaders	https://it.impress.co.jp/articles/-/23696	ブリジストンがAWSと協業、小売やモビリティのサービスメニューを開発して運送業者に提供ITLeadersブリヂストンは年月日、小売サービスやモビリティサービスを強化するため、米AmazonWebServicesAWSと戦略的な協業を開始すると発表した。	2022-08-29 16:32:00
python	Pythonタグが付けられた新着投稿 - Qiita	pip freezeで上手く出力されない場合(@ file:~~となってしまう場合）	https://qiita.com/syusuke9999/items/59ae222ce395d3df0b73	anaconda	2022-08-29 16:36:27
python	Pythonタグが付けられた新着投稿 - Qiita	Google Colaboratory 環境で Stable Diffusion - GPU RAM 節約術（考察）	https://qiita.com/seaweeds/items/269132b783b46149036b	googlecolaboratory	2022-08-29 16:28:07
Linux	Ubuntuタグが付けられた新着投稿 - Qiita	vagrantのホスト名を指定してそこにscpでファイルアップロード	https://qiita.com/greenteabiscuit/items/2d5d26834e19ea60401c	config	2022-08-29 16:58:10
Docker	dockerタグが付けられた新着投稿 - Qiita	【Docker】ARGの値を必須にする方法	https://qiita.com/P-man_Brown/items/196045d8a15c95007cfe	argsamplevariableruntest	2022-08-29 16:40:38
技術ブログ	Developers.IO	[Solana] NTFをmintしてみる	https://dev.classmethod.jp/articles/solana-ntf-mint/	anchor	2022-08-29 07:47:48
技術ブログ	Developers.IO	Jenkins Pipeline and Jenkinsfile	https://dev.classmethod.jp/articles/jenkins-pipeline-and-jenkinsfile/	Jenkins Pipeline and JenkinsfileIntroduction to Jenkins Pipeline and Jenkinsfile Jenkins Pipeline involves the process to integrate and chain	2022-08-29 07:27:26
技術ブログ	Developers.IO	AWS License Manager へ AWS Managed Microsoft Active Directory の設定で失敗となってしまう原因について	https://dev.classmethod.jp/articles/aws-license-manager-failed/	awsmanagedmicrosoft	2022-08-29 07:08:23
海外TECH	DEV Community	Migrating Monoliths to Microservices in Practice	https://dev.to/codenameone/migrating-monoliths-to-microservices-in-practice-5a27	Migrating Monoliths to Microservices in PracticeThere have been amazing articles on the subjects of migrating from a monolith to a microservice architecture e g this is probably one of the better examples The benefits and drawbacks of the architectures should be pretty clear I want to talk about something else though the strategy We build monoliths since they are easier to get started with Microservices usually rise out of necessity when our system is already in production However there are a lot of questions that arise when deciding when to do the migration or not how do you decide the boundaries of a service How do you verify the self healing properties of your microsevice architecture This is especially challenging with the distributed aspect of the service mesh We need a view of the entire application as parts of it break off Our goal is to keep the conveniences we had in the legacy monolith while avoiding the tight coupling that came with the territory In this article I will outline some practical approaches you can use while carrying out this migration DecisionI m strongly in the “start with a monolith camp it should be a modular monolith so we can easily break it down There s a myth of a monolith as a “block of interconnected code This is far from the case most monoliths use the capabilities of modern programming languages e g packages modules etc to separate the various pieces Calls between the various parts of a modular monolith occur through clearly defined interfaces or event buses My pro monolithic applications stance probably stems from my Java background as Java is particularly well suited to large monoliths The point in which you would split a codebase would be radically different depending on your architecture language problem domain etc How do you make an objective choice in this regard When is the perfect time to start a migration to microservices The most important pre requisite for a microservice architecture migration is separation of authorization If this isn t separated as an external service there s probably no room to move forward This is the hardest part of a microservice migration The nice thing about this is that you can take this step while keeping the monolith architecture If you can t perform that migration there s no point in moving forward Once this is done there are several other factors involved Team size as your team grows keeping cohesion is a challenge This is something we can easily benchmark by reviewing the growth of the team Keep an eye on the speed of onboarding and other metrics such as time to issue resolution These are probably the best metrics for project complexity Inter dependence the benefit of microservices might be a hindrance if the project is deeply inter dependent and doesn t have clear separation lines Some projects are inherently deeply intermingled and don t have a clean separation of the parts Pay attention to transactional integrity between different modules Features such as transaction management can t carry between microservices If you have a system that must be reliably consistent such as a banking system that needs to be consistent at all times the boundaries of the transaction must reside within a single service These are the types of things that can make the migration process especially difficult Testing you can t undergo such an effort without a significant amount of module specific tests and a big suite of integration tests Reviewing the test code will tell you more about your readiness than any alternative means Can you logically test a module in isolation Once you have a sense of those you can start estimating the benefit you might get from the monolith to microservices migration Where Do We Start Assuming the monolithic code is already relatively modular and supports SSO Single Sign On we can pick any module we want How do we know which one will have the best return on our investment of time and effort Ideally we want to target the parts that will give us the most benefit and would be easiest to migrate Look at the issue tracker version control which module is the one most prone to failure Check modularity which module is smallest and least interdependent Can the data be cleanly separated it s best to start with lower hanging fruitProfile your application which module is most expensive and can benefit from scaling These things are simple enough when running locally but often the behavior of the application in production is vastly different to its local or staging environment In those cases we can use developer observability tools such as a runtime line counter to evaluate usage We need to strike a balance of benefit and utility when we choose the module to break out Avoiding the Tiny Monolithic ArchitecturePeople often recite the tenants of microservices but proceed to build something that doesn t follow the general rules “Self healing is the most blatant example Decoupling the pieces of a monolith into a microservice application is remarkably hard We need to isolate the pieces and make sure that everything functions reasonably well at scale Or worse during downtime How can a system survive when a deployable service is down How can we test something like that One of the biggest problems in such an architecture is the scale of deployment We wrap individual services in a discovery system and API gateways and circuit breakers to enable the healing properties Often API gateways and similar services are SaaS based solutions but even if we deploy them ourselves accurately replicating our production is hard Typical complexities include coded URLs into the gateways and into the actual code Accidentally going around the gateway and directly to the servers or underlying infrastructure These are subtle things that are hard to detect in legacy code and large systems Because of this complex topology properly testing the healing behavior is nearly impossible when working locally Any result you get would be inaccurate because of the vastly different deployment logistics But we can t bring down a production microservice just to prove a point Right That s one of the enormous benefits of microservices architecture In the discovery code we can add a special case that provides a “dummy or failed microservice for a specific user The problem is that the symptoms might be hard to verify as a “self healing service will appear as if it s functioning In that case we can use logs or snapshots to verify that the right code is reached and the module is indeed disconnected E g we can simulate the unavailability of an API using most API gateways Then we can check that the other services work as expected by invoking a call and verifying that a circuit breaker is triggered and results are still arriving Our system seems healed But maybe some user code invoked the webservice directly and effectively circumvented the API gateway How do you verify that everything works from cache and uses the fallback that you expected This is where logs and snapshots come in We can add them in the backend API and also in the broken off service to verify that the results that we got are indeed the results from the gateway cache Rinse RepeatThis process is most challenging when we break off the first microservice out of monolithic applications As we break additional pieces it typically becomes easier until the entire monolith is gone But there are challenges along the way Initially we pick an achievable goal which is easier As we move forward we run into harder challenges and need to decide on boundaries for a service that might be less than ideal The problem is that we often need to take these steps based on intuition But when we created the modules we might have used logical separation instead of interdependencies As a result two modules might have deep dependencies and might not make sense as a microservice Splitting them in a different location or even bundling them together might make more sense As an example we might have an accounting system which manages multiple accounts A logical separation might move the code that transfers funds between accounts into a separate module But that would make things very difficult In an accounting system money must arrive from one account and move to another it can never “vanish As we add money to one account we must subtract it from the other and both need to happen in a single transaction A trivial workaround might be to do both the deduction and the moving of the funds in a single request However that won t solve the generic problem since money can be withdrawn from one account and divided into multiple accounts Doing this in multiple small operations can cause side effects This is doable but personally I would keep the core accounting logic together with the accounts system in such a case Some of those inter dependencies can be inferred from the code and refactored away Converted to messaging and asynchronous calls Using a messaging service is one of the most effective ways to decouple Many languages and platforms support a module barrier between the various parts This lets us isolate an entire module from the rest of the application and limit the interaction to a narrow interface By raising such a barrier we can use the compiler and IDE to enforce module restrictions FinallyBreaking down monolithic applications is always challenging It takes time and effort to isolate the business logic into the correct domains The communication overhead and division of features to a specific service are the components that make the difference in such a process There are no delivery guarantees and testing is even harder Production is a completely unique environment from development because of the API gateways proxy settings discovery etc A successful migration of legacy code is seamless to the customer For us it changes the dynamics completely Delivery is different verifying that a deployment is successful is far more challenging than it is with a monolithic application The user experience is similar when everything works but how do we verify that That s where tooling comes in we can use developer observability tooling logs counters logs to verify that even with production failures the healing across service boundaries is still working This is no trivial feat since loose coupling is only the first step Behavior during different forms of failure can only be tested in production and we don t want to fail just so we can make a point	2022-08-29 07:35:23
海外TECH	DEV Community	Celebrating 3,000+ GitHub Stars 🎉	https://dev.to/seaql/celebrating-3000-github-stars-3pic	Celebrating GitHub Stars We are celebrating the milestone of reaching GitHub stars across all SeaQL repositories This wouldn t have happened without your support and contribution so we want to thank the community for being with us along the way The JourneySeaQL org was founded back in We devoted ourselves into developing open source libraries that help Rust developers to build data intensive applications In the past two years we published and maintained four open source libraries SeaQuery SeaSchema SeaORM and StarfishQL Each library is designed to fill a niche in the Rust ecosystem and they are made to play well with other Rust libraries Oct SeaQL foundedDec SeaQuery first released Apr SeaSchema first releasedAug SeaORM first releasedNov SeaORM reached Dec SeaQuery reached Dec SeaSchema reached Apr SeaQL selected as a Google Summer of Code mentor organizationApr StarfishQL first releasedJul SeaQuery reached Jul SeaSchema reached Jul SeaORM reached Aug SeaQL reached GitHub stars Where re We Now We re pleased by the adoption by the Rust community We couldn t make it this far without your feedback and contributions Open source projects Startups using SeaQL Dependent projects‍‍‍ Contributors Merged PRs amp resolved issues GitHub stars️ Discord members️ Lines of Rust Downloads on crates io as of Aug Core MembersOur team has grown from two people initially into four We always welcome passionate engineers to join us Chris Tsang Founder Led the initial development and maintaining the projects Billy Chan Founding member Contributed many features and bug fixes Keeps the community alive Ivan Krivosheev Joined in Contributed many features and bug fixes most notably to SeaQuery Sanford Pun Developed StarfishQL and wrote SeaORM s tutorial Special ThanksMarco Napetti Contributed transaction streaming and tracing API to SeaORM nitnelave Contributed binder crate and other improvements to SeaQuery Sam Samai Developed SeaORM s test suite and demo schema Daniel Lyne Developed SeaSchema s Postgres implementation Charles Chege Developed SeaSchema s SQLite implementation SponsorsIf you are feeling generous a small donation will be greatly appreciated A big shout out to our sponsors Émile FugulinDean SheatherShane SvellerSakti Dwi CahyonoUnnamed SponsorUnnamed Sponsor ContributorsMany features and enhancements are actually proposed and implemented by the community We want to take this chance to thank all our contributors What s Next We have two ongoing Summer of Code projects to enrich the SeaQL ecosystem planning to be released later this year In the meantime we re focusing on improving existing SeaQL libraries until reaching version we d love to hear comments and feedback from the community If you like what we do consider starring commenting sharing contributing and together building for Rust s future	2022-08-29 07:03:42
海外科学	NYT > Science	Secret Data, Tiny Islands and a Quest for Treasure on the Ocean Floor	https://www.nytimes.com/2022/08/29/world/deep-sea-mining.html	Secret Data Tiny Islands and a Quest for Treasure on the Ocean FloorMining in parts of the Pacific Ocean was meant to benefit poor countries but an international agency gave a Canadian company access to prized seabed sites with metals crucial to the green energy revolution	2022-08-29 07:02:43
医療系	医療介護 CBnews	【200字で再確認】22年度診療報酬改定・経過措置9月末の巻（8)-地域包括ケア病棟入院料の病床種別による評価の見直し	https://www.cbnews.jp/news/entry/20220829132324	診療報酬	2022-08-29 17:00:00
医療系	医療介護 CBnews	京都府・市が薬物依存症の専門医療機関を共同選定-上京区の診療所、ギャンブル等依存症も	https://www.cbnews.jp/news/entry/20220829161807	依存症専門医療機関	2022-08-29 16:30:00
金融	JPX マーケットニュース	[東証]上場廃止に係る猶予期間入り：（株）極楽湯ホールディングス	https://www.jpx.co.jp/news/1021/20220829-01.html	上場廃止	2022-08-29 17:00:00
ニュース	@日本経済新聞 電子版	米国の農地価格が最高値　穀物高や食料危機でマネー流入 https://t.co/R0GeQGhy0F	https://twitter.com/nikkei/statuses/1564151780682104832	食料	2022-08-29 07:23:39
ニュース	@日本経済新聞 電子版	ウクライナ工作員が背後から奇襲、ロシア軍をかく乱(FT) https://t.co/JUQVGFzxQq	https://twitter.com/nikkei/statuses/1564149787695652865	背後	2022-08-29 07:15:44
ニュース	@日本経済新聞 電子版	日経、米S&Pと提携　アジア企業情報の発信強化 https://t.co/OhEtC8MVwe	https://twitter.com/nikkei/statuses/1564147494145048576	sampampp	2022-08-29 07:06:37
海外ニュース	Japan Times latest articles	Yuta Watanabe signs deal with Nets	https://www.japantimes.co.jp/sports/2022/08/29/basketball/nba/watanabe-to-nets/	agent	2022-08-29 16:40:40
海外ニュース	Japan Times latest articles	Akane Yamaguchi wins second straight world title	https://www.japantimes.co.jp/sports/2022/08/29/more-sports/yamaguchi-win-world-title/	Akane Yamaguchi wins second straight world titleAkane Yamaguchi became the first Japanese to win back to back women s singles badminton world championships on Sunday beating China s Tokyo Olympic gold medalist Chen Yufei	2022-08-29 16:32:30
海外ニュース	Japan Times latest articles	Rory McIlroy rallies to win Tour Championship and FedEx Cup	https://www.japantimes.co.jp/sports/2022/08/29/more-sports/golf/mcilroy-rally-tour-championship/	championship	2022-08-29 16:22:26
ビジネス	ダイヤモンド・オンライン - 新着記事	【社説】米軍艦船の台湾海峡通過 - WSJ発	https://diamond.jp/articles/-/308828	台湾海峡	2022-08-29 16:12:00
北海道	北海道新聞	ＩＡＥＡ、ザポロジエへ　ロシア、原発立地の市に攻撃か	https://www.hokkaido-np.co.jp/article/723312/	事務局長	2022-08-29 16:24:00
北海道	北海道新聞	北電が自由料金プランで値上げ　月額７００円程度	https://www.hokkaido-np.co.jp/article/723311/	一般家庭	2022-08-29 16:22:00
北海道	北海道新聞	道南で３３０人感染　新型コロナ	https://www.hokkaido-np.co.jp/article/723307/	新型コロナウイルス	2022-08-29 16:21:01
北海道	北海道新聞	オリンパス、顕微鏡事業を売却　４２７６億円、医療に集中	https://www.hokkaido-np.co.jp/article/723310/	顕微鏡	2022-08-29 16:18:00
北海道	北海道新聞	１日から通常運行再開　ジェイ・アール北海道バス	https://www.hokkaido-np.co.jp/article/723305/	新型コロナウイルス	2022-08-29 16:11:00
ニュース	Newsweek	ウクライナ議会に親台湾の会派が発足、中国に絶望	https://www.newsweekjapan.jp/stories/world/2022/08/post-99490.php	私たちが中国に望むのは、ロシアを助けないことだけだ」議会のこのような重要な動きを、ゼレンスキーと大統領府が承認したのかどうかは明らかにされていない。	2022-08-29 16:42:17
マーケティング	MarkeZine	WACULが「LTV最大化支援パッケージ」の提供へ　ローソンや読売新聞東京本社で実施	http://markezine.jp/article/detail/39844	wacul	2022-08-29 16:30:00
IT	週刊アスキー	鰻の量が約4倍！　名代 宇奈とと、期間限定「うなめしギガ増し+」9月5日から	https://weekly.ascii.jp/elem/000/004/103/4103330/	名代宇奈とと	2022-08-29 16:50:00
IT	週刊アスキー	アクションシューティング『ネクロムンダ：ハイヤードガン』のトレーラーが公開！明日の8月30日には先行生配信も	https://weekly.ascii.jp/elem/000/004/103/4103334/	playstation	2022-08-29 16:50:00
IT	週刊アスキー	本格ストラテジーRPG『剣と魔法と学園クエスト。』の製品版に引継ぎ可能な無料体験版が配信中！	https://weekly.ascii.jp/elem/000/004/103/4103329/	acquire	2022-08-29 16:35:00
IT	週刊アスキー	写真撮影もOK！　コニカミノルタプラネタリアYOKOHAMAで本編上映前にウェルカム映像「ハロウィンウェルカムドーム」を上映	https://weekly.ascii.jp/elem/000/004/103/4103315/	yokohama	2022-08-29 16:20:00