投稿時間:2023-05-13 08:22:57 RSSフィード2023-05-13 08:00 分まとめ(30件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
AWS	AWS Media Blog	Automatically stop AWS Elemental MediaLive channels when no input is detected	https://aws.amazon.com/blogs/media/automatically-stop-aws-elemental-medialive-channels-when-no-input-is-detected/	Automatically stop AWS Elemental MediaLive channels when no input is detected­Introduction Media organizations and companies around the world use AWS Elemental MediaLive to deliver fast reliable and easy to use high quality live video streams without the need to manage infrastructure MediaLive streamlines live video operations by automating the configuration and management of ingest and encoding components for processing and delivery of live streams As of today there …	2023-05-12 22:17:32
海外TECH	DEV Community	How to deploy thin jars for better Docker caching	https://dev.to/robertmjohnson/how-to-deploy-thin-jars-for-better-docker-caching-4i44	How to deploy thin jars for better Docker cachingThere s plenty of advice around on how to create small Docker containers but what is often missed is the value of making your main application layer as small as possible In this article I m going to show you how to how to do this for a Java application and why it matters I m assuming that you re already familiar with Docker layer caching if not then the official docs will give you a good overview TL DR Instead of a single uberjar creation build step split it into two steps Copy dependencies to a lib folder e g via Maven s copy dependencies plugin Create a jar ensuring that the lib folder is added to its manifest The resulting docker image is much the same size but Docker can now cache the dependencies meaning that each subsequent build requires only a few extra kilobytes to store amp transfer rather than tens of MBs As an added benefit to splitting out the libraries it makes it easier to trim down our dependency jars such as removing useless alternate native libraries from JNI jars The downsides of uberjars for DockerFor a long time the standard way to deploy Java applications has been to deploy the humble uberjar which contains both our compiled code and all our application s dependencies Packaging Java apps in this made sense back when deploying an application meant transferring files to and from servers directly but it s not so useful in this age of containerized apps The reason for this is that for every single change to your application s source all those dependencies bundled inside the uberjar end up inside the same docker layer as your app and so each subsequent build effectively duplicates all of those third party dependencies within your Docker repository This is especially wasteful when we consider that your application code is what is going to change the vast majority of the time Suppose we have a nicely slimmed down dockerfile using an Alpine base image and even creating a tiny custiom JRE using jlink However suppose wehave a lot of dependencies MB in this example The key part of our Dockerfile will look likeWORKDIR appCMD java jar app my app jar COPY from app build app target my app SNAPSHOT jar with dependencies jar app my app jarAnd the docker layers created will look something like docker history my appIMAGE CREATED CREATED BY SIZE COMMENTdddc seconds ago COPY app target my app SNAPSHOT jar wit…MB buildkit dockerfile v lt missing gt About a minute ago CMD java jar app my app jar B buildkit dockerfile v lt missing gt About a minute ago WORKDIR app B buildkit dockerfile v lt missing gt About a minute ago RUN bin sh c apk add no cache libstdc …MB buildkit dockerfile v lt missing gt About a minute ago COPY javaruntime opt java openjdk buildk…MB buildkit dockerfile v lt missing gt About a minute ago ENV PATH opt java openjdk bin usr local sb…B buildkit dockerfile v lt missing gt About a minute ago ENV JAVA HOME opt java openjdk B buildkit dockerfile v lt missing gt months ago bin sh c nop CMD bin sh B lt missing gt months ago bin sh c nop ADD file abc…MBThe total image size is mb and after pushing the first version this takes up MB in my container registry On each subsequent build amp push of the new image we re pushing up a whole layer including all our dependencies all over again The push refers to repository registry digitalocean com my repo my app fbacec Pushing MB MBdadf Layer already existsabede Layer already existseeac Layer already existscdad Layer already existsSo after just pushes we ve already used up MB Splitting apart our dependencies from our application codeUsing Maven we simply replace any uberjar creating step s with the following steps to copy the dependencies to target lib create the jar containing our compiled code only but set up to look for its dependencies in lib lt plugins gt lt other plugins gt lt Copy runtime dependencies to lib folder gt lt plugin gt lt groupId gt org apache maven plugins lt groupId gt lt artifactId gt maven dependency plugin lt artifactId gt lt executions gt lt execution gt lt id gt copy dependencies lt id gt lt phase gt prepare package lt phase gt lt goals gt lt goal gt copy dependencies lt goal gt lt goals gt lt configuration gt lt outputDirectory gt project build directory lib lt outputDirectory gt lt includeScope gt runtime lt includeScope gt lt configuration gt lt execution gt lt executions gt lt plugin gt lt Creates the jar and configures classpath to use lib folder gt lt plugin gt lt groupId gt org apache maven plugins lt groupId gt lt artifactId gt maven jar plugin lt artifactId gt lt configuration gt lt archive gt lt manifest gt lt addClasspath gt true lt addClasspath gt lt classpathPrefix gt lib lt classpathPrefix gt lt mainClass gt path to MainClass lt mainClass gt lt manifest gt lt archive gt lt configuration gt lt plugin gt lt plugins gt All we need to do to our Dockerfile is add an extra build step to copy the libs WORKDIR appCMD java jar app my app jar COPY from app build app target lib app libCOPY from app build app target my app SNAPSHOT jar app my app jar NB It s important here that the lib directory copy happens before the jar copy if not then application updates would invalidate the layer cache for the lib directory thus losing the benefit Benefits of the splitUpon pushing the first version of this build there s not much difference to what we had before the overall image size stored in the repository is almost the same The benefit comes when we push subsequent new builds where we ve changed only our source code after builds where only our app source has changed the total size in our image repo is only a few kb larger During each push we only have to push a few more kb each time now that the libs are in their own layer which remains unchanged the image repository is able to re use the dependencies pushed in previous builds bdd Pushing kBaecbbaaa Layer already existsdadf Layer already existsabede Layer already existseeac Layer already existscdad Layer already existsWe can now push hundreds of new image builds without getting anywhere near to the limit of the free tier of this image repository whereas before we d hit the limit after not even builds How the thin jar worksAll we re doing with the above build configuration is creating a jar with just our compiled code in it but telling it where to find the dependencies If you re not familiar with the structure of a jar file it s basically a zip file that contains a load of compiled java classes class files a manifest file there to tell java things like where your main class is and where any external dependencies are when you try to run it via java jarUberjars simplify things by putting all the dependency compiled code into the jar along with your own app But as described in the official docs for jar manifests all we need to do to split out the dependencies is to specify them in a Class Path entry in our manifest With the split in place our manifest file will look something like Manifest Version Created By Maven JAR Plugin Build Jdk Spec Class Path lib kafka clients jar lib zstd jni jar lib lz java jar lib slfj api jar lib slfj simple jarMain Class my app MainNotice that annoyingly we have to manually specify each jar file explicitly in the manifest thankfully the maven jar plugin does this work for us as should other build tools Bonus Slimming down JNI dependenciesAn added bonus to splitting out our library jars is that it makes it easier to further trim down the contents of JNI Java Native Interface dependencies JNI dependencies often contain native libraries for multiple platforms more waste With an extra command in our Dockerfile we can remove these unwanted native libraries from within those jars to trim down the image size even further The example application I m working with is a Kafka Streams app and so has a transitive dependency on rocksdbjni This is a whopping MB Within our Dockerfile we can remove the unwanted libraries from it using zip delete recall that jar files are just zip files like so RUN zip delete target lib rocksdbjni jar librocksdbjni linux musl so librocksdbjni linux so librocksdbjni linux so librocksdbjni linux ppcle so librocksdbjni linux ppcle musl so librocksdbjni linux aarch so librocksdbjni linux aarch musl so librocksdbjni linux sx so librocksdbjni linux sx musl so librocksdbjni win dll librocksdbjni osx arm jnilib librocksdbjni osx x jnilibThis trimmed down rocksdbjni jar is only MB nice ConclusionWe get a lot of bang for our buck here storage amp network costs converted from megabytes to kilobytes with just a few tweaks to our app amp container builds This might sound rather academic but as we ve seen here it can make the difference between hitting your repository storage limit VS having headroom for hundreds of builds Give it a try and let me know what you think	2023-05-12 22:30:09
海外TECH	Engadget	Korg Berlin shows off a prototype 'acoustic synthesizer'	https://www.engadget.com/korg-berlin-shows-off-a-prototype-acoustic-synthesizer-223023911.html?src=rss	Korg Berlin shows off a prototype x acoustic synthesizer x The idea of an acoustic synthesizer might sound like an oxymoron but it s exactly the sort of unexpected concepts that Korg Berlin was created to pursue This independent R amp D focused division was cofounded in by Maximilian Rest and Tatsuya Takahashi the man behind the Volcas Minilogue and countless other modern classics But it has remained pretty quiet since its inception That changed this week at Superbooth where the team showed off its first prototype the Acoustic Synthesis phase nbsp Unlike a traditional synth that uses oscillators the phase uses tuned metal forks Those forks are specially designed to produce specific fundamental notes and overtones And since the core sound generation here is an acoustic resonator it has certain qualities a normal synth does not For instance it will feedback like a guitar when held near an amp and ring when struck on its side Takahashi told Fess Grandiose of Reverb quot we re trying to kind of capture this rawness of instruments while being at the same time controllable like a synthesizer quot So that s the quot acoustic quot part metal tines that ring resonate and decay almost like a Fender Rhodes The synth part comes from the magnets inside the phase that allow it to sustain just the fundamental note or the fundamental and the overtones or just the overtones The overtones can also be modulated with an LFO creating a sound that can only be described as a sea sick bell nbsp In general the sound it generates in the short demo video above is quite unique It does have a ringing vaguely Rhodes like quality to it But it also kind of sounds like what you might expect of a singing bowl patch on a s sample based synth It s a touch otherworldly nbsp Right now the phase is just a prototype and it s likely to stay that way Right now Korg Berlin is simply gauging interest in the technology And if it seems like there s a market for this sort of strange hybrid acoustic synth then it will explore ways to develop it further into a finished product nbsp View this post on InstagramA post shared by KORG Germany GmbH korg berlin This article originally appeared on Engadget at	2023-05-12 22:30:23
海外科学	NYT > Science	Bernadine Strik, Whose Insights Helped Blueberries Thrive, Dies at 60	https://www.nytimes.com/2023/05/12/science/bernadine-strik-dead.html	Bernadine Strik Whose Insights Helped Blueberries Thrive Dies at A horticulturist she discovered farming methods that increased yields of the fruit as its health benefits became widely understood and demand for it grew	2023-05-12 22:04:43
金融	金融総合：経済レポート一覧	FX Daily（5月11日）～弱い米指標受け一時133円台まで押される	http://www3.keizaireport.com/report.php/RID/537353/?rss	fxdaily	2023-05-13 00:00:00
金融	金融総合：経済レポート一覧	景気減速と高インフレの併存が続く米国：経済の舞台裏	http://www3.keizaireport.com/report.php/RID/537355/?rss	景気減速	2023-05-13 00:00:00
金融	金融総合：経済レポート一覧	ＢＯＥも利上げ継続の可能性を示唆～今後の利上げ確度はＦＲＢ＜ＢＯＥ＜ＥＣＢ：Europe Trends	http://www3.keizaireport.com/report.php/RID/537357/?rss	frbboeecbeuropetrends	2023-05-13 00:00:00
金融	金融総合：経済レポート一覧	金融正常化への険しい道筋：岩田一政の万理一空	http://www3.keizaireport.com/report.php/RID/537366/?rss	万理一空	2023-05-13 00:00:00
金融	金融総合：経済レポート一覧	内外経済とマーケットの注目点（2023/5/12）～米国ではFRBの利下げ期待と景気悪化懸念が入り交じる可能性がある：金融・証券市場・資金調達	http://www3.keizaireport.com/report.php/RID/537380/?rss	大和総研	2023-05-13 00:00:00
金融	金融総合：経済レポート一覧	マーケットフォーカス（米ドル建債券市場）2023年5月号～米国国債利回りは小幅に低下。	http://www3.keizaireport.com/report.php/RID/537384/?rss	三井住友トラスト	2023-05-13 00:00:00
金融	金融総合：経済レポート一覧	英国金融政策（2023年5月）～12会合連続の利上げで政策金利は2008年以来の高水準に：マーケットレター	http://www3.keizaireport.com/report.php/RID/537385/?rss	政策金利	2023-05-13 00:00:00
金融	金融総合：経済レポート一覧	高校で始まった投資教育から見るこれからの資産形成	http://www3.keizaireport.com/report.php/RID/537386/?rss	日本fp協会	2023-05-13 00:00:00
金融	金融総合：経済レポート一覧	ビーアンドピー（東証スタンダード）～業務用インクジェットプリンターによる出力サービスの大手。新型コロナ禍からの回復前提で、前期に続き23年10月期も増収増益の会社計画：アナリストレポート	http://www3.keizaireport.com/report.php/RID/537387/?rss	増収増益	2023-05-13 00:00:00
金融	金融総合：経済レポート一覧	ＣａＳｙ（東証グロース）～家事代行等の暮らし関連サービスのマッチング・プラットフォームを運営。家事代行のサービス 提供プロセスをDX化するビジネスモデルが特徴：アナリストレポート	http://www3.keizaireport.com/report.php/RID/537388/?rss	家事代行	2023-05-13 00:00:00
金融	金融総合：経済レポート一覧	ASEAN諸国の金融包摂の進展をもたらす金融サービスの変化～オルタナティブ融資、オープンファイナンス、組み込み型金融：RIM 環太平洋ビジネス情報 Vol.23,No.89	http://www3.keizaireport.com/report.php/RID/537408/?rss	asean	2023-05-13 00:00:00
金融	金融総合：経済レポート一覧	上昇する中国の潜在不良債権比率～企業の財務データからみた不良債権問題の現状と展望：RIM 環太平洋ビジネス情報 Vol.23,No.89	http://www3.keizaireport.com/report.php/RID/537409/?rss	volno	2023-05-13 00:00:00
金融	金融総合：経済レポート一覧	家計調査報告（貯蓄・負債編）2022年（令和４年）平均結果（二人以上の世帯）～1世帯当たり貯蓄現在高は1901万円、前年に比べ1.1％増加、４年連続の増加。	http://www3.keizaireport.com/report.php/RID/537420/?rss	家計調査	2023-05-13 00:00:00
金融	金融総合：経済レポート一覧	利上げ休止であれ、政策転換であれ、注目すべき債券：アセットアロケーション展望	http://www3.keizaireport.com/report.php/RID/537427/?rss	pimco	2023-05-13 00:00:00
金融	金融総合：経済レポート一覧	英国金融政策（5月ＭＰＣ）～0.25％ポイント利上げ、金融不安の影響は限定的：経済・金融フラッシュ	http://www3.keizaireport.com/report.php/RID/537430/?rss	金融政策	2023-05-13 00:00:00
金融	金融総合：経済レポート一覧	米国：銀行融資担当者調査（2023年1-3月期）～利上げと銀行破綻で融資厳格化が進行、調査対象外の中小行に要警戒：MRIデイリー・エコノミック・ポイント	http://www3.keizaireport.com/report.php/RID/537439/?rss	三菱総合研究所	2023-05-13 00:00:00
金融	金融総合：経済レポート一覧	FX Weekly (2023年5月12日号)～来週の為替相場見通し（1）ドル円：バイデン大統領は来日するのか	http://www3.keizaireport.com/report.php/RID/537440/?rss	fxweekly	2023-05-13 00:00:00
金融	金融総合：経済レポート一覧	IPOを目指すスタートアップを取り巻く環境変化（前編）	http://www3.keizaireport.com/report.php/RID/537462/?rss	発表	2023-05-13 00:00:00
金融	金融総合：経済レポート一覧	【BOE金融政策委員会（2023年5月）】BOEは12会合連続で利上げ ～利上げは次回で打ち止めと予想	http://www3.keizaireport.com/report.php/RID/537470/?rss	打ち止め	2023-05-13 00:00:00
金融	金融総合：経済レポート一覧	Kamiyama Reports：米インフレは峠を越えるだろう	http://www3.keizaireport.com/report.php/RID/537476/?rss	kamiyamareports	2023-05-13 00:00:00
金融	金融総合：経済レポート一覧	【注目検索キーワード】金融経済教育	http://search.keizaireport.com/search.php/-/keyword=金融経済教育/?rss	検索キーワード	2023-05-13 00:00:00
金融	金融総合：経済レポート一覧	【お薦め書籍】1300万件のクチコミでわかった超優良企業	https://www.amazon.co.jp/exec/obidos/ASIN/4492534628/keizaireport-22/	転職	2023-05-13 00:00:00
ニュース	BBC News - Home	The Papers: 'We three kings' and 'Phil fights for job'	https://www.bbc.co.uk/news/blogs-the-papers-65579148?at_medium=RSS&at_campaign=KARANGA	papers	2023-05-12 22:42:51
ビジネス	ダイヤモンド・オンライン - 新着記事	マスク帝国の新生ツイッター、スペースXが手本 - WSJ発	https://diamond.jp/articles/-/322912	新生	2023-05-13 07:17:00
ビジネス	東洋経済オンライン	子育て支援拡充しても｢少子化｣は解決しない根拠 ｢生涯無子率｣から見る日本の本質的な問題点 | ソロモンの時代―結婚しない人々の実像― | 東洋経済オンライン	https://toyokeizai.net/articles/-/671776?utm_source=rss&utm_medium=http&utm_campaign=link_back	子育て支援	2023-05-13 08:00:00
Azure	Azure の更新情報	We're retiring Speech-to-text REST preview API v3.1-preview.1 on May 12, 2023	https://azure.microsoft.com/ja-jp/updates/were-retiring-speechtotext-rest-preview-api-v31preview1-on-may-12-2023/	We x re retiring Speech to text REST preview API v preview on May We recently made the Speech to text REST API version generally available With this release we ll retire the preview version v preview on May	2023-05-12 23:00:08