This document summarizes a microservices meetup hosted by @mosa_siru. Key points include:
1. @mosa_siru is an engineer at DeNA and CTO of Gunosy.
2. The meetup covered Gunosy's architecture with over 45 GitHub repositories, 30 stacks, 10 Go APIs, and 10 Python batch processes using AWS services like Kinesis, Lambda, SQS and API Gateway.
3. Challenges discussed were managing 30 microservices, ensuring API latency below 50ms across availability zones, and handling 10 requests per second with nginx load balancing across 20 servers.
This document discusses Yarn and its advantages over npm. It notes that Yarn uses yarn.lock files instead of npm-shrinkwrap.json files to lock down dependency versions. Yarn is also described as being faster, able to work offline by caching dependencies, and potentially more secure than npm with features like flat mode and module folders. The document suggests Yarn may handle dependencies and devDependencies differently than npm, and questions whether the yarn.lock file should be committed to source control.
Event : Visual Studio Users Community Japan #1
Date : 2019/09/14
ソフトウェア/サービス開発において最も後回しにされるものの代表が「パフォーマンスの向上」です。C#/.NET の最大の武器は開発生産性ですが、C# 7.0 以降はパフォーマンス向上のための機能追加が多数行われています。いくつかのポイントを押さえることで実装時からより高速なコードを書くことができるようになります。
このドキュメントでは、そんなポイントとなる箇所をふんだんにお届けします。
This document discusses Yarn and its advantages over npm. It notes that Yarn uses yarn.lock files instead of npm-shrinkwrap.json files to lock down dependency versions. Yarn is also described as being faster, able to work offline by caching dependencies, and potentially more secure than npm with features like flat mode and module folders. The document suggests Yarn may handle dependencies and devDependencies differently than npm, and questions whether the yarn.lock file should be committed to source control.
Event : Visual Studio Users Community Japan #1
Date : 2019/09/14
ソフトウェア/サービス開発において最も後回しにされるものの代表が「パフォーマンスの向上」です。C#/.NET の最大の武器は開発生産性ですが、C# 7.0 以降はパフォーマンス向上のための機能追加が多数行われています。いくつかのポイントを押さえることで実装時からより高速なコードを書くことができるようになります。
このドキュメントでは、そんなポイントとなる箇所をふんだんにお届けします。
ソフトウェア業界ではワクワクする新しいテクノロジーがどんどん生まれ、それが世の中で使われるまでも早くなっています。2018年に革新があった Deep Learning は、既に民主化?日常化もしてます。この講演では、そのソフトウェアの今を俯瞰し、今後どうなっていくのか? その未来予想とともに。職業として20年以上の経験を得た私の学びをお伝えします。
1. The document discusses using Outlook and Teams to efficiently handle multitasking. It provides tips for classifying and processing information and tasks in a timely manner.
2. It suggests using tools like Outlook, Teams, OneDrive for task management and sharing files and information. Smartphones are highly effective for initial processing of emails and tasks.
3. PCs are necessary for longer responses, document creation, coding, and research. Cloud services allow storing and accessing all work files and emails from any device.
IoT Devices Compliant with JC-STAR Using Linux as a Container OSTomohiro Saneyoshi
?
Security requirements for IoT devices are becoming more defined, as seen with the EU Cyber Resilience Act and Japan’s JC-STAR.
It's common for IoT devices to run Linux as their operating system. However, adopting general-purpose Linux distributions like Ubuntu or Debian, or Yocto-based Linux, presents certain difficulties. This article outlines those difficulties.
It also, it highlights the security benefits of using a Linux-based container OS and explains how to adopt it with JC-STAR, using the "Armadillo Base OS" as an example.
Feb.25.2025@JAWS-UG IoT
16. Thumbnail
Service
Thumbnail
ServicePhoto Share
Service
Photo Share
Service
Photo Share
Service
Photo Share
Service
Thumbnail
Service
Photo Share Service
Thumbnail
SharedLib-v7
Photo Share
Service
SharedLib-v1
Photo Share
Service
node.js
Thumbnail
Service
.NET
Photo Share
Service
V1
Thumbnail
Service
V1
Thumbnail
Service
SharedLib-v7
Thumbnail
Service
V2
SharedLib-v1
メンテ可能な状態を継続できる
17. ? 単一のデータベース
? 単一テクノロジーのレイヤ
従来型のステート マイクロサービスのステート
? マイクロサービスがグラフ状に結合
? マイクロサービス毎のステート
? 様々なテクノロジーが使われる
stateless
Service
stateless Service with
separate stores
stateful
Service
stateless
presentation
Service
20. 物理コンピュー
ター
仮想マシン ProcessContainer
More isolated More efficient
ハードウェア Not shared Shared Shared Shared
カーネル Not shared Not shared Shared* Shared
システム リソー
ス
(ex: File System)
Not shared Not shared Not shared Shared
29. Declarative Application Description
Deploy, Upgrade and
Monitoring
Service discovery
Reliability, Availability,
Replication, Service
Orchestration
Application Lifecycle
Fault inject,
Test in ProductionFederation a set of nodes to from a consistent scalable fabric
Secure Point-to-point communication
30. Azure Consistent Private Cloud Azure Public Cloud
VMs and VM Scale Sets
VM Extensions
Mesosphere/Swarm
Marathon/Chronos/Swarm
Cluster Management
Federation and Reliability:
? Failover manager
? Cluster manager
? Naming
? Image store service
? Leader Election
Container/Service scheduling
Hosting
? Container activation and Monitoring
Balancing and Scheduling
? Resource Balancing & Placement
ZooKeaper
Application Programming Models
? Stateful/Stateless Service
? Reliable Actors
? Reliable Service
? Health Monitoring
Communication Subsystem
? Service/Service Communication
? Sessions/Streams
?Healthmanagementanddiagnostics
?Testabilityframework
70. ? 2016 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a
commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation.
MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.