投稿時間:2021-09-20 04:13:22 RSSフィード2021-09-20 04:00 分まとめ(16件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
AWS	lambdaタグが付けられた新着投稿 - Qiita	URLパラメータで指定したEC2の起動・停止	https://qiita.com/hayayu0/items/673c57952b8665e9dd6d	URLパラメータで指定したECの起動・停止最小限の手順でサクッと構成したい「ECの起動とか停止とかをURLアクセスでできないかね。	2021-09-20 03:22:38
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	JavaScript: forEachで作った3つめのボタンだけ他と違う属性値をつけたいです	https://teratail.com/questions/360366?rss=all	JavaScriptforEachで作ったつめのボタンだけ他と違う属性値をつけたいです前提・実現したいことJavaScriptでボタンをつ作り、つ目のボタンだけ別のイベントリスナーにレンダリングするために別のsetAttributeをつけたいのです。	2021-09-20 03:21:22
AWS	AWSタグが付けられた新着投稿 - Qiita	URLパラメータで指定したEC2の起動・停止	https://qiita.com/hayayu0/items/673c57952b8665e9dd6d	URLパラメータで指定したECの起動・停止最小限の手順でサクッと構成したい「ECの起動とか停止とかをURLアクセスでできないかね。	2021-09-20 03:22:38
golang	Goタグが付けられた新着投稿 - Qiita	値レシーバとポインタレシーバの違いについての備忘録（new UserとUser{}を使った場合について）	https://qiita.com/t0m0_sun/items/ea2e9c36518a842b0bcb	値レシーバとポインタレシーバの違いについての備忘録newUserとUserを使った場合についてGo初心者で躓いたのでメモとして残します。	2021-09-20 03:08:42
海外TECH	DEV Community	The frontend Landscape – Different Architectures	https://dev.to/learnersbucket/the-frontend-landscape-different-architectures-m2j	The frontend Landscape Different ArchitecturesVisit learnersbucket com If you are preparing for your JavaScript interview You will find DSA System Design and JavaScript Questions Web development Frontend has come a long way from its inception There was a time when static websites were designed using tables for layouts and some styles around it which were only built for desktops But today web apps can be created with complex user interfaces and for cross devices SAAS which are built as web applications allow us to stream movies and music on demand order pizza handle bank processes even book a cab and do more and more things which makes our life easier Over time to create apps which provide so much capabilities security flexibility and also are manageable and scalable organizations experimented with multiple architectures As a developer architect or tech lead when we start a fresh project we need to decide which architecture we will be following There are an array of options to choose from but not all of them are fit for every job We need to understand the challenges we will face along the way to make the right decision for our projects Let us explore the current architectures which are available to us for the frontend development Server Side Application or Multi Page Application Server side rendered websites were a thing back when they had not become the web apps All they did was display text and images and very minimal interactivity These websites were built with server side rendering which means the HTML was generated on the server along with all the data and it is returned to the browser and then the browser used to render it When a page refreshes or the user navigates to a different page the servers used to send new HTML This will be repeated every time if your browser does not have the cached version of that page As each time when you make the request to the server the server regenerates the whole HTML even if we are only expecting for minor changes this hampers the speed of the website Though the speed of the website varies on many factors like your internet speed location of the server number of users who are trying to access the site etc For small websites these issues are negligible but for modern websites which have more than thousands of lines of code as well as complex logics will take more time for processing Now imagine when you browse through the website and you have to keep waiting for each web page which you visit But the good thing about server side rendering is that it is great for SEO Your content is present before you get it so search engines are able to index it and crawl it just fine Single Page Application Client Side Rendering In the current time SPAs are the most used implementations In single page applications client side rendering is used The browser loads the initial page from the server along with the scripts frameworks libraries app code and stylesheets required for the whole app When the user navigates to other pages a page refresh is not triggered The URL of the page is updated via the HTML History API New data required for the new page usually in JSON format is retrieved by the browser via AJAX requests to the server The SPA then dynamically updates the page with the data via JavaScript which it has already downloaded in the initial page load This model is like how native mobile apps work Using SPAs has many advantages like the whole application code is downloaded just once on initial load and then the entire application logic is available throughout the user session As the SPAs only deal with the client side logic it can be developed independently and to get the data it communicates with APIs by exchanging data with the persistent layer backend or server side The client side and server side are decoupled which means that we can independently develop new clients for different platforms e g mobile chatbots smart watches without having to modify the server code The client can also be developed using a new tech stack As we don t have to repeatedly fetch the same resources again and again we have to make fewer HTTP requests also the payloads size is smaller which is faster to process Because both client and server side are decoupled which means they are smaller in size and faster to download interpret and process All these features enhance the user experience and give an expression of what we usually have when we interact with a native application for mobile devices or desktop SPAs also allow us to decide how we are going to split the application logic between server and client We can have either “thick client and “fat server or “fat client and “thick server depending upon which type of problem we are addressing Majorly “thick client and “fat server is used as by keeping all the logic on the server we can use that across multiple clients that way if we update the logic on one platform it will be available on each client The bad thing about this is as the majority of the resources are fetched when the web app loads for the first time it can hamper the initial load time of the application majorly on devices with less processing power and slower networks There s an additional step to be done on your server which is to configure it to route all requests to a single entry point and allow client side routing to take over from there All the client side routing is managed internally using HTML history API As the pages in the SPAs are dynamically generated on the run time another disadvantage of using SPAs relates to search engine optimization SEO When a crawler tries to index your website it won t have an easy job indexing all the contents served by an SPA unless we prepare alternative ways for fetching it Another disadvantage of using SPAs is on the organizational side When the SPA is a large application being developed and maintained by coalted teams working on the same codebase could end up with a mix of approaches and decisions that could confuse team members Isomorphic applications Hybrid approach With the above two approaches we learned that server side rendering can be used to solve the SEO related issues and client side rendering can be used for performance optimization What if we could use both of them together and use the best of both to create faster web applications which are also very well SEO optimized Isomorphic or universal applications are web applications where the code between server and client is shared and can run in both contexts These web applications share code between server and client When you visit the web app for the first time the application is rendered on the server side using server side rendering techniques with Nodejs and then it is sent to the browser and displayed to the user here after whenever user navigates the web apps the pages are rendered on client side with JavaScript using SPA techniques The content is updated by consuming APIs and fetching data from them The complexity of this approach is majorly among the state management One way to solve this is to create and save the state on the server side and then provide this state to the browser The browser uses this state to bootstrap the SPA without this the user must wait for the server side page to render and wait more for the complete re render process in the browser To make the most out of this approach we can render the page with bare minimum things which is required to create the skeleton of the page such as inline CSS and few HTML content and minimum JavaScript so that browser can load it extremely fast and there after update the content as per requirement on the client side using JavaScript With these we can also solve the routing issue you can either render the pages complete on the server side or use the hybrid approach Use the server side rendering for initial view and then load an SPA where the server will do the macro routing that serves different SPAs each with its own routing system to navigate between views Isomorphic applications can suffer from the scalability problems if the web app is visited by a large number of users Having a right caching in place could solve this problem as pages are rendered on server side Micro Frontend ArchitectureMicro Frontend is a fairly new and emerging architecture which is inspired by the micro services architecture of backend development When multiple teams are involved in the development of a single application it becomes difficult to manage the code base and applications itself as multiple people will be touching the same code base This approach tends to solve this problem by splitting the application in different parts depending on the requirement and each of them would be developed independently which would be shipped as a single application The main idea behind this is to break down a monolithic codebase into smaller parts allowing to spread out the work among various teams whether collocated or distributed There are different approaches for architecturing a micro frontends application Certain architectural decisions have to be made upfront because they will cave the road for future decisions The decision majorly covers four key areas Defining different micro frontends Composing micro frontends Routing micro frontends Communicating between micro frontends You can decide multiple micro frontends for the same view or having one micro frontend per view and based on this we can split the application The application can be split horizontally or vertically In the horizontal split we split the views of the pages into multiple micro frontends and different teams will be responsible for the development of these views This approach provides great flexibility as certain micro frontends could be reused across different views but it also needs more discipline and governance to make sure we don t end up with large amounts of micro frontends In the vertical split we split the pages or module completely For example different teams will be responsible for the development of different modules like authentication streaming services search etc JAMSTackNowadays there s another new frontend architecture which is enjoying its success called JAMStack JavaScript APIs Markup Being a modern architecture JAMSTack helps to create fast and secure sites and dynamic apis with JavaScript APIs and pre rendered markup served without web servers In fact the final output is a static artifact composed of HTML CSS and JavaScript basically the holy trinity of frontend development which can be served directly using CDN as it doesn t require any server side technology to work The most simplest way of serving a JAMStack application is using Github pages for hosting the final result The primary advantages of these architectures are better performances cheaper infrastructure and maintenance considering they can be served directly by a CDN great scalability because static files are served higher security due to decrease of attack surface and easy integration with headless CMS JAMStack is a great companion for many websites we have to create especially considering the frictionless developer experience	2021-09-19 18:14:23
海外TECH	Engadget	US probe into Binance reportedly expands to investigate insider trading	https://www.engadget.com/binance-insider-trading-probe-184903656.html?src=rss	US probe into Binance reportedly expands to investigate insider tradingBinance is apparently facing more pressure from regulators over possible abuses at its cryptocurrency exchange Bloombergsources said US officials have expanded their probe of Binance to include possible insider trading and market manipulation The company hasn t been accused of wrongdoing but Commodity Futures Trading Commission investigators have reportedly inquired with potential witnesses about issues like the location of Binance servers and thus whether the US can pursue any cases The commission had previously launched an investigation into the sales of derivatives tied to cryptocurrencies It s reportedly looking for internal Binance data that might show sales of those derivatives to American customers breaking regulations that forbid those sales without registrations The Internal Revenue Service and Justice Department are also probing possible money laundering on the exchange There are no guarantees of action The CFTC and Justice Department have supposedly been investigating Binance for months and any decisions might take a while longer Not surprisingly Binance said it was above board A spokesperson told Bloomberg the exchange had a quot zero tolerance quot approach to insider trades as well as ethical codes and security guidelines to prevent those actions The company added that it fires offenders at a bare minimum The CFTC has declined to comment The heightened scrutiny of Binance if accurate would come as part of a larger US crackdown on cryptocurrencies Officials are concerned the lack of consumer protections including regulation might hurt customers who sign up for services expecting the same safeguards they have with conventional money In this case the focus is on accountability ーinsider trading could wreck valuable investments and erode trust in Binance and other crypto exchanges	2021-09-19 18:49:03
ニュース	BBC News - Home	Chelsea beat Spurs to extend unbeaten run & go joint top	https://www.bbc.co.uk/sport/football/58533942?at_medium=RSS&at_campaign=KARANGA	tottenham	2021-09-19 18:11:46
ニュース	BBC News - Home	Watch: Sunday Sportscene - Scottish Premiership highlights	https://www.bbc.co.uk/sport/av/football/58548395?at_medium=RSS&at_campaign=KARANGA	sportscene	2021-09-19 18:12:28
ビジネス	ダイヤモンド・オンライン - 新着記事	誰一人取り残さない、デジタル化が孤独に陥る高齢者を救う - 数字は語る	https://diamond.jp/articles/-/282498	国際比較	2021-09-20 03:50:00
ビジネス	ダイヤモンド・オンライン - 新着記事	金融庁が公表した「保険モニタリングレポート」を深読み解説 - ダイヤモンド保険ラボ	https://diamond.jp/articles/-/282551	保険会社	2021-09-20 03:45:00
ビジネス	ダイヤモンド・オンライン - 新着記事	「どんな」顧客が 「なぜ」買うのか？ まるわかりになる方法 - 売上最小化、利益最大化の法則	https://diamond.jp/articles/-/279535		2021-09-20 03:40:00
ビジネス	ダイヤモンド・オンライン - 新着記事	信用していた人に 陰で悪口を言われたら - 精神科医Tomyが教える １秒で元気が湧き出る言葉	https://diamond.jp/articles/-/280110	人気シリーズ	2021-09-20 03:35:00
ビジネス	ダイヤモンド・オンライン - 新着記事	【現役サラリーマンが株式投資で2億円】 損切りはできるだけ早く 利益確定はできるだけ遅く - 割安成長株で2億円 実践テクニック100	https://diamond.jp/articles/-/279756	【現役サラリーマンが株式投資で億円】損切りはできるだけ早く利益確定はできるだけ遅く割安成長株で億円実践テクニック定年まで働くなんて無理……ならば、生涯賃金億円を株式投資で稼いでしまおうそう決意した入社年目、知識ゼロの状態から株式投資をスタートした『割安成長株で億円実践テクニック』の著者・現役サラリーマン投資家の弐億貯男氏。	2021-09-20 03:30:00
ビジネス	ダイヤモンド・オンライン - 新着記事	関西在住なら一度は行っておきたい大阪一の神社 - 最強の神様100	https://diamond.jp/articles/-/282507	関西在住なら一度は行っておきたい大阪一の神社最強の神様「仕事運」「金運」「恋愛運」「健康運」アップ「のご利益」の組み合わせからあなたの願いが叶う神様が必ず見つかる八百万やおよろずの神様から項目にわたって紹介。	2021-09-20 03:25:00
ビジネス	ダイヤモンド・オンライン - 新着記事	資産総額1000億ドル超！ 世界屈指の投資家も実践する「専門知識・理論不要」の投資ルール - お金持ちがしている100の習慣	https://diamond.jp/articles/-/282531	専門知識	2021-09-20 03:20:00
ビジネス	ダイヤモンド・オンライン - 新着記事	揚げ物の面倒くささが、 劇的に解消される！ 3つの裏ワザ - ぽんこつ主婦の高見えごはん	https://diamond.jp/articles/-/282525	揚げ物の面倒くささが、劇的に解消されるつの裏ワザぽんこつ主婦の高見えごはんフォロワー約万人の料理インスタグラマー「ぽんこつ主婦」こと橋本彩さんの、おかず、おつまみ、副菜までレシピが掲載されたレシピ本「ぽんこつ主婦のいつもの食材でパパっと“高見えレシピ」が発売即重版に鶏むね肉、豚こま肉、サバ缶、卵、豆腐……など、お財布にも優しい食材で、おいしいのはもちろん、見映えもよい、ひとひねりしたレシピが超簡単に作れると話題です。	2021-09-20 03:15:00