投稿時間:2023-08-17 19:27:12 RSSフィード2023-08-17 19:00 分まとめ(33件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
IT	InfoQ	Presentation: Programming Your Policies	https://www.infoq.com/presentations/policy-dealing-with/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global	Presentation Programming Your PoliciesJustin Cormack discusses how to deal with policies what the business drivers are how it affects developers compliance and security departments and the cultural and communication changes there By Justin Cormack	2023-08-17 09:35:00
IT	ITmedia 総合記事一覧	[ITmedia Mobile] Yahoo!天気アプリが「ダークモード」に対応　黒基調でアイコンなどが見やすく	https://www.itmedia.co.jp/mobile/articles/2308/17/news143.html	itmediamobileyahoo	2023-08-17 18:04:00
IT	情報システムリーダーのためのIT情報専門サイト IT Leaders	「HUEチャットボット」がChatGPTと連携、FAQで用意されない質問にも回答 | IT Leaders	https://it.impress.co.jp/articles/-/25237	azureopenaiservice	2023-08-17 18:26:00
AWS	AWS Japan Blog	AWS Weekly Roundup – Amazon MWAA、EMR Studio、生成系 AI など – 2023 年 8 月 14 日	https://aws.amazon.com/jp/blogs/news/aws-weekly-roundup-amazon-mwaa-emr-studio-generative-ai-and-more-august-14-2023/	emrstudio	2023-08-17 09:57:23
AWS	AWS Japan Blog	Amazon Neptune Serverlessでコストとパフォーマンスを最適化するベストプラクティスおよびユースケースの紹介	https://aws.amazon.com/jp/blogs/news/use-cases-and-best-practices-to-optimize-cost-and-performance-with-amazon-neptune-serverless/	amazonneptuneserverless	2023-08-17 09:52:06
AWS	AWS Japan Blog	AWS AppSync が GraphQL API のすべてのリゾルバで JavaScript をサポート	https://aws.amazon.com/jp/blogs/news/aws-appsync-now-supports-javascript-for-all-resolvers-in-graphql-apis/	AWSAppSyncがGraphQLAPIのすべてのリゾルバでJavaScriptをサポートAppSyncはJavaScriptのサポートをユニットリゾルバに拡張しました。	2023-08-17 09:33:44
python	Pythonタグが付けられた新着投稿 - Qiita	【Python】isinstance関数の使い方 & type関数との違いとは？	https://qiita.com/Ryo-0131/items/c5c650359ab8ce10b507	adataifisinstancedatali	2023-08-17 18:02:53
Ruby	Rubyタグが付けられた新着投稿 - Qiita	【Rails】saveとsave!の挙動の違い	https://qiita.com/ym0628/items/d05cccb3405bcd60b1fe	rubyo	2023-08-17 18:08:06
AWS	AWSタグが付けられた新着投稿 - Qiita	CodePipelineのポーリングパイプラインが非推奨になったのでEventBridgeでS3イベントを受けてパイプラインを開始できるようにマイグレーションする	https://qiita.com/YoukyMurakami/items/9d3af050abffffd9728e	codecommit	2023-08-17 18:37:05
Ruby	Railsタグが付けられた新着投稿 - Qiita	【Rails】saveとsave!の挙動の違い	https://qiita.com/ym0628/items/d05cccb3405bcd60b1fe	rubyo	2023-08-17 18:08:06
技術ブログ	Developers.IO	CEDEC 2023に出展します #CEDEC2023 #classmethod_game	https://dev.classmethod.jp/articles/230817_cedec2023/	cedec	2023-08-17 09:40:15
技術ブログ	Developers.IO	AWS ParallelCluster のコンピュートノードでベアメタルインスタンスを使ってみた	https://dev.classmethod.jp/articles/use-bare-metal-instances-with-aws-parallelcluster/	awsparallelcluster	2023-08-17 09:22:44
技術ブログ	Developers.IO	プライベートサブネット上のEC2にPatch Manager利用時、OS別の構成(Windows, Linux)とパッチ適用方法まとめ	https://dev.classmethod.jp/articles/private-subnet-ec2-patchmanager/	systemsmana	2023-08-17 09:22:07
技術ブログ	Developers.IO	[アップデート] Amazon OpenSearch Serverless で最大 OCU および時系列コレクションのインデックスデータサイズ上限が拡張されました	https://dev.classmethod.jp/articles/opensearch-serverless-workloads-collections/	opensearchcomputeunitsocu	2023-08-17 09:02:08
海外TECH	DEV Community	What's a Merge Queue and Why Use it?	https://dev.to/wakatepemergify/whats-a-merge-queue-and-why-use-it-1b39	What x s a Merge Queue and Why Use it That s a good question isn t it Indeed if it was only a little known term a few months ago merge queues would be more and more talked about Between announcements from leaders like GitHub and real technical solutions merge queues are increasingly adopted by software development teams So you ll be able to dive into this topic to understand what a merge queue is in what situations they are useful and how they work in practice Are you ready for it Let s get started ーyou can also watch our video at the end of this article What Do We Mean by “Merge Queue Before wanting to know why you should work with a merge queue it is important to define what it is Its name says all a Merge Queue is simply a queue of Pull Requests waiting to be merged Each member of your team creates Pull Requests like a lot each day Then the maintainers of the repository add it to the queue Simple right To be accurate you are not just putting basic PRs in a queue All the PRs present in the queue have been approved by maintainers It means that they passed all the required checks So you get a queue full of validated Pull Requests Sounds cool not really useful though Why not just merge them one by one To give you an answer let see first what common issues you will encounter if you do not use a merge queue Why Do You Need a Merge Queue To be honest there are plenty of reasons and arguments to explain why you should bet on a merge queue In this part you will discover a really problematic situation and how you can solve it by using a merge queue The Common Issue Merging Outdated Pull RequestsTo understand the problem queues resolve you first have to understand the issue To do so imagine the following situation The main branch passes its continuous integration testing correctly A pull request is created which also passes the CI Call it PR At this time here is how you can represent the state of your repository Right now everything is totally OK but it will not last Let s see While PR is still open another commit is pushed to the main branch No matter if this newly created commit is pushed directly to the main branch or merged from another pull request In fact you just have to understand that the main branch has been modified Then the tests are run against the main branch by the CI and they pass again At this point you can describe the state of your repository and its continuous integration system like this img alt A new commit has been pushed and merged into the main branch lt br gt height src dev to uploads s amazonaws com uploads articles jwhdkokyujtjbum png width You can see the PR is still marked as valid by the continuous integration system Indeed it is normal since it did not change Only the main branch changed As there is no code conflict GitHub considers PR as mergeable the merge button turns green All happy you are you smash that green button But you saw that coming you might have a surprise ーand not a good one Now that you want to merge PR a new merge commit is created and the continuous integration tests fail but why In fact when PR was marked as valid the CI did not test ーagain ーPR with the new commit added to the main branch remember it However the last commit brought new tests in the main branch with him and now PR does not have the correct code to pass this new test As sad as logical How to Deal with this Situation Basically the problem is all about rebase and the necessity for each pull request to be up to date If you do not use a Merge Queue you have two options Only run your CI on the head of your feature branch ーand do not require your feature branch to be up to date with the main branch →The main drawback here is that your feature branch might be or not compatible with the main branch Require all feature branches to be up to date with the target →The main drawback is that you waste a lot of time and money That s a quite common situation for organizations and teams working with CI CD processes If it is an issue do not worry you have found the real solution The Real Solution a Merge QueueA promise is a promise you re not going to stay in this dead end situation Your solution using a merge queue Indeed it solves that problem by updating any pull request before being merged But only the ones that are not up to date with its main branch Actually a merge queue forces the CI system to test the PR again but with the new code from its main branch In the previous situation if you use a merge queue it would automatically merge the main in the feature branch As you can see below the CI would have rerun Then the pull request would have been marked as failing and removed from the queue Of course if the PR was valid and all the checks passed it would have been merged Another case of scenario multiple pull requests are validated and ready to be merged A merge queue will schedule their merging sequentially and ensure you that they are all updated on top of each other Obviously these updates are only done if the pull requests complete all the conditions Nevertheless what happens when you merge an updated pull request and then get another one which is still outdated To ease your understanding what about another illustration A merge queue will make sure the second pull request is updated with the latest tip of the main branch before merging By doing this there is no way to merge an outdated and broken pull request into the main branch And you repeat this as many times as necessary for each outdated pull request in the queue Life is not always easy but a merge queue can make it a lot easier How Does a Merge Queue Work Now that you know what kind of issue a merge queue can solve let s summarize its functioning As you probably understood a merge queue looks more or less like a complex workflow we can analyze step by step ️ Queue Valid PRsRun the engine on your pull requests All valid pull requests ーthe ones which validated all the conditions can be added to the queue Update and CIThe merge queue will make sure that each PR in the queue is up to date by merging the main branch into the feature branch Then the CI rerun to make sure the PR is mergeable To Merge or not to Merge that s the QuestionTwo quite distinct cases All checks passed →merge the PR Failing test →remove the PR from the queue What About Mergify s Merge Queue In concrete terms Mergify s Merge Queue does everything you just read It is one of the first merge queues launched on the market and already has thousands of happy users While the common features presented before can solve many headaches you may find yourself facing even more complex and specific situations These situations require very specific functionalities Good news with Mergify you already have them at your fingertips Speculative Checks Testing Different PRs in ParallelThe first pull requests from the queue are embarked in a merge train and tested together in parallel so they can be merged faster Batches Check and Merge Multiple PRs at Once Mergify allows checking the mergeability of multiple pull requests at once using the batch size option Multiple Queues Put PRs in a Dedicated Queue By using multiple queues it s possible to put some pull requests in a higher priority queue Queue Freeze Stopping All Merging Processes Mergify allows freezing the merge of one or several queues simultaneously to provide maximum control and flexibility on how and when you want the code to be merged Priority Management Prioritize your Pull Requests Choose which PR should be merged first depending on labels owners etc Your rules ultimately Demo Video ConclusionHere you are folks you should know everything about the concept of a merge queue From how it works to why you should use one merge queues have no secrets for you It s now time to try it and you know what You can enjoy a day trial for free with Mergify I guess it s your chance to say bye bye to this outdated pull request issue	2023-08-17 09:41:22
海外TECH	DEV Community	Migrating Legacy Apps to AWS: Overcoming Challenges for Success	https://dev.to/softwebsolution/migrating-legacy-apps-to-aws-overcoming-challenges-for-success-997	Migrating Legacy Apps to AWS Overcoming Challenges for SuccessIntroductionIn today s rapidly evolving technological landscape businesses are constantly seeking ways to leverage the benefits of cloud computing For many organizations this involves migrating their legacy applications to cloud platforms such as Amazon Web Services AWS However this process can present several challenges and complexities that need to be carefully addressed to ensure a successful migration This article aims to explore the intricacies of migrating legacy applications to AWS highlighting the common challenges faced and providing valuable insights on how to overcome them Understanding Legacy ApplicationsLegacy applications refer to software systems that have been in operation for a significant period and may be based on outdated technologies or architectures These applications often play a critical role in business operations but can become a hindrance to scalability agility and cost efficiency Migrating these applications to the cloud offers numerous advantages and enables organizations to modernize their IT infrastructure while maintaining business continuity Benefits of Migrating Legacy Applications to AWSMigrating legacy applications to AWS brings forth several benefits that contribute to an organization s growth and success Firstly AWS provides a highly scalable and flexible infrastructure allowing businesses to dynamically adjust resources based on demand This scalability empowers organizations to handle peak loads effectively ensuring optimal performance and user experience Additionally AWS offers a broad range of services and tools that enhance application capabilities enabling businesses to leverage advanced technologies such as machine learning artificial intelligence and data analytics Common Challenges in Legacy Application MigrationWhen migrating legacy applications to AWS organizations often encounter various challenges that require careful attention and mitigation strategies These challenges include Compatibility and DependenciesLegacy applications might have dependencies on specific hardware operating systems or software components Ensuring compatibility and addressing these dependencies during the migration process can be complex and time consuming Scalability and PerformanceLegacy applications are not inherently designed for cloud environments and may lack the scalability and performance capabilities required in today s dynamic business landscape Optimizing application architecture and infrastructure to achieve scalability and performance in the AWS cloud is crucial Security and ComplianceLegacy applications may not have been developed with modern security practices in mind Migrating such applications to AWS requires a robust security framework to ensure data protection compliance with industry regulations and protection against evolving cyber threats Data Migration and IntegrationTransferring data from legacy systems to AWS while maintaining data integrity and minimizing downtime is a significant challenge Integrating legacy application data with new cloud native services and platforms requires careful planning and execution Strategies for Successful Legacy Application MigrationTo overcome the challenges associated with migrating legacy applications to AWS organizations can adopt several strategies based on their specific requirements and constraints These strategies include To learn more about strategies for migrating data to the AWS cloud you can explore the following resource Strategies for Migrating Data to AWS Cloud This comprehensive guide provides valuable insights and best practices specifically focused on data migration to AWS complementing the information covered in this article Assessment and PlanningThoroughly assess the legacy application landscape and define a comprehensive migration plan Identify dependencies prioritize applications and determine the most suitable migration approach for each application Refactoring and ReplatformingModernize the application architecture by refactoring code and adopting cloud native services Replatforming involves moving the application to a different platform within AWS optimizing its performance and scalability Rehosting and Lift and ShiftRehosting also known as the lift and shift approach involves moving the application to AWS with minimal modifications This strategy offers a faster migration process but may not fully leverage the benefits of the cloud Decommissioning and ReplacementFor applications that no longer serve a purpose or are highly outdated decommissioning and replacing them with modern cloud native alternatives can be a viable strategy This approach ensures long term efficiency and cost savings Best Practices for Legacy Application Migration to AWSSuccessful migration of legacy applications to AWS requires adherence to a set of best practices These practices include Establish Clear Goals and Objectives Clearly define the goals and objectives of the migration project Identify key performance indicators KPIs to measure success and ensure alignment with the organization s overall strategy Prioritize Security and Compliance Implement robust security measures including access controls encryption and monitoring Adhere to industry compliance standards and regulations relevant to your organization Optimize Performance and Scalability Leverage AWS services to optimize application performance and scalability Utilize auto scaling load balancing and caching mechanisms to handle varying workloads effectively Ensure Seamless Data Migration and Integration Devise a comprehensive data migration strategy including backup and restoration plans Establish data integration mechanisms between legacy and cloud systems to ensure smooth operation Test Rigorously and Monitor Continuously Thoroughly test the migrated applications to identify and rectify any issues Implement monitoring and alerting mechanisms to proactively detect and address performance or security anomalies To explore more about the benefits of cloud modernization you can refer to our article on Cloud Modernization Benefits This resource provides valuable insights into how modernizing your legacy applications with cloud technologies can bring substantial advantages complementing the information covered in this article Overcoming Challenges and Ensuring SuccessOvercoming the challenges associated with migrating legacy applications to AWS requires a combination of technical expertise and strategic planning Some key steps to ensure success include Comprehensive Testing and ValidationConduct extensive testing and validation to ensure the migrated applications function as intended Implement rigorous testing methodologies to identify and resolve any performance or compatibility issues Partnering with AWS ExpertsLeverage the expertise of AWS certified professionals or consulting partners Their knowledge and experience can significantly contribute to a smooth and successful migration process Embracing Automation and DevOpsUtilize automation tools and adopt DevOps practices to streamline the migration process Automation minimizes manual effort reduces the risk of errors and accelerates the overall migration timeline Continuous Optimization and IterationOptimize the migrated applications on an ongoing basis Monitor performance identify areas for improvement and iterate on the architecture to leverage the full potential of AWS services ConclusionMigrating legacy applications to AWS requires careful planning execution and continuous optimization By addressing challenges such as compatibility scalability security and data migration organizations can successfully modernize their applications and leverage the benefits of AWS Thorough testing collaboration with AWS experts and the adoption of automation and DevOps practices are crucial for a smooth and successful migration With careful execution organizations can unlock the advantages of the cloud enabling modernization cost savings scalability and agility in today s competitive digital landscape Frequently Asked Questions FAQs FAQ Is it necessary to refactor legacy applications before migrating to AWS Refactoring legacy applications can be beneficial but is not always necessary It depends on the specific application and its compatibility with the AWS environment Refactoring can optimize the application for better performance and scalability in the cloud but it also requires additional time and resources FAQ How long does the migration process usually take The duration of the migration process varies depending on factors such as the complexity of the application the amount of data to be transferred and the chosen migration strategy It can range from weeks to several months Thorough planning and proper execution can help streamline the process and minimize downtime FAQ Can we migrate legacy applications with complex dependencies Yes it is possible to migrate legacy applications with complex dependencies to AWS However careful analysis and planning are required to identify and address these dependencies during the migration process It may involve refactoring re platforming or adopting specific migration strategies to ensure a smooth transition FAQ What security measures should be taken during the migration Security is a critical aspect of any migration process When migrating legacy applications to AWS organizations should implement security best practices such as access controls encryption and monitoring They should also ensure compliance with relevant industry standards and regulations to protect sensitive data FAQ How can we ensure minimal downtime during the migration Minimizing downtime during the migration requires careful planning and execution Strategies such as performing the migration in stages implementing parallel testing environments and utilizing load balancers can help ensure a smooth transition with minimal disruption to the application s availability	2023-08-17 09:39:30
海外TECH	DEV Community	The Role of MicroGateways in Microservices	https://dev.to/amplication/the-role-of-microgateways-in-microservices-3a29	The Role of MicroGateways in Microservices IntroductionMicroservices have redefined how applications are planned developed and deployed Its modular design provides exceptional flexibility and scalability allowing organizations to adjust to changing demands quickly However this modularity brings new challenges such as managing cross cutting concerns like security access control logging and communication interfaces This is where MicroGateways come into the picture MicroGateways serve as a watchdog at the microservices level addressing these complicated challenges and facilitating efficient communication What are MicroGateways MicroGateways serve as the point of providing a secure and efficient environment for communication between microservices They act as intermediaries that are strategically positioned between microservices and the client as well as between microservices and other microservices This lets MicroGateways orchestrate essential cross cutting concerns while letting each microservice focus on its functionality What are the benefits of Micro Gateways In essence MicroGateways offer the same basic benefits as traditional API Gateways such as enhanced security streamlined access control optimized communication and centralized logging Those key benefits include Enhanced SecurityMicroGateways stand as the first line of defense against security threats They enforce authentication and authorization protocols by serving as a controlled entry point for external requests This prevents unauthorized access attempts safeguarding microservices from potential breaches Additionally micro gateways enable encrypted communication channels ensuring data privacy and integrity during transit Streamlined Access ControlThe centralized access control mechanisms implemented by micro gateways alleviate the complexities of managing permissions across multiple microservices They enforce access policies uniformly reducing the chances of misconfigurations or inconsistencies that could compromise the system s security Granular access controls based on roles users or actions can be efficiently managed enhancing the overall access management strategy Efficient Logging and MonitoringMicroGateways excel in aggregating and centralizing logs and metrics generated by microservices This unified logging approach simplifies the monitoring and troubleshooting process allowing for comprehensive insights into system behavior Developers and operations teams can efficiently detect anomalies identify performance bottlenecks and track down errors This streamlined approach contributes to improved system observability and quicker issue resolution Communication OptimizationThe diverse communication protocols employed by microservices can impede smooth interactions MicroGateways mitigate this challenge by standardizing communication interfaces As protocol translators they enable microservices to communicate seamlessly using varying protocols This optimization promotes interoperability facilitating communication between microservices using different technologies or data formats What are the differences between a MicroGateways and a Traditional API Gateway Figure The difference between a MicroGateway and an API GatewayIn a nutshell a traditional API Gateway acts as a client facing endpoint that aims to simplify Client to Service Communication But internally each microservice communicates with the single API Gateway and directly with each other A MicroGateway on the other hand lets a client directly interact with the service that it requires ultimately enabling you to scale a service independently to the traditional API Gateway A detailed difference breakdown is presented below MicroGateways Agility and Adaptability Allow seamless addition modification or removal of services without disrupting the entire architecture Scalability and Performance Optimized for microservices lightweight nature micro gateways efficiently scale with the number of services thus minimizing overhead and latency Deployment and Management Simplify deployment by offering per service gateways enabling independent updates and reducing the risk of service disruptions Customization and Flexibility Allow fine tuned customization to cater to microservices unique requirements ensuring a tailored approach to each service s needs Ownership MicroGateways development and deployment are owned by the same team that develops and deploys the Microservice thus removing cross team dependencies Traffic Coverage As each Microservice has its own MicroGateway communication between microservices internally east west is also covered as well as inbound communication from clients north south This allows us to take advantage of all the advantages of the gateway also for east west communication API Gateways Agility and Adaptability It might require significant reconfiguration to accommodate changes in a microservices environment potentially leading to downtime Scalability and Performance Suited for monolithic applications traditional gateways might introduce performance bottlenecks and unnecessary features in a microservices ecosystem Deployment and Management Deployment might be more complex as changes to a central gateway could impact multiple services simultaneously Customization and Flexibility Offer less granularity in customization potentially resulting in services conforming to a more uniform set of configurations Ownership As they are the entry point for all the microservices ownership of traditional gateways will usually be assigned to a platform engineering team a DevOps team or a dedicated Gateway team Traffic Coverage In most architectures API gateways are only situated on the inbound traffic from clients north south while inter service communication is usually direct unsecured or with a JWT token or similar mechanism What are the challenges in MicroGateway implementation Increased ComplexityManaging multiple micro gateways can introduce complexity in configuration management and coordination Service DiscoveryA centralized gateway that knows all the services can greatly assist with service discovery When using MicroGateways other means of service discovery mechanisms need to be utilized on top of the MicroGateways themselves to ensure seamless communication between microservices Latency ConcernsIntroducing additional network hops through MicroGateways might lead to increased latency in microservices interactions How should you select a MicroGateway Compatibility with Technology Stack Opt for a MicroGateway solution that seamlessly integrates with your existing microservices technology stack Performance Optimization Prioritize MicroGateways with minimal latency overhead ensuring efficient communication between microservices Customization Options Select a MicroGateway offering flexible configuration options allowing tailored adjustments to meet specific microservices requirements Security Measures Assess MicroGateway s capabilities for enforcing authentication authorization and encryption protocols to safeguard microservices interactions Scalability Support Ensure the MicroGateway solution can scale effortlessly as your microservices ecosystem grows without compromising performance Monitoring and Analytics Look for built in monitoring and analytics features that offer insights into microservices interactions and performance Community and Support Evaluate the availability of active communities and support channels for troubleshooting and updates Feature Set If you require specific features like rate limiting or specific integrations make sure to look for a MicroGateway solution that supports as many of your desired features out of the box as possible These comprehensive criteria ensure that the chosen micro gateway aligns with the architectural needs of your microservices environment By addressing challenges and employing a well defined selection process organizations can leverage the full potential of micro gateways in enhancing their microservices architecture The use of MicroGateways in modern software Stringent Security Measures in Financial Microservices EcosystemIn a financial institution s microservices architecture security is paramount Micro gateways play a pivotal role by enforcing strict authentication and authorization protocols They ensure that only authorized users and applications can access critical financial services As they also cover service to service communication a breach in one service does not give access to another service immediately Furthermore micro gateways facilitate the encryption of sensitive data during transmission safeguarding against potential breaches The result is a fortified ecosystem where microservices communicate securely maintaining the integrity of financial transactions Seamless Communication with Diverse ProtocolsConsider an e commerce platform s microservices ecosystem that involves various services communicating over different protocols Micro gateways act as protocol translators allowing microservices to communicate seamlessly regardless of the underlying technology They convert protocols on the fly enabling interactions between services that use distinct data formats and communication patterns This flexibility fosters a cohesive ecosystem where services collaborate effortlessly enhancing the overall shopping experience Access Control Management in Healthcare SystemAccess control is critical to protect patient data in a healthcare organization s microservices setup Micro gateways simplify access control management by allowing for both centralized as well as decentralized permission policies They enforce granular access rights based on user roles ensuring that healthcare professionals can access patient records only when authorized This centralized decentralized control reduces the risk of improper data access aligning with healthcare privacy regulations Key TakeawaysMicro gateways are indispensable in the microservices landscape addressing cross cutting concerns and facilitating efficient communication They enhance security streamline access control centralize logging and optimize communication interfaces while offering agility scalability and microservices centric focus compared to traditional API gateways making them ideal for many modern architectures As organizations adopt microservices architecture the need for efficient development and management tools becomes paramount Amplication with its robust features and capabilities seamlessly integrates into microservices ecosystems enhancing the development and deployment of microservices based applications	2023-08-17 09:06:16
海外TECH	DEV Community	Ops friendly Apache APISIX	https://dev.to/apisix/ops-friendly-apache-apisix-2b8c	Ops friendly Apache APISIXThough I always worked on the Dev side of IT I was also interested in the Ops side I even had a short experience being a WebSphere admin I used it several times helping Ops deal with the Admin console while being a developer Providing a single package that Ops can configure and deploy in different environments is very important As a JVM developer I ve been happy using Spring Boot and its wealth of configuration options command line parameters JVM parameters files profiles environment variables etc In this short post I d like to describe how you can do the same with Apache APISIX in the context of containers File based configurationThe foundation of configuring Apache APISIX is file based The default values are found in the usr local apisix conf apisix config default yaml configuration file For example by default Apache APISIX runs on port and the admin port is That s because of the default configuration apisix node listen deployment admin admin listen ip port Regular portAdmin portTo override values we need to provide a file named config yaml in the usr local apisix conf apisix directory apisix node listen deployment admin admin listen port Override valuesNow Apache APISIX should run on port and the admin port should be Here s how to run the Apache APISIX container with the above configuration docker run it rm apache apisix debian p p v config yaml usr local apisix conf apisix config yaml Environment based configurationThe downside of a pure file based configuration is that you must provide a dedicated file for each environment even if only a single parameter changes Apache APISIX allows replacement via environment variables in the configuration file to account for that apisix node listen APISIX NODE LISTEN deployment admin admin listen port DEPLOYMENT ADMIN ADMIN LISTEN Replace the placeholder with its environment variable value at runtimeWe can reuse the same file in every environment and hydrate it with the context dependent environment variables docker run it rm apache apisix debian e APISIX NODE LISTEN e DEPLOYMENT ADMIN ADMIN LISTEN p p v config yaml usr local apisix conf apisix config yamlIcing on the cake we can also offer a default value apisix node listen APISIX NODE LISTEN deployment admin admin listen port DEPLOYMENT ADMIN ADMIN LISTEN If no environment variable is provided use those ports otherwise use the environment variables valueThe trick works in standalone mode with the apisix yaml file You can parameterize every context dependent variable and secrets with it routes uri upstream nodes httpbin plugins openid connect client id apisix client secret OIDC SECRET discovery https OIDC ISSUER well known openid configuration redirect uri http localhost callback scope openid session secret SESSION SECRET ConclusionWhen configuring Apache APISIX we should ensure it s as operable as possible In this post I ve described several ways to make it so Happy Apache APISIX To go further Default configurationConfiguration file switching based on environment variablesOriginally published at A Java Geek on August th	2023-08-17 09:02:00
海外TECH	Engadget	Amazon sale slashes Fire TV streaming devices by up to 51 percent	https://www.engadget.com/amazon-sale-slashes-fire-tv-streaming-devices-by-up-to-51-percent-094341678.html?src=rss	Amazon sale slashes Fire TV streaming devices by up to percentIf you missed out on grabbing one of Amazon s Fire TV devices during Prime Day then you re in luck Most of the lineup is currently marked down and they re each only a tiny bit more than they were during the site s big sale The cheapest option is Amazon s Fire TV Stick Lite with a percent discount cutting its price from to nbsp Amazon s Fire TV Stick Lite is a great entry point into the series giving you all the basics for the price of two movie tickets or let s be real basically one at this point It works with TV streamers like Netflix and Disney alongside Spotify and Amazon Music You can also watch live TV and have Alexa Voice Remote Lite control your smart home devices to dim the lights nbsp On the more technical side The Fire TV Stick Lite has GB of storage HDMI passthrough of Dolby encoded audio and Wi Fi compatibility However unlike the classic Fire TV Stick the remote doesn t include TV controls like volume The Fire TV Stick is more than its Lite counterpart thanks to the sale dropping its price from to It also includes Alexa Voice Remote and Dolby Atmos Both devices have a quad core CPU GHz and a GPU MHz nbsp The Fire TV Stick K Max has the biggest sale of all with a percent discount bringing its price from to For more than the classic you can get K Ultra HD Dolby Vision and Wi Fi support It also has live view picture in picture and a quad core CPU GHz and a GPU MHz Then there s the big one the Fire TV Cube which has a percent discount cutting its price from to It s significantly more expensive than its counterparts but also comes with many more features like an octa core x GHz x GHz and a GPU MHz Plus Amazon s Fire TV Cube has GB of storage hands free control with Alexa and Wi Fi E support with an Ethernet port Oh and you can connect all your devices to it like game consoles and webcams nbsp Are you just looking for some high tech control Amazon s Alexa Voice Remote Pro is also on sale dropping from to This device is a good option if you tend to lose things as you can tell Alexa find my remote and it will ring nbsp Follow EngadgetDeals on Twitter and subscribe to the Engadget Deals newsletter for the latest tech deals and buying advice This article originally appeared on Engadget at	2023-08-17 09:43:41
海外TECH	CodeProject Latest Articles	Travel through Time Data	https://www.codeproject.com/Articles/5366787/Travel-through-Time-Data	dataexmaple	2023-08-17 09:51:00
海外TECH	CodeProject Latest Articles	Structured ASP.NET Localization	https://www.codeproject.com/Articles/5366784/Structured-ASP-NET-Localization	localization	2023-08-17 09:41:00
海外科学	NYT > Science	Where Ozempic, Wegovy and New Weight Loss Drugs Came From	https://www.nytimes.com/2023/08/17/health/weight-loss-drugs-obesity-ozempic-wegovy.html	Where Ozempic Wegovy and New Weight Loss Drugs Came FromThe empty auditoriums Gila monsters resistant pharmaceutical executives and enigmas that led to Ozempic and other drugs that may change how society thinks about obesity	2023-08-17 09:00:59
海外科学	NYT > Science	How to Survive in the Heat: Coping Advice From Around the World	https://www.nytimes.com/2023/08/17/well/live/heat-hydration-advice.html	extreme	2023-08-17 09:00:59
金融	金融庁ホームページ	入札公告等を更新しました。	https://www.fsa.go.jp/choutatu/choutatu_j/nyusatu_menu.html	公告	2023-08-17 11:00:00
ニュース	BBC News - Home	Sir Michael Parkinson: Chat show host dies aged 88	https://www.bbc.co.uk/news/entertainment-arts-66411604?at_medium=RSS&at_campaign=KARANGA	british	2023-08-17 09:53:57
ニュース	BBC News - Home	Memorable moments from Parkinson's star-studded show	https://www.bbc.co.uk/news/uk-66414755?at_medium=RSS&at_campaign=KARANGA	parkinson	2023-08-17 09:10:38
ニュース	BBC News - Home	More than 60 migrants feared dead at sea off Cape Verde coast	https://www.bbc.co.uk/news/world-africa-66528273?at_medium=RSS&at_campaign=KARANGA	senegal	2023-08-17 09:29:27
ニュース	BBC News - Home	Saudi crown prince invited to visit UK, government source says	https://www.bbc.co.uk/news/uk-politics-66531007?at_medium=RSS&at_campaign=KARANGA	jamal	2023-08-17 09:44:56
ニュース	BBC News - Home	Women's World Cup 2023: England v Australia watched by 7m on BBC TV	https://www.bbc.co.uk/sport/football/66530998?at_medium=RSS&at_campaign=KARANGA	australia	2023-08-17 09:55:34
ニュース	BBC News - Home	School staff to strike in 10 Scottish council areas	https://www.bbc.co.uk/news/uk-scotland-66532163?at_medium=RSS&at_campaign=KARANGA	september	2023-08-17 09:50:35
ニュース	BBC News - Home	Michael Parkinson obituary: Setting the standard for TV talk shows	https://www.bbc.co.uk/news/entertainment-arts-12225132?at_medium=RSS&at_campaign=KARANGA	broadcaster	2023-08-17 09:07:15
マーケティング	MarkeZine	マクロミル、モニタスを連結子会社化　約3,600万人のパネル資産を基にサービス開発や支援強化を目指す	http://markezine.jp/article/detail/43091	連結子会社化	2023-08-17 18:15:00
IT	週刊アスキー	オーディオテクニカ、カーオーディオ用ハイグレード光デジタルケーブル	https://weekly.ascii.jp/elem/000/004/150/4150338/	月日	2023-08-17 18:45:00