投稿時間:2022-12-07 17:30:52 RSSフィード2022-12-07 17:00 分まとめ(32件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
IT	ITmedia 総合記事一覧	[ITmedia PC USER] マウス、第12世代CPU搭載17.3型ノートPC　HDMIに加えディスプレイ出力可能USB Type-C搭載	https://www.itmedia.co.jp/pcuser/articles/2212/07/news144.html	displayportaltmode	2022-12-07 16:16:00
IT	ITmedia 総合記事一覧	[ITmedia ビジネスオンライン] 約9割が「マッチングアプリ疲れ」に悩んでいる　疲れの原因は？	https://www.itmedia.co.jp/business/articles/2212/07/news145.html	itmedia	2022-12-07 16:14:00
TECH	Techable（テッカブル）	営業マンの立ち合い不要！ 自分のペースで“完全セルフ内見”ができる「スマビュー」	https://techable.jp/archives/187164	不動産会社	2022-12-07 07:49:43
AWS	AWS Japan Blog	Amazon EKS クラスターでアドオンを活用し、Amazon EBS スナップショットを永続ストレージに使用する	https://aws.amazon.com/jp/blogs/news/using-amazon-ebs-snapshots-for-persistent-storage-with-your-amazon-eks-cluster-by-leveraging-add-ons/	hotsforpersistentstorage	2022-12-07 07:40:14
python	Pythonタグが付けられた新着投稿 - Qiita	PytestでMockを使う時の備忘録	https://qiita.com/Mochieyan/items/a6a2c017b2719e180589	gtpipinstallpytestpytes	2022-12-07 16:50:36
python	Pythonタグが付けられた新着投稿 - Qiita	1-3 始めてのコミットと、改行コードエラーの克服(warning: LF will be replaced by CRLF in)(スナガクのポートフォリオ作成日記)	https://qiita.com/sean-sunagaku/items/cc188bc88a6eace842ea	django	2022-12-07 16:44:54
python	Pythonタグが付けられた新着投稿 - Qiita	【Azure】Auto MLで作成したモデルをPythonからデプロイする方法	https://qiita.com/kkawano_neko/items/2593a58560ae499bf3e8	oswindowsnvidiagtxtigbra	2022-12-07 16:32:32
js	JavaScriptタグが付けられた新着投稿 - Qiita	Notion APIでデータベースが変更されたか監視してみる #notion	https://qiita.com/n0bisuke/items/5a30538ad02347be901a	notion	2022-12-07 16:37:12
js	JavaScriptタグが付けられた新着投稿 - Qiita	JavaScript（jQuery）の基礎問題3選　中級編	https://qiita.com/ninja0408/items/42630bd87a13e343ed9e	javascript	2022-12-07 16:14:52
js	JavaScriptタグが付けられた新着投稿 - Qiita	HTMLを書き換える	https://qiita.com/masatom86650860/items/6b485ec9941553480aec	ltpgtlts	2022-12-07 16:00:54
Ruby	Rubyタグが付けられた新着投稿 - Qiita	チェリー本読破までの自分メモ【2章】	https://qiita.com/haruki_kobayashi/items/b09c93fccc1ad9d578b3	ileencordingrescueundefre	2022-12-07 16:23:21
Docker	dockerタグが付けられた新着投稿 - Qiita	go言語(echo)APIサーバーの構築手順(+reactとの接続設定手順)	https://qiita.com/kubota_ndatacom/items/65af3f33734dc12f102e	docker	2022-12-07 16:56:24
golang	Goタグが付けられた新着投稿 - Qiita	go言語(echo)APIサーバーの構築手順(+reactとの接続設定手順)	https://qiita.com/kubota_ndatacom/items/65af3f33734dc12f102e	docker	2022-12-07 16:56:24
Azure	Azureタグが付けられた新着投稿 - Qiita	【Azure】Auto MLで作成したモデルをPythonからデプロイする方法	https://qiita.com/kkawano_neko/items/2593a58560ae499bf3e8	oswindowsnvidiagtxtigbra	2022-12-07 16:32:32
技術ブログ	Developers.IO	[レポート] 『CM re:Growth 2022 〜技術者による技術者のためのAWS re:Invent ふりかえり勉強会〜』に参加しました #reinvent #cmregrowth	https://dev.classmethod.jp/articles/report-cm-regrowth-2022/	awsreinve	2022-12-07 07:53:45
海外TECH	DEV Community	How to choose the right API Style and Technology	https://dev.to/apisix/how-to-choose-the-right-api-style-and-technology-5fb7	How to choose the right API Style and TechnologyAPIs are an essential design element in any software architecture that interconnects components digitally and allows various systems and devices to communicate easily with each other When we built a new API initially we think about the API design and how the API interacts with the external world by using which style and technology In this post we ll go through the most popular API styles and look at very common questions like “How to decide on the right API style and which technology to choose for a style and provide practical scenarios where an API Gateway can supplement their weaknesses No best API styleNote that there is no single best way of approaching all problems in a software design The same is true with API styles There is no “best API style They all have strengths and weaknesses that depend on the problem that is being addressed Let s go through each style and understand the main properties interaction model and limitations Resource Hypermedia Query Tunnel Event Based Then we pick a suitable style and technology that works well for the given style Resource styleThe resource style as the name implies is resource oriented Many of today s APIs use the resource style and this can be easily verified by the popularity of OpenAPI which is the most popular way of describing resource oriented APIs In this style the main focus is on which resources to expose to consumers so that they can interact with these resources The resource in this context can be assumed to be similar in scope to what you would have in resources such as web pages when designing a website The idea of resources gives us a great way to expose the relevant aspects of an API s functionality and at the same time allows us to hide implementation details behind the resources There can be resources for persistent concepts such as products product categories and customer information Also there can be resources for process oriented concepts such as ordering products or selecting a shipping option For the resource style there is REST as an architectural pattern but that doesn t mean that REST gives you concrete technologies For REST choosing HTTP as a protocol is a preferred choice and for the representation format it s probably safe to say that JSON by far overshadows any other representation such as the XML that was popular before JSON When a client request is made through a RESTful API it transfers a representation of the state of the resource to the endpoint In developing REST APIs with many collections of resources that are integrated with backend HTTP endpoints you can use API Gateway features to help you with all aspects of the API lifecycle from creation to monitoring your production APIs API Gateway REST APIs use a request response model where a client sends a request to a service and the service responds back synchronously You can read more about how to choose the right API Gateway for your REST APIs Resource style lacks is the ability to better represent workflows across these resources The hypermedia style adds a key component to the resource style to address resource linking concerns Hypermedia StyleJust as on the web the most important paths across resources can be navigated by simply using links between them instead of having to know each resource individually and enter its URI in the browser s address bar the hypermedia style does the same but for the resources of an API On the web humans read pages and then decide which link to follow For hypermedia APIs this decision is usually made by a machine This means that links need to have machine readable labels so that machines can identify the available options and then make a choice These labels are conceptually similar to the text of a link that humans click on web pages but the labels are represented in the machine readable representation of resources which nowadays in many cases will be JSON In a hypermedia API where you can “navigate across resources using the links between them Resource style sometimes requires HATEOAS HATEOAS is an abbreviation for Hypermedia As The Engine Of Application State HATEOAS is the aspect of REST which allows for dynamic resource routing There are two main advantages of hypermedia APIs over resource style APIs They provide all the links necessary in the previous response to choose the available resources in the next step Links span resources and it doesn t matter whether these resources are provided by one API or several APIs All of this sounds very positive because the Hypermedia style provides the necessary knowledge for API consumers to discover your API themselves and what resources you offer to them You can build a hypermedia driven REST service with any programming language and framework used in your stack For example using ASP NET Web API or Spring Boot Rest API However the ease of browsing may increase the risk of the learner skipping through the materials and getting fragmented information Also since data is shared between client and server it can also lead to “chatty APIs that require a number of interactions for the client to access all required information and what if API endpoints are exposed by multiple backend services microservices and serverless APIs The latter challenge can be solved by leveraging an API Gateway with a response aggregator composer functionality Moreover API consumers do not know what they want from the very beginning and it is more efficient to write a query to get exactly what they want as is offered by the query style in the next section Query StyleThe query style is rather different from the resource and hypermedia styles because it provides a single entry point to access a potentially large set of resources The idea of the query style is that these resources are managed in a structured form by the API provider This structure can be queried and the response contains the query results At some level this can be seen as similar to how databases work They have an underlying data model for the data they store and a query language that can be used to select and retrieve parts of that data One benefit of the query style is that each consumer can request exactly what they want This means that with a well constructed query it may be possible to combine results that would have required numerous requests in resource hypermedia APIs For example instead of sending several HTTP requests to different endpoints you can POST a single “query for all you need For the query style it s probably fair to say that GraphQL by now is by far the most popular choice when it comes to building single page applications SPAs It is a language for querying databases from client side applications The big advantage that GraphQL has is that it plugs into a JSON based ecosystem While GraphQL does not use JSON for queries it returns results in JSON which make it easy to process in JSON focused environments Although query style has negligible disadvantages over its advantages we can identify one of them is the query complexity API consumers need to have a good understanding of the underlying data and query models so that they know how to use the query API properly and make efficient requests to avoid recursion or getting too many nested resources Also it is more complicated to implement a simplified cache with GraphQL than implement it in resource style because REST APIs have multiple endpoints they can leverage native HTTP caching to avoid re fetching resources Another problem with GraphQL is rate limiting where you say we allow only this amount of requests Nevertheless the last two mentioned downsides caching and rate limiting can be developed by introducing the API Gateway between the client and data store to win in this situation For example an open source Apache APISIX API Gateway has the matching ability to recognize GraphQL syntax By efficiently matching GraphQL statements carried in requests it can filter out abnormal traffic to further apply rate limiting policies and improve system performance with its caching capability Tunnel StyleIn tunnel style an API is a collection of functions that can be invoked remotely APIs become a simple extension of what is in a local programming scenario where all exposed procedures are available as APIs The tunnel style is convenient for developers because it can take very little effort to create APIs A common technique used in this style is the Remote Procedure Call method RPC is a request response protocol where a client sends a request to a remote server to execute a specific procedure and then the client receives a response back However RPC APIs are much more difficult to maintain and update than REST APIs so again RPC APIs aren t used as much in modern API development gRPC is an efficient tunnel style RPC implementation and is well suited for distributed systems It has SDKs for many languages and platforms so it can be used widely for communication across platforms and languages gRPC is super fast and efficient because it uses Protocol Buffers protobufs to serialize and deserialize the HTTP standard for optimized binary transfers and bidirectional streaming to avoid long polling and blocking HTTP calls Tools can be used to expose procedures as APIs in which case a lot of the task of “creating the API can be automated There still should be some management layer for securing the APIs but that can be addressed by using a component such as an API gateway and its gRPC proxying ability to convert payloads from one format to another over the same transport from REST to gRPC or vice versa if different API protocols are used in the system Event Based StyleIn the event based style the API provider creates events that are then delivered to consumers of the API instead of consumers requesting something from the provider Consuming applications expect to be informed of any change of state on a specific record or records on API There are many ways and technology options to consider when implementing an event driven API For example we explored how to build Event Driven APIs with Webhook and API Gateway in this post Another approach is that event consumers connect to a message broker that decouples them from event producers The message broker takes care of managing events and consumers must subscribe to certain event types so that the broker can make sure that events of this type are delivered to subscribers In this case the architecture is much more centered around the delivery broker and all event producers and consumers are connected to this message broker In this case a good technology to consider can be Kafka which is Kafka is highly scalable and resilient Some drawbacks of choosing an event based style are it takes more time to implement compared to other styles it may trigger multiple duplicate messages across different services if the style is not properly applied error handling and troubleshooting can be challenging without installing amp configuring third party tools to monitor the event flow effectively However you can put the API Gateway in front of even driven APIs when observing modern applications with its simple built in integration to several monitoring platforms Wrapping UpAs we reviewed styles were the foundation of popular approaches and technologies such as REST OpenAPI HTTP gRPC GraphQL and Kafka The most important lesson to learn about these API styles is that there is no “best style When it comes to choosing an API style it all boils down to the following classes a problem consumers and context Problem As discussed in the individual styles each style has a certain focus and certain strengths Thus it is important to think about the problem that is addressed with an API Consumer Every API is built for consumption and thus an API s consumers always should be an important design aspect Since APIs ideally are reused it s not always possible to plan for all consumers and their constraints but it makes sense to design with at least some consumers in mind and to make assumptions about others Context Most APIs are part of an API landscape That landscape can have a different audience and scope depending on whether the API is meant for internal partner or public use Ultimately the style that you and your team are more familiar with and easier to build might be a good fit for your project Sometimes we need to use different styles together in one software project Related resources➔API fundamentals ➔API Styles SOAP REST RPC GraphQL and more Recommended content ➔Read the blog posts How to build Event Driven APIs with Webhook and API Gateway most common use cases of an API Gateway How to choose the right API Gateway A poor man s API Community️Join the Apache APISIX Community Follow us on TwitterFind us on Slack	2022-12-07 07:35:53
医療系	医療介護 CBnews	「かかりつけ医機能」年内結論-全世代型会議「足元の課題」	https://www.cbnews.jp/news/entry/20221207163242	医療改革	2022-12-07 16:45:00
海外ニュース	Japan Times latest articles	Ruthless England sack Eddie Jones nine months from Rugby World Cup	https://www.japantimes.co.jp/sports/2022/12/07/rugby/eddie-jones/	Ruthless England sack Eddie Jones nine months from Rugby World CupJones future was in the balance following a recent Autumn series where a lone win over Japan and fortunate draw with New Zealand were bookended	2022-12-07 16:16:23
ニュース	BBC News - Home	China rolls back strict Covid rules after protests	https://www.bbc.co.uk/news/world-asia-china-63855508?at_medium=RSS&at_campaign=KARANGA	centres	2022-12-07 07:12:59
ニュース	BBC News - Home	UK weather: People urged to heat main rooms as cold snap begins	https://www.bbc.co.uk/news/uk-63879870?at_medium=RSS&at_campaign=KARANGA	advise	2022-12-07 07:03:08
ニュース	BBC News - Home	German raids target group who plotted coup	https://www.bbc.co.uk/news/world-europe-63885028?at_medium=RSS&at_campaign=KARANGA	german	2022-12-07 07:39:39
ニュース	BBC News - Home	Syria camps: Relatives of Islamic State group 'stuck in limbo'	https://www.bbc.co.uk/news/world-middle-east-63879028?at_medium=RSS&at_campaign=KARANGA	countries	2022-12-07 07:44:30
ニュース	Newsweek	ロシア領内深くの基地を襲ったのはウクライナの国産ドローンか	https://www.newsweekjapan.jp/stories/world/2022/12/post-100289.php	ロシア領内深くの基地を襲ったのはウクライナの国産ドローンか破壊されたロシアの爆撃機のように見える画像が、ソーシャルメディアで拡散されている。	2022-12-07 16:52:14
マーケティング	MarkeZine	データで見るZ世代のInstagram利用、2022年の動向は？【Instagram調査】	http://markezine.jp/article/detail/40760	instagram	2022-12-07 16:15:00
IT	週刊アスキー	5種ブレンドチーズを使用！　とんかつ新宿さぼてん「たっぷりチーズのヒレかつ」を販売中	https://weekly.ascii.jp/elem/000/004/116/4116409/	販売中	2022-12-07 16:45:00
IT	週刊アスキー	2週間限定で50％オフ！Switch『ルーンファクトリー5』がセールを開始	https://weekly.ascii.jp/elem/000/004/116/4116455/	nintendo	2022-12-07 16:40:00
IT	週刊アスキー	「アイカツ！10th STORY ～未来へのSTARWAY～×JOYSOUND直営店コラボキャンペーン」！　JOYSOUND新宿西口店にカラオケコラボルームをオープン	https://weekly.ascii.jp/elem/000/004/116/4116405/	joysound	2022-12-07 16:30:00
IT	週刊アスキー	TP-Link、Wi-Fi 6E対応トライバンドメッシュルーター「Deco XE75」	https://weekly.ascii.jp/elem/000/004/116/4116449/	通信速度	2022-12-07 16:30:00
IT	週刊アスキー	さくらインターネット、水中調査を自動化する水上ドローンを試作	https://weekly.ascii.jp/elem/000/004/116/4116450/	実証実験	2022-12-07 16:30:00
IT	週刊アスキー	Discord、絵文字がコミュニケーションに与える効果についての調査結果を発表	https://weekly.ascii.jp/elem/000/004/116/4116421/	discord	2022-12-07 16:20:00
マーケティング	AdverTimes	【人事】電通（2023年1月1日付、2月1日付）	https://www.advertimes.com/20221207/article406061/	電通	2022-12-07 07:52:14
マーケティング	AdverTimes	受験生にしか見えない広告「ZONe ENERGY」が赤シートを活用したメッセージで応援	https://www.advertimes.com/20221207/article406054/	youtuber	2022-12-07 07:23:39