KINTOãã¯ãããžãŒãº ã®æè¡ããã°
å š1113件
An Issue We Encountered During Testing With Spring Batch using DBUnit Introduction Hello. I am Takehana from the Payment Platform Team, Common Service Development Group[^1][^2][^3][^4][^5][^6] at the Platform Development Division. This time, I would like to write about an issue that we encountered while testing with Spring Batch + DBUnit. Environment Libraries, etc. Version Java 17 MySQL 8.0.23 Spring Boot 3.1.5 Spring Boot Batch 3.1.5 JUnit 5.10.0 Spring Test DBUnit 1.3.0 Encountered Issues We are using DB unit for testing Spring Boot 3 with Spring Batch. The Batch process follows the Chunk model, where ItemReader performs DB searches, and ItemWriter updates the DB. Given this setup, when running tests with data volumes exceeding the Chunk size, the tests did not complete... Investigations and Attempts Observations Code new StepBuilder("step", jobRepository) .<InputDto, OutputDto>chunk( CHUNK_SIZE, transactionManager) .reader(reader) .processor(processor) .writer(writer) .build(); I was testing a batch with the steps mentioned above as follows. @SpringBatchTest @SpringBootTest @TestPropertySource( properties = { "spring.batch.job.names: Foobar-batch", "targetDate: 2023-01-01", }) @Transactional(isolation = Isolation.SERIALIZABLE) @TestExecutionListeners({ DependencyInjectionTestExecutionListener.class, DirtiesContextTestExecutionListener.class, TransactionDbUnitTestExecutionListener.class }) @DbUnitConfiguration(dataSetLoader = XlsDataSetLoader.class) class FoobarBatchJobTest { @Autowired private JobLauncherTestUtils jobLauncherTestUtils; @BeforeEach void setUp() { } @Test @DatabaseSetup("classpath:dbunit/test_data_import.xlsx") @ExpectedDatabase( value = "classpath:dbunit/data_expected.xlsx", assertionMode = DatabaseAssertionMode.NON_STRICT_UNORDERED) void launchJob() throws Exception { val jobExecution = jobLauncherTestUtils.launchJob(); assertEquals(ExitStatus.COMPLETED, jobExecution.getExitStatus()); } } When I set the test data to be less than the chunk size, the test passed without any issues. However, when the test data exceeded the chunk size, the test froze and never completed. (This occurred even with a chunk size of 1 and a data count of 1) Suspecting the issue might be on DB connections, I noted that Spring Batch treats each chunk as a single transaction. If processing in parallel, it would require more DB connections than the number of concurrent executions. So I adjusted the pool size to test this hypothesis. spring: datasource: hikari: maximum-pool-size: I changed 10 to 100 among other adjustments, but the issue was still not resolved⊠Start debugging I set up debug logs and ran the application to observe the behavior. The execution seemed to stop at the log output on line 88 of org.springframework.batch.core.step.item.ChunkOrientedTasklet . So, I set a breakpoint to verify. I then reached line 408 of org.springframework.batch.core.step.tasklet.TaskletStep . It appeared that the semaphore couldnât acquire a lock (= waiting for the lock to be released), causing the execution to halt there. Delving deeper into Spring Batch Continuing my investigation, I traced the flow of execution in the step processing. The rough outline of the relevant parts is as follows. Execute doExecute of TaskletStep Create a semaphore Pass the semaphore to ChunkTransactionCallback , which is an implementation of TransactionSynchronization , link it with the transaction execution, and configure it in RepeatTemplate Step processing begins for the chunk The semaphore is locked in doInTransaction of TaskletStep Execute the main step processing The commit is executed by TransactionSynchronizationUtils` The AbstractPlatformTransactionManager âs triggerAfterCompletion method is called, and the in-process invokeAfterCompletion` is executed. The semaphore is released in the afterCompletion method of the ChunkTransctionCallback by the invokeAfterCompletion. If data remains, return to 4 During this test run, the semaphore of 9 was not released, and it passed through 4 again and ended up freezing at 5 . Why was the semaphore not released...? During the review mentioned above, at Step semaphore release , I found the following condition in the relevant code. status.isNewSynchronization() did not become true , so invokeAfterCompletion was not executed. org.springframework.transaction.support.DefaultTransactionStatus#isNewSynchronization is as follows: /** * Return if a new transaction synchronization has been opened * for this transaction. */ public boolean isNewSynchronization() { return this.newSynchronization; } It returns whether a new transaction synchronization has been opened for this transaction. Considerations The current situation is that we havenât fully traced yet why isNewSynchronization doesnât become true . However, I thought I might be able to find some clues in the logs from our various trial and error attempts. If @Transactional is not applied to the test class 2024-03-27T08:57:14.527+0000 [Test worker] TRACE o.s.t.i.TransactionInterceptor - Completing transaction for [org.springframework.batch.core.repository.support.SimpleJobRepository.update] Foobar-batch 19 2024-03-27T08:57:14.527+0000 [Test worker] DEBUG o.s.orm.jpa.JpaTransactionManager - Initiating transaction commit Foobar-batch 19 2024-03-27T08:57:14.527+0000 [Test worker] DEBUG o.s.orm.jpa.JpaTransactionManager - Committing JPA transaction on EntityManager [SessionImpl(1075727694<open>)] Foobar-batch 19 2024-03-27T08:57:14.534+0000 [Test worker] DEBUG o.s.orm.jpa.JpaTransactionManager - Closing JPA EntityManager [SessionImpl(1075727694<open>)] after transaction Foobar-batch 19 2024-03-27T08:57:14.536+0000 [Test worker] DEBUG o.s.b.repeat.support.RepeatTemplate - Repeat operation about to start at count=2 Foobar-batch 19 If @Transactional is applied to the test class 2024-03-27T09:04:04.600+0000 [Test worker] TRACE o.s.t.i.TransactionInterceptor - Completing transaction for [org.springframework.batch.core.repository.support.SimpleJobRepository.update] Foobar-batch 20 2024-03-27T09:04:04.601+0000 [Test worker] DEBUG o.s.b.repeat.support.RepeatTemplate - Repeat operation about to start at count=2 Foobar-batch 20 When @Transactional is applied, "Initiating transaction commit..." from JpaTransactionManager with @Transactionalis not being logged. The test class uses TransactionalTestExecutionListener and executes within the same transaction using @Transactional . This ensures that the test data registered with DBUnit is accessible to code under test and is rolled back after the test is completed. However, I concluded that isNewSynchronization does not become true because existing transactions are being reused (a new transaction is not started) when the same step is executed. Workaround As a brute-force workaround to avoid using TransactionalTestExecutionListener , I performed the cleanup manually after each test, which successfully prevented the freeze. class FoobarTestExecutionListenerChain extends TestExecutionListenerChain { private static final Class<?>[] CHAIN = { FoobarTransactionalTestExecutionListener.class, DbUnitTestExecutionListener.class }; @Override protected Class<?>[] getChain() { return CHAIN; } } class HogeTransactionalTestExecutionListener implements TestExecutionListener { private static final String CREATE_BACKUP_TABLE_SQL = "CREATE TEMPORARY TABLE backup_%s AS SELECT * FROM %s"; private static final String TRUNCATE_TABLE_SQL = "TRUNCATE TABLE %s"; private static final String BACKUP_INSERT_SQL = "INSERT INTO %s SELECT * FROM backup_%s"; private static final List<String> TARGET_TABLE_NAMES = List.of( "Foobar", "fuga", "dadada"); /** * Create a test working table * * @param testContext * @throws Exception */ @Override public void beforeTestMethod(TestContext testContext) throws Exception { val dataSource = (DataSource) testContext.getApplicationContext().getBean("dataSource"); val jdbcTemp = new JdbcTemplate(dataSource); // Backup existing data to a temporary table before testing TARGET_TABLE_NAMES.forEach( tableName -> jdbcTemp.execute(String.format(CREATE_BACKUP_TABLE_SQL, tableName, tableName))); // Table initialization TARGET_TABLE_NAMES.forEach( tableName -> jdbcTemp.execute(String.format(TRUNCATE_TABLE_SQL, tableName))); } /** * Drop the test working table * * @param testContext * @throws Exception */ @Override public void afterTestMethod(TestContext testContext) throws Exception { val dataSource = (DataSource) testContext.getApplicationContext().getBean("dataSource"); val jdbcTemp = new JdbcTemplate(dataSource); // Restore the table TARGET_TABLE_NAMES.forEach( tableName -> jdbcTemp.execute(String.format(TRUNCATE_TABLE_SQL, tableName, tableName))); TARGET_TABLE_NAMES.forEach( tableName -> jdbcTemp.execute(String.format(BACKUP_INSERT_SQL, tableName, tableName))); } } Remove TransactionDbUnitTestExecutionListener and avoid using TransactionalTestExecutionListener. (Use DbUnitTestExecutionListener to lode the test data from Excel) Create a custom TestExecutionListener and move data from the target table to a temporary table during pre-processing, then restore it after the test. beforeTestMethod is executed before the test method, and afterTestMethod is executed after the test method. This approach made it possible to run tests while preserving Springâs transaction management. Impressions Despite extensive searches, I couldnât find satisfactory information, leaving the issue in a state of uncertainty. However, by looking further into the Spring Boot source code, I made various discoveries and it turned out to be a valuable learning experience through code reading. (Although I havenât fully grasped everything yetâŠ) I was wondering if I was fundamentally misunderstanding how to use Spring and the test libraries, questioning whether I was implementing them correctly based on the library creatorsâ assumptions and if there were more suitable classes available. This has highlighted that I still have much to learn. I would like to continue to approach exploration and improvement with the same curiosity, asking, âHow does this work?â Thank you for reading this article. I hope this will be helpful to others facing similar issues. [^1]: Post 1 by a member of the Common Service Development Group [ Domain-Driven Design (DDD) incorporated in a payment platform intended to allow global expansion ] [^2]: Post 2 by a member of the Common Service Development Group [ Remote Mob Programming: How a Team of New Hires Achieved Success Developing a New System Within a Year ] [^3]: Post 3 by a member of the Common Service Development Group [ Efforts to Improve Deploy Traceability to Multiple Environments Utilizing GitHub and JIRA ] [^4]: Post 4 by a member of the Common Service Development Group [ Creating a Development Environment Using VS Code's Dev Container ] [^5]: Post 5 by a member of the Common Service Development Group [ Spring Boot 2 to 3 Upgrade: Procedure, Challenges, and Solutions ] [^6]: Post 6 by a member of the Common Service Development Group [ Guide to Building an S3 Local Development Environment Using MinIO (RELEASE.2023-10) ]
Introduction Hello. I am Nakaguchi from KINTO Technologies' Mobile App Development Group. I lead the iOS team for the KINTO Easy Application app which I will refer to as âthe iOS teamâ in this article for convenience. We hold Retrospectives irregularly, but I find that they can be rather challenging. Am I succeeding in bringing out everyone's true feelings?? What are the team's real challenges?? Is my facilitation effective?? etc. I recently watched a webinar by Classmethod, Inc. and was so impressed by their session on "How to Build a Self-Managed Team" that I decided to apply for another training session they introduced in it about Retrospectives. In this article, I'll share my experience attending that session. Pre-Alignment Session Before the Retrospective, we had a meeting with Mr. Abe and Mr. Takayanagi from Classmethod. In order to hold Retrospectives that were best suited to our teamâs situation, we discussed the current status of the iOS team with them for nearly an hour. Overview of the Retrospective On the day of the Retrospective, Mr. Takayanagi and Mr. Ito came to the company to facilitate the meeting. The meeting lasted for about two hours and followed this general flow: Self-introductions Aligning the purpose of our Retrospectives Individual exercise on âHow to make the team a little bit betterâ Same content as above but in pairs Sharing the findings with the whole team Thinking about specific action plans in pairs Sharing the findings with the whole team Closing First Half Out of the almost two-hours meeting, it is worth noting that about half of the time was spent on "1. Self-introductions" and "2. Aligning the purpose of our Retrospectives". During the segment "1. Self-introductions", the facilitators asked us questions such as our names or nicknames, our roles in the team, or the extent of our interactions with other team members. They looked not only at the atmosphere of the team and the personality of each of us, but also at the relationships and compatibility between team members. During "2. Aligning the purpose of our Retrospectives", I got everyone to agree on what can be done to make the current team a little better , which was a topic I had requested. After a major release last September, our team is currently focused on improving features and refactoring, so although we are in a less busy spot, it seems that it is no easy feat to improve teams in our situation to make them a little better . I also explained the purpose, role, and expectations for each participant that I, as the meeting organizer, had in mind when inviting them. I was told that this helps clarify how everyone should participate and makes it easier for them to speak up. I think it was a good opportunity for me to talk about things that I usually donât have the right timing for or that I canât speak about directly. By spending this time in the first half of the meeting, we were able to create an atmosphere where it was easy for everyone to speak, and I felt that overall rapport was greatly improved. Facilitation Second Half After thinking about " 3. Making the team a little better" individually, we proceed on with the work. However, we didnât use any framework related to retrospectives. Instead, we simply wrote down what could make the team a little better on sticky notes. We did individual work and then moved on to pair work. There are situations where pair work is beneficial and others where it is not. In this case, it seemed like the team benefited from it. Also, the combination of people is key, as it is important not to cause psychological strain amongst the participants. Pair Work After that, everyone gave presentations, and there were many opinions that I was not able to draw out in the Retrospectives I have held so far. I felt that I was able to draw them out through the rapport we built and the pair work in the first half. Then, based on the opinions that came up, everyone was asked to think about what specific actions should be taken and 6. Thinking about specific action plans in pairs. Then, each team presented their ideas. Presentation As a result, we decided to implement the following actions: Creating a Slack channel Having a place where everyone can chat freely Setting up a weekly meeting dedicated to chatting We could build more trust by talking more about ourselves, so we decided to create a private channel instead of a public one. Trying to gather together at meeting rooms as much as possible (as many people used to attend online to meetings from their desks even if they were in the office). Setting up guideline consultation meetings regarding assigned tasks Clearly stating the deadline on the task tickets We are addressing these issues as quickly as possible, starting the next day. Closing At the end of the meeting, Mr. Takayanagi talked about the importance of customizing meetings, such as understanding the time allocation of meetings, the characteristics of participants and to draw their opinions. In particular, at this Retrospective, he focused his facilitation on people , using a lot of pair work. Closing Post-Retrospective Survey Results Here are the results of the feedback survey taken after the Retrospective (out of 10 responses). Change in evaluation Before: 6.3 -> After: 9 NPS 80 (What is NPS?) AI summary of "How satisfied did you feel after you participated?" (free text) The survey results showed that participants were happy with the session and the facilitator's explanations. In addition, there were many positive comments about how specific decisions were made that led to the next actions. Furthermore, the opportunity to understand the thoughts of other team members, and the ability to listen to things that are not normally heard, were also highly evaluated. These results suggest that the meeting was meaningful for everyone. ** Just being above 0 was a great, but there was a whopping NPS of 80! ** Final Thoughts Through this Retrospective, I realized that there were many members who felt that there was a lack of communication, and we were able to focus on the next course of action so it was a very fulfilling Retrospective. I was happy to see from the questionnaire results that the participating members were also satisfied. I also realized that the role of the meeting facilitator is very important. This is a very advanced skill that cannot be acquired overnight, and I think that the organization should focus on developing and acquiring such skills. To start with, I would like to study facilitation and become able to conduct better meetings.
Introduction Hello. I am Nakaguchi from KINTO Technologies' Mobile App Development Group. I lead the iOS team for the KINTO Easy Application app which I will refer to as âthe iOS teamâ in this article for convenience. We hold Retrospectives irregularly, but I find that they can be rather challenging. Am I succeeding in bringing out everyone's true feelings?? What are the team's real challenges?? Is my facilitation effective?? etc. I recently watched a webinar by Classmethod, Inc. and was so impressed by their session on "How to Build a Self-Managed Team" that I decided to apply for another training session they introduced in it about Retrospectives. In this article, I'll share my experience attending that session. Pre-Alignment Session Before the Retrospective, we had a meeting with Mr. Abe and Mr. Takayanagi from Classmethod. In order to hold Retrospectives that were best suited to our teamâs situation, we discussed the current status of the iOS team with them for nearly an hour. Overview of the Retrospective On the day of the Retrospective, Mr. Takayanagi and Mr. Ito came to the company to facilitate the meeting. The meeting lasted for about two hours and followed this general flow: Self-introductions Aligning the purpose of our Retrospectives Individual exercise on âHow to make the team a little bit betterâ Same content as above but in pairs Sharing the findings with the whole team Thinking about specific action plans in pairs Sharing the findings with the whole team Closing First Half Out of the almost two-hours meeting, it is worth noting that about half of the time was spent on "1. Self-introductions" and "2. Aligning the purpose of our Retrospectives". During the segment "1. Self-introductions", the facilitators asked us questions such as our names or nicknames, our roles in the team, or the extent of our interactions with other team members. They looked not only at the atmosphere of the team and the personality of each of us, but also at the relationships and compatibility between team members. During "2. Aligning the purpose of our Retrospectives", I got everyone to agree on what can be done to make the current team a little better , which was a topic I had requested. After a major release last September, our team is currently focused on improving features and refactoring, so although we are in a less busy spot, it seems that it is no easy feat to improve teams in our situation to make them a little better . I also explained the purpose, role, and expectations for each participant that I, as the meeting organizer, had in mind when inviting them. I was told that this helps clarify how everyone should participate and makes it easier for them to speak up. I think it was a good opportunity for me to talk about things that I usually donât have the right timing for or that I canât speak about directly. By spending this time in the first half of the meeting, we were able to create an atmosphere where it was easy for everyone to speak, and I felt that overall rapport was greatly improved. Facilitation Second Half After thinking about " 3. Making the team a little better" individually, we proceed on with the work. However, we didnât use any framework related to retrospectives. Instead, we simply wrote down what could make the team a little better on sticky notes. We did individual work and then moved on to pair work. There are situations where pair work is beneficial and others where it is not. In this case, it seemed like the team benefited from it. Also, the combination of people is key, as it is important not to cause psychological strain amongst the participants. Pair Work After that, everyone gave presentations, and there were many opinions that I was not able to draw out in the Retrospectives I have held so far. I felt that I was able to draw them out through the rapport we built and the pair work in the first half. Then, based on the opinions that came up, everyone was asked to think about what specific actions should be taken and 6. Thinking about specific action plans in pairs. Then, each team presented their ideas. Presentation As a result, we decided to implement the following actions: Creating a Slack channel Having a place where everyone can chat freely Setting up a weekly meeting dedicated to chatting We could build more trust by talking more about ourselves, so we decided to create a private channel instead of a public one. Trying to gather together at meeting rooms as much as possible (as many people used to attend online to meetings from their desks even if they were in the office). Setting up guideline consultation meetings regarding assigned tasks Clearly stating the deadline on the task tickets We are addressing these issues as quickly as possible, starting the next day. Closing At the end of the meeting, Mr. Takayanagi talked about the importance of customizing meetings, such as understanding the time allocation of meetings, the characteristics of participants and to draw their opinions. In particular, at this Retrospective, he focused his facilitation on people , using a lot of pair work. Closing Post-Retrospective Survey Results Here are the results of the feedback survey taken after the Retrospective (out of 10 responses). Change in evaluation Before: 6.3 -> After: 9 NPS 80 (What is NPS?) AI summary of "How satisfied did you feel after you participated?" (free text) The survey results showed that participants were happy with the session and the facilitator's explanations. In addition, there were many positive comments about how specific decisions were made that led to the next actions. Furthermore, the opportunity to understand the thoughts of other team members, and the ability to listen to things that are not normally heard, were also highly evaluated. These results suggest that the meeting was meaningful for everyone. Just being above 0 was a great, but there was a whopping NPS of 80! Final Thoughts Through this Retrospective, I realized that there were many members who felt that there was a lack of communication, and we were able to focus on the next course of action so it was a very fulfilling Retrospective. I was happy to see from the questionnaire results that the participating members were also satisfied. I also realized that the role of the meeting facilitator is very important. This is a very advanced skill that cannot be acquired overnight, and I think that the organization should focus on developing and acquiring such skills. To start with, I would like to study facilitation and become able to conduct better meetings.
âKINTOãµãŒãã¹ã®èªèšŒåºç€ã«ã€ããŠãéçºãæ
åœããŠããPham Hoangã§ããæ¬èšäºã§ã¯ãGlobal KINTO ID Platform (GKIDP) ã«å®è£
ããããã¹ããŒã«ã€ããŠã話ããŸãã OpenID Summit Tokyo 2024 ã«åå ããŠãOIDC ãšçµã¿åãããããã¹ããŒã«ã€ããŠäŒºã£ãŠããããã¹ããŒãç§ãã¡ã®IDãã©ãããã©ãŒã ã«ã©ãã ãå€ãã®å©çããããããã€ããŠããäŒãããããšæããŸããã I. GKIDP ã§ã®ãã¹ããŒã®èªåå
¥å ãã¹ããŒã¯ããã¹ã¯ãŒãã®ä»£æ¿ãšãªããã®ã§ããŠãŒã¶ãŒã®ç«¯æ«ããããéããããç°¡åã«ãããå®å
šã«ããŠã§ããµã€ããã¢ããªãžãµã€ã³ã€ã³ããããšãã§ããŸãã以äžã¯ããŠãŒã¶ãŒãã¯ã³ã¯ãªãã¯ã§ãã¹ããŒèªèšŒãè¡ãæ¹æ³ã§ãã  å³1.KINTO Italyã®IDãã©ãããã©ãŒã ãžãã¹ããŒã§ãã°ã€ã³ããæ§å ãã¹ããŒã®çŽ æŽããããšããã¯ã·ãŒã ã¬ã¹ãªUXã§ããã¹ ã¯ãŒã ã®èªåå
¥åæ©èœãšåãã§ãããŠãŒã¶ãŒã¯ãã¹ããŒãšãã¹ã¯ãŒãã®è€éãªéããç解ããå¿
èŠã¯ãããŸããããã®ã·ã¹ãã ã¯ããŠãŒã¶ãŒãèŠããŠããå¿
èŠã®ãããã¹ã¯ãŒããªã©ã䜿ããã«ãè£åŽã§é察称æå·åã䜿çšããŸããFaceIDèªèšŒã ãã§ããã¹ãŠã®èšå®ãå®äºããŸãã ãã¹ããŒã¯ã2022幎åŸåããAndroidãšiOSã«ãã£ãŠãµããŒããããŠãããæãå®å
šã§æå
端ã®èªèšŒã·ã¹ãã ã§ãããŸã éçºäžã§ãçŸåšãã¢ããã°ã¬ãŒãããç¶ããŠããŸããGKIDP (Global KINTO ID Platform)ã«ææ°æè¡ã§äŸ¿å©ãªç¶æ
ãä¿ã€ããã2023幎7æã«ãã¹ããŒã®èªåå
¥åæ©èœãå°å
¥ããŸããããã®å°å
¥ã¯ãã¡ã«ã«ãªãã€ããŒãžã£ãã³ãGitHubãMoneyForwardã§ããããå°å
¥ããããããšã®ããšã§ãã 次ã®ããŒãã§ã¯ããã¹ããŒãFederated LoginïŒé£æºãã°ã€ã³ïŒã«æŽ»çšããGKIDPãŠãŒã¶ãŒããã°ããŒãã«ãã°ã€ã³ãæ©èœãããå¿«é©ã«å©çšã§ããããã«ããæ¹æ³ã«ã€ããŠèª¬æããŸãã II. Federated Identityã«ããããã¹ã㌠Global KINTO ID Platform (GKIDP) ã¯ã2024幎3ææç¹ã§ã€ã¿ãªã¢ããã©ãžã«ãã¿ã€ãã«ã¿ãŒã«ãšåç±³ååœã«å°å
¥ãããŠããKINTOãµãŒãã¹ã®èªèšŒã·ã¹ãã ã§ããGDPRããã³ãã®ä»ã®ããŒã¿ä¿è·èŠå¶ã«éµå®ãããããGKIDPã¯ååœããšã«è€æ°ã®IDãããã€ããŒïŒIDPïŒã«åããããŠããããã³ãŒãã£ããŒã¿ãŒããéããŠãŠãŒã¶ãŒãäžã€ã®ã°ããŒãã«IDãšããŠèå¥ããŸããã°ããŒãã«ID ã掻çšããããšã§ããŠãŒã¶ãŒã¯äžçäžã®KINTOãµãŒãã¹ãå
±éã®IDã§å©çšããããšãã§ããŸãã å³2.GKIDP ãšãã¹ããŒå¯Ÿå¿ã®IDP éåžžããã¹ããŒã§ãã°ã€ã³(å³1ãåç
§)ããããšããŠãŒã¶ãŒã¯ããŒã«ã«IDPã䜿çšããŠèªèšŒé£æºãè¡ããèªåœå
ã®KINTOãµãŒãã¹ãå©çšã§ããŸããããããç§ãã¡ã®å ŽåãRP(Relying Party)ã®ã¢ããªã±ãŒã·ã§ã³ãŸãã¯ãã©ãžã«ã® KINTO ONE Personal ããã®ä»ã®KINTOãµãŒãã¹ã®ãããªããµãã©ã€ããµãŒãã¹ãã§ãã¹ããŒæ©èœã䜿ããªããšãããªããããååœã®IDP (äŸïŒãã©ãžã«IDP)ã«ãã¹ããŒãå®è£
ããŸããã ãã®å©ç¹ã«ã€ããŠãç§ãã¡ãåå ãã OpenID Summit Tokyo 2024 ã§ãåãäžããããŠããããã¹ããŒãOpenID Connectãããã³ã«ãšçµã¿åãããŠå®è£
ããããšãæšå¥šãããŠãããšç¥ããŠè¯ãã£ãã§ãã ããã«GKIDPã«ã¯ãKINTOãµãŒãã¹ãããä»åœã«ãŠãŒã¶ãŒãæ
è¡ãåŒè¶ããããéãèªåœãµãŒãã¹ãšåæ§ã«åœå€ãµãŒãã¹ã§ãKINTOãŸãã¯é¢é£ãµãŒãã¹ã«ãã°ã€ã³ã§ããç¬èªã®æ©èœããããŸãããããç§ãã¡ã¯ãã°ããŒãã«ãã°ã€ã³ãæ©èœãšåŒãã§ããŸããå©çšã«ã¯è€æ°ã®ã¹ããããå¿
èŠã§ãããïŒã€ã®ãŠãŒã¶ãŒåãšãã¹ã¯ãŒãã§ç®¡çã§ããã®ã§ããµãŒãã¹ããšã«ãŠãŒã¶ãŒåãšãã¹ã¯ãŒããèŠããªããŠãè¯ããªããŸããããã«ãã¹ããŒå®è£
ã«ãã£ãŠããã°ã€ã³æ
å ±ãèŠãããå
¥åãããããå¿
èŠãªããç°¡åãªæé ã§ã°ããŒãã«ãŠãŒã¶ãŒã®ãã°ã€ã³ããã»ã¹ã®ç¡é§ããªãããŸããäŸãã°ãã€ã¿ãªã¢ã®KINTO GOãŠãŒã¶ãŒïŒå³1ã®ãŠãŒã¶ãŒïŒããã°ããŒãã«ãã°ã€ã³ãå©çšããŠã¿ã€ã®KINTO SHAREãµãŒãã¹ã«ã¢ã¯ã»ã¹ããæ¹æ³ãèŠãŠã¿ãŸãããããããæ°åã®ã¯ãªãã¯ã§ãã°ã€ã³æéãå¹³å2ïœ3åããçŽ30ç§ã«ççž®ããããšãã§ããŠããŸãïŒå³3ïŒãããŒã«ã«IDPããã¹ããŒããµããŒãããŠãããã©ããã«é¢ä¿ãªãã1ã€ã®ãã¹ããŒã䜿çšããŠãã¹ãŠã®KINTOãµãŒãã¹ã«ã¢ã¯ã»ã¹ã§ããŸãã  å³3. ãã¹ããŒã«ããã°ããŒãã«ãã°ã€ã³ ãã¹ããŒã¯ãããŒã«ã«ãã°ã€ã³ãšã°ããŒãã«ãã°ã€ã³ã ãã§ãªããåèªèšŒãªã©ãå«ããã¹ãŠã®èªèšŒç»é¢ã«ã掻çšãããŠããŸããäžåºŠãã¹ããŒãç»é²ããããšããŠãŒã¶ãŒã¯äœãã確èªããããã®ãã¹ã¯ãŒãããã¯ãã»ãšãã©å¿
èŠãšããŸããã III. ãã¹ããŒãšãã®éèŠ å³4. ãã¹ããŒç»é²ãŠãŒã¶ãŒ ã€ã¿ãªã¢ã®IDPã§ã¯ã875åã®ãŠãŒã¶ãŒãã¹ããŒãå©çšããŠç»é²ããŠããããã¹ããŒãªãªãŒã¹åŸã®æ°èŠãŠãŒã¶ãŒã®52.2ïŒ
ãå ããŠããŸãããã¹ããŒã®èªåå
¥åããµããŒãããOSã«ã¢ããããŒããããŠãŒã¶ãŒãå¢ããã«ã€ããŠã«ã€ããŠããã®å²åãå¢ããããšãæåŸ
ããŠããŸãã(iOS 16.0以äžãAndroid 9以äž) ãã¹ã¯ããããŠãŒã¶ãŒãå€ããå ããKINTO Brazilã§ã¯ãMicrosoft PCã§ãã¹ããŒãåºãå©çšãããŠããªãã«ãé¢ãããããªãªãŒã¹åŸã®æ°èŠç»é²ãŠãŒã¶ãŒ1176人ã®ãã¡20ïŒ
以äžããã¹ããŒã䜿çšããŠããŸãã IV. ãããã« KINTOã®ãšã³ãžãã¢ãšããŠããã¹ã¯ãŒãã¬ã¹ã®æªæ¥ã®ããã«æ°ããæè¡ãå°å
¥ãããŠãŒã¶ãŒã®ããŒã¿ä¿è·ã匷åã§ããããšããšãŠãå¬ããæããŸãããã¹ããŒã掻çšããããšã§ããŠãŒã¶ãŒã¯æé«ã¬ãã«ã®ã»ãã¥ãªãã£ã§ç°¡åã«ãã°ã€ã³ã§ããããã«ãªããŸãããããããããäžçäžã®KINTOãµãŒãã¹ãæ°ããæã
ã®IDPããïŒGKIDPã«ç¹ãããšãã§ããã®ã楜ãã¿ã«ããŠããŸãã Hoang Phamã®ä»ã®èšäºã¯ãã¡ã: https://blog.kinto-technologies.com/posts/2022-12-02-load-balancing/
[[[Amazonãžã®ãªã³ã¯]]]( https://amzn.asia/d/06GXK0Fd ) ãã³ã¹ã»Pã»ããããŒããµãã¿ã³ã»ã¹ã«ã€ãŽã¡ã³ã·å
±è ãVisionãã®å
容ãå¿ããªãããåå¿é²ãšããŠãŸãšããããšèããŠãããŸãããããšãŠãè¯ãæ¬ãªã®ã§å
±æããããšæããããã«ãã®äžéšã玹ä»ããããŸãã æ¥åžžã«æº¢ãããã¶ã€ã³ãããããžã¥ã¢ã«ã¯ãç§ãã¡ã«æ§ã
ãªææ
ãåŒã³èµ·ãããŸãããªãç¹å®ã®ããžã¥ã¢ã«ãç§ãã¡ã«åŒ·ãå°è±¡ãäžããã®ãããŸããã®èåŸã«ããå¿çãã©ã®ããã«ç解ããããããã®æ¬ã¯è§£ãæãããŠãããŸãã èè
ã¯ããžã¥ã¢ã«ãéããŠã¹ããŒãªãŒãèªãããã®å
·äœçãªæ¹æ³ãäŸãã°è²åœ©ã圢ã®éžæãææ
ã«ã©ã®ããã«äœçšããããæããŠãããŸããããã«ãããå°é家ã§ãªããšãæ¥ã
ã®èŠèŠçäœéšãè±ãã«è§£éã§ããããã«ãªããšæããŸãã ãVisionããèªãããšã§ãç§éã®æ¥åžžã«æ°ããªèŠç¹ãçãŸãããšæããŸãããã®ããã°ãéããŠèå³ãæãããæ¹ã¯ããã²æã«åã£ãŠã¿ãããšããå§ãããŸãã ãã¡ãã®æžç±ã¯ä»¥äžã®å
容ã§æ§æãããŠããŸãã åºæ ã¯ããã« ããžã¥ã¢ã«ã³ããã¥ã±ãŒã·ã§ã³ã®ããã»ã¹ãšã¯ ç»åã®å¿çåŠ ã©ã€ã³ ã·ã§ã€ã æ床 è² å
ã«ã¡ã© æ§å³ ãŸãšã ä»åã¯ãã®äžã§ãããžã¥ã¢ã«ã³ããã¥ã±ãŒã·ã§ã³ã®ããã»ã¹ãšã¯ããç»åã®å¿çåŠããã©ã€ã³ãã®å
容ãããã€ãŸãã§çŽ¹ä»ããŠããããšæããŸãã ããžã¥ã¢ã«ã³ããã¥ã±ãŒã·ã§ã³ã®ããã»ã¹ãšã¯ ããžã¥ã¢ã«ã³ããã¥ã±ãŒã·ã§ã³ã®ããã»ã¹ãšã¯ãç®ããå
¥ã£ããã®ãç¬æã«æ§ã
ãªææ
ãåŒãèµ·ããèªåçåŠçã ãšèè
ã¯èšã£ãŠããŸãã äŸãã°ããèæãè·¯å°ã«äŒžã³ã圱ããããã§ææã«ãã®ã®ã人ããæãããæ ç»ã®ãã¹ã¿ãŒãèŠãã ãã§ãç§éã¯ãã®æ ç»ãäžå®ãææãããŒãã«ããŠããã®ã ãšçŽæçã«èªèããŸãããã®ç¬éçãªææ
ã®åå¿ã¯èªåçã«åŒãèµ·ããããŠãããã®ãªã®ã ãšããããšã§ãã ãã®æ¬ã®ç®çã¯ãèªè
ããã®ãããªèªåçåŠçãããã»ã¹ãèŠçŽ ã«å解ãããªããããã£ãæ°æã¡ãåŒãèµ·ããããã®ããç解ã§ããåãã€ããããšã ãšè¿°ã¹ãããŠãããæ©é次ã®ç« ã§ã¯ãã®èªååŠçãå¿ççåŽé¢ãã説æããŠãããŸãã ç»åã®å¿çåŠ ç»åãèŠãŠããªã©ãã¯ã¹ãããææãæãããããã®ã¯ãªããããã®ããã»ã¹ã説æããã«ãããç»åãåãŒãå¿çåŠçåŽé¢ã®äžèŠçŽ ã«ã€ããŠèšåããŠããŸãã â é¢é£ä»ã â¡ã¡ã«ããºã â¢é¿ããšã â é¢é£ä»ã äŸãã°ãèæãè·¯å°è£ãšæã圱ãçµã¿åããããšãææãæããããšãäžè¬çã§ãããã®ããã«ãç»åãæ åã¯ç§ãã¡ã®éå»ã®èšæ¶ã«ãªã³ã¯ããŠãããè³ã¯ããããèŠããšèªåçã«ç¹å®ã®ææ
ãæ³èµ·ãããããã§ããããã¯ãé£æ³ãã®ããã»ã¹ã«äŒŒãŠããŸãã ãããã£ãŠãé©åãªããžã¥ã¢ã«èŠçŽ ãéžæãé¢é£ä»ããããšã§ãäœåã¯èŠã人ã«åŒ·çãªå°è±¡ãäžããããšãã§ããŸã®ã ãšãããŸãã â¡ã¡ã«ããºã èŠèŠãã¶ã€ã³ã«ãããŠãã©ã€ã³ãã·ã§ã€ããè²ãšãã£ãèŠçŽ ã®çµã¿åããã¯éèŠãªåœ¹å²ãæãããŸããäŸãã°å¯Ÿç«è²â»1ãé£ãåããã«é
眮ããããšå¯Ÿæ¯ãçããŠåºæ¿ãçã¿åºããŸãããã®æ§ã«èŠèŠèŠçŽ ãçžäºäœçšããŠæã«åºæ¿ã調åãçãããããšããããšã§ãã â¢é¿ããšã ãèšãããšããããšããé¿ããã®ã¯äŒããããšããå
容ãšãã®äŒãæ¹ãäžèŽãããšãã ããïŒåŒçš p20ïŒ äŸãã°å€§åãªäººã®æ²çãªãæ»ãèªãå Žé¢ã«ããããªã«ã©ãŒãªã³ã°ã䜿çšããå Žåããã®æ²ãã¿ã¯äŒããã¥ãããªããšãã£ãå
·åã«ãå
容ãšäŒãæ¹ãäžèŽããŠãªããã®ã¯èŠãŠãã人ã®å¿ã«é¿ããªããšããããšã§ãã ããããè²åœ©ãªã©ã®ãã¶ã€ã³èŠçŽ ãç©æ¥µçã«çµã¿åãããããšã§ããçµµãã®é
åãåäžãããšãèè
ã¯åŒ·èª¿ããŠããŸããããã«ãããããèŠçŽ ããå¶ç¶ãããããããŸãŸãã«ä»»ããã¹ãã§ã¯ãªããæå³çã«éžæããããšã«ãã£ãŠèŠã人ã®ææ
ã«èšŽããããã¹ãã ãšè¿°ã¹ãŠããŸãã ç»åã®ã¢ããã㌠ã¢ããããŒãšã¯ã解ååŠãã®ããšã§ãã 以äžã«åæããé
ç®ã䜿ã£ãŠãçµµããå解ããŠããããšã§ãèŠæ¹ããæ§ç¯ããŠããããšãå¯èœã«ãªããšããããããããžã¥ã¢ã«ã§ã¹ããŒãªãŒãèªãããã®åºæ¬ã ãšèè
ã¯è¿°ã¹ãŠããŸãããããŠãã€ã§ãèŠè¿ãããšãåºæ¥ãããã«ããŠããããšããå§ãããŠããŸãã 被åäœ æåéã被åäœã®ããšã ãã©ãŒããã: ç»åã®çžŠæšªæ¯ã åã: 瞊é·ãããã¯æšªé·ã ãã¬ãŒãã³ã°: æ§å³å
ã®é
眮ã ã©ã€ã³: ç·ç¶ã®èŠçŽ ã ã·ã§ã€ã: ãã¬ãŒã å
ã®åœ¢ç¶ã æ床ïŒããªã¥ãŒïŒ: æãããŸãã¯æãã®åºŠåãã è²: æåéãè²ã®ããšã ãã¿ãŒã³: ãã¶ã€ã³ãŸãã¯ç¹°ãè¿ãã®èŠçŽ ã ã·ã«ãšãã: ãã¶ã€ã³èŠçŽ ã®èŒªéå
ãé»ãå¡ãã€ã¶ãããã®ã ãã¯ã¹ãã£: ãã¶ã€ã³èŠçŽ ã®èŒªéã瀺ãæ
å ±ã å
: æããèŒãèŠçŽ ã 奥è¡ã: 空éã®æèŠã ãšããž: ã·ã§ã€ããéãŠãå¢çã®åŒ·åŒ±ã åã: ãã¹ãŠã®åãèŠçŽ ã ã©ã€ã³ ã©ã€ã³ã¯ãæ§å³ç·ãããã³ã³ããžã·ã§ãã«ã©ã€ã³ããšåŒã°ããèŠç·ããã©ãçµè·¯ãäœãåºããŸããåºæ¬ãããŠè»œèŠãããã¡ã§ãããå€æ§ãªåŽé¢ãæã¡æ§ã
ãªæŒåºãå¯èœã«ããåãæã€ãšèè
ã¯è¿°ã¹ãŠããŸããäžå³ã¯äž»ãªã©ã€ã³ã®äŸã®å³è§£ïŒäžéšæç²ïŒãšãªã£ãŠããŸãã ãã¬ãŒã ã®å¢çç·ã1~4 å
šãŠã«è©²åœãã©ã®æ§å³ã«ãå¿
ãååšããäžäžå·Šå³ã®æ ç·ã®ããšã§ãã 1ã»2ïŒæ§å³å
ã®äººç©ãããã®æ¹åã«å¿ããŠæ§å³ç·ã«ãªã£ãŠããŸãã 3ïŒãªããžã§ã¯ãã®å®éã®åãããã³æ瀺ãããåãããæ確ãªã©ã€ã³ã圢æããŠããŸãã 4ïŒæãå¡ããæ§å³ç·ã«ãªã£ãŠããŸãã ã©ã€ã³ã®æ¹å ã©ã€ã³ã®æ¹åãšã¯ãã¬ãŒã äžäžå·Šå³ã®æ ç·ã«å¯Ÿããã©ã€ã³ã®äœçœ®é¢ä¿ã®ããšã§ããã©ã€ã³ã®æ¹åã§ææ
ãè¡šçŸããããšãå¯èœã§ãé©åãªã¢ããŒããšçµã¿åãããããšã§è±ããªææ
ãè¡šãããšãã§ããŸãã äŸïŒ åçŽïŒéåã«æã匷ããæ°åïŒæšã建ç©ãªã©é äžé«ããã³ãããã®ïŒ æãïŒæ°Žå¹³åçŽã«å¯Ÿããã³ã³ãã©ã¹ãã«ããããã©ãããšãã«ã®ãŒããã€ãããã¯ãïŒåŽ©ãããã©ã³ã¹ãšåæïŒ æ°Žå¹³ïŒç©ãããéããïŒæ°Žå¹³ç·ãæµ·ãéããå ŽæïŒ ã©ã€ã³ã®é
眮 ã©ã€ã³ã®é
眮ã«ãã£ãŠãã¬ãŒã ãåå²ãããã·ã§ã€ããçã¿åºãããŸãããã®ã·ã§ã€ãã®ãã©ã³ã¹ã«ãã£ãŠæ§å³ã®é
åãå€åããŸãã åçåå²ãå·Šå³å¯Ÿç§°ïŒéèªç¶çã人工çã é察称ïŒãã©ã³ã¹æ¬¡ç¬¬ã§é
åçã«ãªããäžåå²ãé»éæ¯ãªã©ã ã©ã€ã³ã®è³ª ã©ã€ã³ã®è³ªãç¹åŸŽã¯ææ
ã匷ãåèµ·ããŸãã çŽç·ïŒç·åŒµæ æ²ç·ïŒãœããæ 倪ç·ïŒå匷ããé äžã 極现ç·ïŒæŽç·Žãç¹çŽ°ã 調åãšå¯Ÿæ¯ ãã¬ãŒã å
ã«ã©ã€ã³ãæããé端ã«ã調åã察æ¯ãçã¿åºãããŸããã€ãŸãã©ã€ã³å士ã®é¢ä¿ããªãºã ã調åãäžèª¿åããã©ã³ã¹ãã¢ã³ãã©ã³ã¹ãçµ±äžãªã©ãçã¿åºããšããããšã§ãã äŸãã°äžç«¯ã«æ°Žå¹³ãªã©ã€ã³ã¯èª¿åãçã¿åºããããããæãã«ããããšã«ãã£ãŠé端ã«å¯Ÿæ¯ãçããããšã«ãªããããã調åã察æ¯ãè¡ãéãããšéå±ããç
©éãã«ã€ãªããã®ã§ãã©ã³ã¹ã«ã¯æ³šæãå¿
èŠã ãšããããšã§ãã ãªãºã ã©ã€ã³ãç¹°ãè¿ãããšã«ãã£ãŠãªãºã ãçããæ§å³ã«æ°ããªåŽé¢ãå ãããŸãã äžå®ééã§èŠåçãªã©ã€ã³ïŒæŽç¶ããïŒéå±ãïŒ ã©ã³ãã ãªç¹°ãè¿ãïŒãšãã«ã®ãã·ã¥ãç·åŒµæ ããŸãšãã é©åã«é¢é£ä»ãããããã¶ã€ã³èŠçŽ ã䜿çšããããšã«ããäžæãã¡ã«ããºã ãåãèŠã人ã®å¿ã«é¿ãããžã¥ã¢ã«ã«ãªããããšãã·ã³ãã«ãªã©ã€ã³ãšããèŠçŽ ã§ãã£ãŠãææ
ãç·åŒµæãéå±ãã調åã察æ¯ãšãã£ãæŒåºãå¯èœã ãšããããšã§ãã ããã«èè
ãç¹°ãè¿ããŠããã®ã¯ãããã£ããŒã«ã«ãšãããããåçŽåããŠèãããããšããããšã§ãããããç¹°ãè¿ããã¡ã«æ§å³äœãã«å¯Ÿããç解ãæ·±ãŸããèªåãªãã«å¿çšãå©ããããšãã§ããããã«ãªãã¯ãã ããšè¿°ã¹ãŠããŸãã 以äžãåºç€ãäžéšãã玹ä»ãããšãã圢ã§æžãããŠããã ããŸãããã玹ä»ããéšåã ãã§ãããžã¥ã¢ã«ã®åæã«ã€ããŠèŠéãåºãããšæããŠããã ããã®ã§ã¯ãªãã§ããããã ãŸãæ©äŒããããŸãããä»ã®ç« ãã玹ä»ã§ããããšæããŸãã
[[[Amazonãžã®ãªã³ã¯]]]( https://amzn.asia/d/06GXK0Fd ) ãã³ã¹ã»Pã»ããããŒããµãã¿ã³ã»ã¹ã«ã€ãŽã¡ã³ã·å
±è ãVisionãã®å
容ãå¿ããªãããåå¿é²ãšããŠãŸãšããããšèããŠãããŸãããããšãŠãè¯ãæ¬ãªã®ã§å
±æããããšæããããã«ãã®äžéšã玹ä»ããããŸãã æ¥åžžã«æº¢ãããã¶ã€ã³ãããããžã¥ã¢ã«ã¯ãç§ãã¡ã«æ§ã
ãªææ
ãåŒã³èµ·ãããŸãããªãç¹å®ã®ããžã¥ã¢ã«ãç§ãã¡ã«åŒ·ãå°è±¡ãäžããã®ãããŸããã®èåŸã«ããå¿çãã©ã®ããã«ç解ããããããã®æ¬ã¯è§£ãæãããŠãããŸãã èè
ã¯ããžã¥ã¢ã«ãéããŠã¹ããŒãªãŒãèªãããã®å
·äœçãªæ¹æ³ãäŸãã°è²åœ©ã圢ã®éžæãææ
ã«ã©ã®ããã«äœçšããããæããŠãããŸããããã«ãããå°é家ã§ãªããšãæ¥ã
ã®èŠèŠçäœéšãè±ãã«è§£éã§ããããã«ãªããšæããŸãã ãVisionããèªãããšã§ãç§éã®æ¥åžžã«æ°ããªèŠç¹ãçãŸãããšæããŸãããã®ããã°ãéããŠèå³ãæãããæ¹ã¯ããã²æã«åã£ãŠã¿ãããšããå§ãããŸãã ãã¡ãã®æžç±ã¯ä»¥äžã®å
容ã§æ§æãããŠããŸãã åºæ ã¯ããã« ããžã¥ã¢ã«ã³ããã¥ã±ãŒã·ã§ã³ã®ããã»ã¹ãšã¯ ç»åã®å¿çåŠ ã©ã€ã³ ã·ã§ã€ã æ床 è² å
ã«ã¡ã© æ§å³ ãŸãšã ä»åã¯ãã®äžã§ãããžã¥ã¢ã«ã³ããã¥ã±ãŒã·ã§ã³ã®ããã»ã¹ãšã¯ããç»åã®å¿çåŠããã©ã€ã³ãã®å
容ãããã€ãŸãã§çŽ¹ä»ããŠããããšæããŸãã ããžã¥ã¢ã«ã³ããã¥ã±ãŒã·ã§ã³ã®ããã»ã¹ãšã¯ ããžã¥ã¢ã«ã³ããã¥ã±ãŒã·ã§ã³ã®ããã»ã¹ãšã¯ãç®ããå
¥ã£ããã®ãç¬æã«æ§ã
ãªææ
ãåŒãèµ·ããèªåçåŠçã ãšèè
ã¯èšã£ãŠããŸãã äŸãã°ããèæãè·¯å°ã«äŒžã³ã圱ããããã§ææã«ãã®ã®ã人ããæãããæ ç»ã®ãã¹ã¿ãŒãèŠãã ãã§ãç§éã¯ãã®æ ç»ãäžå®ãææãããŒãã«ããŠããã®ã ãšçŽæçã«èªèããŸãããã®ç¬éçãªææ
ã®åå¿ã¯èªåçã«åŒãèµ·ããããŠãããã®ãªã®ã ãšããããšã§ãã ãã®æ¬ã®ç®çã¯ãèªè
ããã®ãããªèªåçåŠçãããã»ã¹ãèŠçŽ ã«å解ãããªããããã£ãæ°æã¡ãåŒãèµ·ããããã®ããç解ã§ããåãã€ããããšã ãšè¿°ã¹ãããŠãããæ©é次ã®ç« ã§ã¯ãã®èªååŠçãå¿ççåŽé¢ãã説æããŠãããŸãã ç»åã®å¿çåŠ ç»åãèŠãŠããªã©ãã¯ã¹ãããææãæãããããã®ã¯ãªããããã®ããã»ã¹ã説æããã«ãããç»åãåãŒãå¿çåŠçåŽé¢ã®äžèŠçŽ ã«ã€ããŠèšåããŠããŸãã â é¢é£ä»ã â¡ã¡ã«ããºã â¢é¿ããšã â é¢é£ä»ã äŸãã°ãèæãè·¯å°è£ãšæã圱ãçµã¿åããããšãææãæããããšãäžè¬çã§ãããã®ããã«ãç»åãæ åã¯ç§ãã¡ã®éå»ã®èšæ¶ã«ãªã³ã¯ããŠãããè³ã¯ããããèŠããšèªåçã«ç¹å®ã®ææ
ãæ³èµ·ãããããã§ããããã¯ãé£æ³ãã®ããã»ã¹ã«äŒŒãŠããŸãã ãããã£ãŠãé©åãªããžã¥ã¢ã«èŠçŽ ãéžæãé¢é£ä»ããããšã§ãäœåã¯èŠã人ã«åŒ·çãªå°è±¡ãäžããããšãã§ããã®ã ãšãããŸãã â¡ã¡ã«ããºã èŠèŠãã¶ã€ã³ã«ãããŠãã©ã€ã³ãã·ã§ã€ããè²ãšãã£ãèŠçŽ ã®çµã¿åããã¯éèŠãªåœ¹å²ãæãããŸããäŸãã°å¯Ÿç«è²â»1ãé£ãåããã«é
眮ããããšå¯Ÿæ¯ãçããŠåºæ¿ãçã¿åºããŸãããã®æ§ã«èŠèŠèŠçŽ ãçžäºäœçšããŠæã«åºæ¿ã調åãçãããããšããããšã§ãã â¢é¿ããšã ãèšãããšããããšããé¿ããã®ã¯äŒããããšããå
容ãšãã®äŒãæ¹ãäžèŽãããšãã ããïŒåŒçš p20ïŒ äŸãã°å€§åãªäººã®æ²çãªãæ»ãèªãå Žé¢ã«ããããªã«ã©ãŒãªã³ã°ã䜿çšããå Žåããã®æ²ãã¿ã¯äŒããã¥ãããªããšãã£ãå
·åã«ãå
容ãšäŒãæ¹ãäžèŽããŠãªããã®ã¯èŠãŠãã人ã®å¿ã«é¿ããªããšããããšã§ãã ããããè²åœ©ãªã©ã®ãã¶ã€ã³èŠçŽ ãç©æ¥µçã«çµã¿åãããããšã§ããçµµãã®é
åãåäžãããšãèè
ã¯åŒ·èª¿ããŠããŸããããã«ãããããèŠçŽ ããå¶ç¶ãããããããŸãŸãã«ä»»ããã¹ãã§ã¯ãªããæå³çã«éžæããããšã«ãã£ãŠèŠã人ã®ææ
ã«èšŽããããã¹ãã ãšè¿°ã¹ãŠããŸãã ç»åã®ã¢ããã㌠ã¢ããããŒãšã¯ã解ååŠãã®ããšã§ãã 以äžã«åæããé
ç®ã䜿ã£ãŠãçµµããå解ããŠããããšã§ãèŠæ¹ããæ§ç¯ããŠããããšãå¯èœã«ãªããšããããããããžã¥ã¢ã«ã§ã¹ããŒãªãŒãèªãããã®åºæ¬ã ãšèè
ã¯è¿°ã¹ãŠããŸãããããŠãã€ã§ãèŠè¿ãããšãåºæ¥ãããã«ããŠããããšããå§ãããŠããŸãã 被åäœ æåéã被åäœã®ããšã ãã©ãŒããã: ç»åã®çžŠæšªæ¯ã åã: 瞊é·ãããã¯æšªé·ã ãã¬ãŒãã³ã°: æ§å³å
ã®é
眮ã ã©ã€ã³: ç·ç¶ã®èŠçŽ ã ã·ã§ã€ã: ãã¬ãŒã å
ã®åœ¢ç¶ã æ床ïŒããªã¥ãŒïŒ: æãããŸãã¯æãã®åºŠåãã è²: æåéãè²ã®ããšã ãã¿ãŒã³: ãã¶ã€ã³ãŸãã¯ç¹°ãè¿ãã®èŠçŽ ã ã·ã«ãšãã: ãã¶ã€ã³èŠçŽ ã®èŒªéå
ãé»ãå¡ãã€ã¶ãããã®ã ãã¯ã¹ãã£: ãã¶ã€ã³èŠçŽ ã®èŒªéã瀺ãæ
å ±ã å
: æããèŒãèŠçŽ ã 奥è¡ã: 空éã®æèŠã ãšããž: ã·ã§ã€ããéãŠãå¢çã®åŒ·åŒ±ã åã: ãã¹ãŠã®åãèŠçŽ ã ã©ã€ã³ ã©ã€ã³ã¯ãæ§å³ç·ãããã³ã³ããžã·ã§ãã«ã©ã€ã³ããšåŒã°ããèŠç·ããã©ãçµè·¯ãäœãåºããŸããåºæ¬ãããŠè»œèŠãããã¡ã§ãããå€æ§ãªåŽé¢ãæã¡æ§ã
ãªæŒåºãå¯èœã«ããåãæã€ãšèè
ã¯è¿°ã¹ãŠããŸããäžå³ã¯äž»ãªã©ã€ã³ã®äŸã®å³è§£ïŒäžéšæç²ïŒãšãªã£ãŠããŸãã ãã¬ãŒã ã®å¢çç·ã1~4 å
šãŠã«è©²åœãã©ã®æ§å³ã«ãå¿
ãååšããäžäžå·Šå³ã®æ ç·ã®ããšã§ãã 1ã»2ïŒæ§å³å
ã®äººç©ãããã®æ¹åã«å¿ããŠæ§å³ç·ã«ãªã£ãŠããŸãã 3ïŒãªããžã§ã¯ãã®å®éã®åãããã³æ瀺ãããåãããæ確ãªã©ã€ã³ã圢æããŠããŸãã 4ïŒæãå¡ããæ§å³ç·ã«ãªã£ãŠããŸãã ã©ã€ã³ã®æ¹å ã©ã€ã³ã®æ¹åãšã¯ãã¬ãŒã äžäžå·Šå³ã®æ ç·ã«å¯Ÿããã©ã€ã³ã®äœçœ®é¢ä¿ã®ããšã§ããã©ã€ã³ã®æ¹åã§ææ
ãè¡šçŸããããšãå¯èœã§ãé©åãªã¢ããŒããšçµã¿åãããããšã§è±ããªææ
ãè¡šãããšãã§ããŸãã äŸïŒ åçŽïŒéåã«æã匷ããæ°åïŒæšã建ç©ãªã©é äžé«ããã³ãããã®ïŒ æãïŒæ°Žå¹³åçŽã«å¯Ÿããã³ã³ãã©ã¹ãã«ããããã©ãããšãã«ã®ãŒããã€ãããã¯ãïŒåŽ©ãããã©ã³ã¹ãšåæïŒ æ°Žå¹³ïŒç©ãããéããïŒæ°Žå¹³ç·ãæµ·ãéããå ŽæïŒ ã©ã€ã³ã®é
眮 ã©ã€ã³ã®é
眮ã«ãã£ãŠãã¬ãŒã ãåå²ãããã·ã§ã€ããçã¿åºãããŸãããã®ã·ã§ã€ãã®ãã©ã³ã¹ã«ãã£ãŠæ§å³ã®é
åãå€åããŸãã åçåå²ãå·Šå³å¯Ÿç§°ïŒéèªç¶çã人工çã é察称ïŒãã©ã³ã¹æ¬¡ç¬¬ã§é
åçã«ãªããäžåå²ãé»éæ¯ãªã©ã ã©ã€ã³ã®è³ª ã©ã€ã³ã®è³ªãç¹åŸŽã¯ææ
ã匷ãåèµ·ããŸãã çŽç·ïŒç·åŒµæ æ²ç·ïŒãœããæ 倪ç·ïŒå匷ããé äžã 極现ç·ïŒæŽç·Žãç¹çŽ°ã 調åãšå¯Ÿæ¯ ãã¬ãŒã å
ã«ã©ã€ã³ãæããé端ã«ã調åã察æ¯ãçã¿åºãããŸããã€ãŸãã©ã€ã³å士ã®é¢ä¿ããªãºã ã調åãäžèª¿åããã©ã³ã¹ãã¢ã³ãã©ã³ã¹ãçµ±äžãªã©ãçã¿åºããšããããšã§ãã äŸãã°äžç«¯ã«æ°Žå¹³ãªã©ã€ã³ã¯èª¿åãçã¿åºããããããæãã«ããããšã«ãã£ãŠé端ã«å¯Ÿæ¯ãçããããšã«ãªããããã調åã察æ¯ãè¡ãéãããšéå±ããç
©éãã«ã€ãªããã®ã§ãã©ã³ã¹ã«ã¯æ³šæãå¿
èŠã ãšããããšã§ãã ãªãºã ã©ã€ã³ãç¹°ãè¿ãããšã«ãã£ãŠãªãºã ãçããæ§å³ã«æ°ããªåŽé¢ãå ãããŸãã äžå®ééã§èŠåçãªã©ã€ã³ïŒæŽç¶ããïŒéå±ãïŒ ã©ã³ãã ãªç¹°ãè¿ãïŒãšãã«ã®ãã·ã¥ãç·åŒµæ ããŸãšãã é©åã«é¢é£ä»ãããããã¶ã€ã³èŠçŽ ã䜿çšããããšã«ããäžæãã¡ã«ããºã ãåãèŠã人ã®å¿ã«é¿ãããžã¥ã¢ã«ã«ãªããããšãã·ã³ãã«ãªã©ã€ã³ãšããèŠçŽ ã§ãã£ãŠãææ
ãç·åŒµæãéå±ãã調åã察æ¯ãšãã£ãæŒåºãå¯èœã ãšããããšã§ãã ããã«èè
ãç¹°ãè¿ããŠããã®ã¯ãããã£ããŒã«ã«ãšãããããåçŽåããŠèãããããšããããšã§ãããããç¹°ãè¿ããã¡ã«æ§å³äœãã«å¯Ÿããç解ãæ·±ãŸããèªåãªãã«å¿çšãå©ããããšãã§ããããã«ãªãã¯ãã ããšè¿°ã¹ãŠããŸãã 以äžãåºç€ãäžéšãã玹ä»ãããšãã圢ã§æžãããŠããã ããŸãããã玹ä»ããéšåã ãã§ãããžã¥ã¢ã«ã®åæã«ã€ããŠèŠéãåºãããšæããŠããã ããã®ã§ã¯ãªãã§ããããã ãŸãæ©äŒããããŸãããä»ã®ç« ãã玹ä»ã§ããããšæããŸãã
ã¯ããã« ããã«ã¡ã¯ïŒiOSãšã³ãžãã¢ã®Viacheslav Voronaã§ããããŒã ã¡ã³ããŒãšäžç·ã«ä»å¹Žéå¬ã®try! Swift Tokyoã«åå ããããšã§ãSwiftã³ãã¥ããã£å
šäœã®ååã«ã€ããŠèããããšãã§ããŸãããããªãæ°ãããã®ãããã°ãåã
ãããã£ãããã©æè¿ã«ãªã£ãŠé²åãããã®ããããæ¬èšäºã§ã¯ç§ã®ææãçããã«ãäŒãããŸãã èŠãŠèŠã¬ãµãã¯ã§ããªã話é¡... ãŸãã¯é¿ããŠéããªããã®è©±é¡ãããåŸ
æã®Apple Vision Proãçºå£²ãããã®ã¯ãtry! Swiftéå¬ã®ããã2ãµæåã§ãããtry! Swiftã®äŒå ŽãAppleãã¡ã³ã§æº¢ããŠããã®ã«ãçŽåŸãããŸããApple Vision ProããŸã è©Šçããããšã®ç¡ã人ãã¡ã¯ããæ°åã ãã§ãè£
çããŠã¿ããïŒããšããã®ãã£ã³ã¹ãåæããŠããŸããã Satoshi Hattoriæ°ã«ãããSwiftã§visionOSã®ã¢ããªãã€ããããã®äŒå Žã¯æºåžã§ãããã¢ããªèªäœã¯ããŠãŒã¶ãŒã®ä»®æ³ç©ºéã« å圢ã®ã¿ã€ã㌠ãæµ®ãã¹ãã ãã®ã·ã³ãã«ãªãã®ã§ããããæéšãããå®éã«ãããã»ãããè£
çãããªã¢ã«ã¿ã€ã ã§ã¯ãŒã¯ã®çµæãèŠãå§ãããšãäŒå Žã¯å€§ããçãäžãããŸããã ãŸããæ¬ã«ã³ãã¡ã¬ã³ã¹ã®2æ¥ç®ã«ã¯ç©ºéã³ã³ãã¥ãŒãã£ã³ã°ã®ãã¡ã³ãã¡ãå°ããªéå
¬åŒããŒãã£ã³ã°ãéããŠããŸãããAppleã®ä»ã®ããã€ã¹ãšã¯ç°ãªããVision Proã¯Swiftã³ãã¥ããã£å
ã§ãç¬èªã®ãµãã³ãã¥ããã£ã圢æããŠããŸããæ ç»ã§è¿æªæ¥çãªä»®æ³ããã€ã¹ãèŠãŠè²ã£ã人ãã¡ã¯ããµã€ããŒãã³ã¯ã®å€¢ã«è¿ã¥ããŠããããšãå®æãå§ããŠããã®ã§ãããšããµã€ãã£ã³ã°ã§ããåé¢ã人ã«ãã£ãŠã¯è
åšã«æãããããããŸããã ãããŠãã¡ãããã«ã³ãã¡ã¬ã³ã¹ã®ãªãŒããã³ã°ã§ã®ãSwift Punkãã®ããã©ãŒãã³ã¹ãVision Proã«ã€ã³ã¹ãã€ã¢ããããã®ã ãšããããšã¯å¿ããã«è§ŠããŠãããŸãã $10000+ã®å°éå
·ã§è¡ããããªãŒããã³ã°ããã©ãŒãã³ã¹ Swiftã®æ°å¢å° æå
端ã®ãã¬ã³ãã§ã¯ãªããŠããæè¿ã¯å€æ¹é¢ã«ãããŠèå³æ·±ãéçºãé²ããããŠããŸããã€ãŸããSwiftã³ãã¥ããã£ããAppleããã€ã¹ã®é åãè¶
ããŠããã«æ¡å€§ããããšããŠãããšããããšã§ãã ãµãŒããŒãµã€ãSwiftãªã©ã¯ä»¥åããååšããŠããŸãã Vapor ã¯2016幎ã«ãªãªãŒã¹ãããåºãæ¡çšãããããã§ã¯ãªãã§ãããä»ã皌åãç¶ããŠããŸããVapor Core Teamã® Tim Condon æ°ã«ãããtry! Swiftã§å€§èŠæš¡ãªã³ãŒãããŒã¹ã®ç§»è¡ã«ã€ããŠå€§å€èå³æ·±ããã¬ãŒã³ãèãããšãã§ããŸãããããã¯Vaporãversion5.0ã§Swift Concurrencyãå®å
šã«ãµããŒãããããã«çŸåšé²ããŠãã移è¡ã«å€§ãã圱é¿ãããŠããŸããTimæ°ã«ãããšããã®ããŒãžã§ã³ã¯2024幎å€ã«ãªãªãŒã¹ãããäºå®ãªã®ã§ããµãŒããŒãµã€ãSwiftãè©ŠããŠã¿ããæ¹ã«ãšã£ãŠã¯å§ããã®ã«çµ¶å¥œã®ã¿ã€ãã³ã°ãããããŸããã Vaporã®ä»æã人ãTim Condonæ°ãã·ã£ããè¯ãæãïŒ Swiftã§æžãããAPIã«åãããŠãåãSwiftèšèªã䜿ã£ãŠWebããŒãžãå®è£
ããŠã¿ãããšãã§ããŸãããã㯠Paul Hudson æ°ã®ããŒã¯ããŒãã§ãããSwiftãªã¶ã«ããã«ããŒãå©çšããHTMLçæã«é¢ããPaulæ°ã®è¬æŒã¯ãçµéšè±ããªåœŒã ããããã§ãããã®ã§ããšãŠããããããã£ãã§ããã¹ããŒãã®ã¯ã©ã€ããã¯ã¹ã¯ã圌ãã¹ããŒãã§è©±ããŠããã®ãšãŸã£ããåãåçã䜿ã£ãæ°ãããµã€ããã«ããŒã Ignite ã®çºè¡šã§ããã Paul Hudsonæ°ïŒ Igniteãå«ãå€ãã®ãã®ãè£ã§æ¯ããŠããä»æã人 ãã®ã«ããŽãªãŒã§ããäžã€å°è±¡çã ã£ãã®ã¯ãã¯ãã¹ãã©ãããã©ãŒã Swiftããããªãæãã Saleem Abdulrasool æ°ã«ãããã®ã§ãWindowsãšmacOSã®éããšé¡äŒŒç¹ããããŠSwiftéçºè
ãWindowsã¢ããªã±ãŒã·ã§ã³ãäœãããšããéã«çŽé¢ãã課é¡ã«ã€ããŠè©±ããŠãããŸããã æåŸã«å¿ããŠã¯ãããªãã®ãã Yuta Saito æ°ã«ããSwiftã®ãã€ããªåæžã¹ãã©ããžãŒã«ã€ããŠã§ããäžèŠãç§ãæ¬èšäºã§æžããŠãããã¬ã³ããšã¯é¢ä¿ç¡ãããã«èŠããŸãããéœè€ããã Playdate ãšããå°ããªã²ãŒã æ©ã«ãããã€ãããã·ã³ãã«ãªSwiftã¢ããªãèŠãããšãã«ãç¡é¢ä¿ã§ã¯ãªãããšã«æ°ã¥ããŸãããæåçã§ããã SwiftãAppleã®ãã©ãããã©ãŒã ã§æ°ããæ©èœãåŸãã ãã§ãªããæ°ããé åã絶ããæ¢æ±ããŠããã®ã¯åã°ããããšã§ãã "ã¶ã»ã³ã³ãã¥ãŒã¿ãŒ (ãã©ãã€ã¢)" æåŸã«ãããæ°å¹Žãã¡ãã¡ã§è©±é¡ãšãªããæ°ããããªã«ããã匷åãªãã¢ãã«ã次ã
ãšåºãŠããAIãLLMãªã©ã®ãããã¯ã«ã€ããŠã話ããŸããããžã¿ã«ã»ãŽãŒã«ãã©ãã·ã¥ã®æšä»ããœãããŠã§ã¢äŒæ¥ã¯AIåŠçããããšãããããã®ã«é©çšããããšããŠããŸãããã¡ãããSwiftã³ãã¥ããã£ããã®åœ±é¿ãåããã«ã¯ããããŸãããtry! Swiftã§ãããã®åŸåãéæã«èŠãããŸããã ã«ã³ãã¡ã¬ã³ã¹ã§æåã«è¡ããããã¬ãŒã³ã®äžã€ã¯ãDuolingoã®ãšã³ãžãã¢ã§ãã Xingyu Wang æ°ã«ãããã®ã§ãããOpenAIãšå
±åã§å°å
¥ããããŒã«ãã¬ã€æ©èœã«ã€ããŠãAIãæèŒããããã¯ãšã³ãã®æŽ»çšãAIçæã«ãããæéãæé©åããããã®ææŠããããŠããã軜æžããããã«Xingyuæ°ã®ããŒã ãé©çšãããœãªã¥ãŒã·ã§ã³ã«ã€ããŠèªãããŸãããå
šäœçã«ååãã§ãAIãç§ããç¡éã®å¯èœæ§ãæããã€ã¡ãŒãžã§æãããŠããã®ãèŠããŠããŸãã äžæ¹ã§ãã«ã³ãã¡ã¬ã³ã¹ã®åã«ç§ã泚ç®ããã®ã¯ã Emad Ghorbaninia æ°ã«ãã "AIããªãæªæ¥ãèãã / What Can We Do Without AI in the Future?"ã®ã»ãã·ã§ã³ã§ããã©ããªå
容ãªã®ãããšãŠãèå³ãæã£ãŠããŸãããå®éã«èŽè¬ããŠãAIã®ãããªãçºå±ã«äŒŽããéçºè
ãšããŠããããŠäººéãšããŠãç§ãã¡ãä»åŸçŽé¢ããã§ããã課é¡ã«ã€ããŠæ·±ãèããããããŸãããEmadæ°ã®èãã«ãããšäººå·¥ç¥èœã«å¯Ÿæããããã«ã¯ã人éãæããã®åŒ·ã¿ãåºããåµé çãªããã»ã¹ã«çŠç¹ãåœãŠãã¹ãããšã®ããšã§ãããåè«ã§ããŸããã ãããã« try! Swift Tokyoã§ã®ãã£ã¹ã«ãã·ã§ã³ããµãè¿ããSwiftã³ãã¥ããã£ã®é²åãææ°ã®æè¡ååã«é©å¿ããŠãã£ãŠããæ§åã¯éåžžã«èå³æ·±ãã§ããApple Vision Proã®ãããªé©æ°çãªããŒããŠã§ã¢ãåãå
¥ããããšããããµãŒããŒãµã€ãSwiftãAIã®çµ±åãšãã£ãæ°ããªé åã®éæãŸã§ãä»åèŠããé²å±ã¯æè¡ã®ååã«åºãææã«å¯Ÿå¿ããã³ãã¥ããã£ã®å§¿å¢ãæµ®ã圫ãã«ããŠããŸãããã®å¥œå¥å¿ãšã€ãããŒã·ã§ã³ãžã®æ
ç±ããSwiftãiOSéçºã«éå®ãããèšèªã§ã¯ãªãããœãããŠã§ã¢ã®å¯èœæ§ãåºããããã®åŒ·åãªããŒã«ã»ããã«ããŠããŸããä»åŸããéçºè
ã®åµé æ§ãšæè¡ã®ãã€ãããã¯ãªçžäºäœçšã¯Swiftã³ãã¥ããã£å
ã§ããã«ãšããµã€ãã£ã³ã°ãªé²æ©ãããããããšãæåŸ
ãããŸãããã®æŽ»æ°ã«æºã¡ããšã³ã·ã¹ãã ã®äžå¡ãšãªããããšã¯éåžžã«æ¥œãã¿ã§ãïŒ
ã¯ããã« ããã«ã¡ã¯ïŒKINTOãã¯ãããžãŒãºã§iOSã¢ããªã±ãŒã·ã§ã³ãéçºããŠããFelixã§ããSwiftã«çŠç¹ãåœãŠãã«ã³ãã¡ã¬ã³ã¹ã«è¡ãã®ã¯åããŠã§ããã2024幎3æ22æ¥ãã24æ¥ãŸã§ãæžè°·ã§éå¬ãããtry! Swift 2024 Tokyoã«åå ããŸãããæ¥çã®ææ°ãã¬ã³ãã«è§Šããä»ã®ãšã³ãžãã¢ãšã®ãããã¯ãŒã¯ãåºãã絶奜ã®æ©äŒãšãªããŸããã ãã¬ãŒã³ ãããããªèª¬åŸåã®ãããã¬ãŒã³ã®äžã§ãç¹ã«å°è±¡ã«æ®ã£ããã®ã2ã€æããããŠãã ããã ãŸããDuolingoã®AIãã¥ãŒã¿ãŒæ©èœã«ã€ããŠã®ãã¬ãŒã³ã§ããè¬æŒè
ã®Xingyu Wangããã¯ãAIãã¥ãŒã¿ãŒæ©èœã®å®è£
ã«é¢ããŠè¬æŒãããŸããããŸãããã£ããã€ã³ã¿ãŒãã§ã€ã¹ã®æ§ç¯ããæçãªãã¬ãŒãºã®ã¬ã€ãã³ã·ãŒã®æé©åãšãã£ã課é¡ã«è§ŠããGPT-4ã®æ©èœã掻çšãã解決çã玹ä»ããŸãããããã³ããšã³ãã ãã§ãªããçŸåšçŽé¢ããŠãã課é¡ã«ãèšåããªããããœãããŠã§ã¢å
šäœã®ã¢ãŒããã¯ãã£ãŒã«ã€ããŠã話ãããã ããŠéåžžã«è¯ãã£ãã§ããå人çãªè©±ã§ããã以åç§ã¯ãæ¥æ¬äººãŠãŒã¶ãŒåãã®è±èªåŠç¿ã¢ããªãéçºããããšãããåããããªç®æšãæã£ãŠããŸããããã®ç¥èã¯ãåããããªãµãŒãã¹ãäœãäžã§éåžžã«æçšã§ããããã§ããããŒã«ãã¬ã€æ©èœãçµã¿èŸŒãããšã§ãåŠç¿è
ãå®ç掻ã«è¿ãç°å¢ã§äŒè©±ã¹ãã«ãç·Žç¿ããããšãã§ããããã«ãªããŸãã ããäžã€ã玹ä»ãããã®ã¯ããã¬ãŒã ã¯ãŒã¯ã®ã³ãã¥ããã£ã§æåãªPoint-Freeã«ãããã®ã§ããSwiftã®version 5.9ã§å°å
¥ãããSwiftãã¯ããã¹ãã«é¢ããçºè¡šãç¹ã«å°è±¡çã§ãããã³ã³ãã€ã©ãã©ã°ã€ã³ã§ãããã¯ãã¯ãæ°ããã³ãŒãã蚺æãä¿®æ£ãçæããããšã§ãSwiftã®ã³ãŒãã匷åããŸãããã¬ãŒã³ã¿ãŒã®ãäºäººã¯ãSwiftã®åŸ®çŽ°ãªãã¥ã¢ã³ã¹ã匷調ãããããã®ãã¯ããäœæããããšããã¹ãããããšã®è€éãã玹ä»ãã ãããŸããããŸãã圌ãã®ãã¹ãã©ã€ãã©ãªã§ããswift-macro-testingãããã¯ãã®ãã¹ãããã»ã¹ãããç°¡çŽ åããå¹ççãã€å¹æçã«ããããšã§ãAppleã®ããŒã«ãåäžãããæ¹æ³ã«ã€ããŠã瀺ããŠãã ãããŸããããã¬ãŒã³ã¿ãŒã®æ¹ã
ãSwiftãæ·±ãç解ããäžã§éçºã¯ãŒã¯ãããŒã®æ¹åã«åããŠé©æ°çãªã¢ãããŒããåã£ãŠããããããããŸããã ããŒã¹ ããŒã¹ãšãªã¢ã¯ãäŒæ¥ãšäº€æµããããããã«ãã£ãéããåå è
ã§ã«ããã£ãŠããŸããããµã€ããŒãšãŒãžã§ã³ãã®ããŒã¹ã¯ç¹ã«é
åçã§ãåå è
ããã¹ãã€ããã«ã³ãŒãã®èŠçŽãæžã蟌ãããã¯ã€ãããŒããèšçœ®ãããŠããŸããããã®ã€ã³ã¿ã©ã¯ãã£ããªããŒã¹äŒç»ã¯ãç¥èãæ·±ããã®ã«åœ¹ç«ã£ãã®ãšåæã«ãSwiftãžã®é¢å¿ãããã«é«ããã®ã«å¹æçã ãšæããŸããã ä»åã®ã«ã³ãã¡ã¬ã³ã¹ã§ã¯ãéåžžã®è³ªçå¿çã§ã¯ãªãããã¬ãŒã³ã®ããšã«è³ªåããã人ã¯æå®ãããããŒã¹ã§ç»å£è
ãšçŽæ¥äŒã£ãŠè©±ãããšãã§ããããšããæ°ããã¹ã¿ã€ã«ãæ¡ãããŠããŸããããããããåå è
ããã質åãããããªããç»å£è
ãšã®äº€æµãã§ãããããããè¯ãã³ãã¥ãã±ãŒã·ã§ã³ããããã¯ãŒãã³ã°ã®æ©äŒã«ãªã£ããšæããŸãã ã¯ãŒã¯ã·ã§ãã ã«ã³ãã¡ã¬ã³ã¹æçµæ¥ã«ã¯ã奜ããªã¯ãŒã¯ã·ã§ãããéžãã§åå ããããšãã§ããŸãããç§ã¯TCAã«é¢ããã¯ãŒã¯ã·ã§ãããéžã³ãçŽ200人ãå容ãã倧ããªéšå±ã®åŸãã®æ¹ã«åº§ããŸããããã®ã¯ãŒã¯ã·ã§ããã§ã¯ãäž»ã«ã³ã³ããŒã¶ãã«ã»ã¢ãŒããã¯ãã£ãŒã䜿çšããŠãµã³ãã«ã®ãSyncUpãã¢ããªãéçºããæ¹æ³ã«ã€ããŠè§£èª¬ãããŠããŸãããç§ãæåã¯äžç·ã«ã³ãŒãã£ã³ã°ããããšããŸããããæçµçã«ã¯èŠåŠããããšã«ããŸãããèå³æ·±ãç¹ã¯ããã®ãã¬ãŒã ã¯ãŒã¯ãå¯äœçšã管çããããã®æ§é åãããã¢ãããŒããæäŸããŠããããšã§ããã¢ããªã®å€éšãšçžäºäœçšããéšåããã¹ãå¯èœã§ãç解ãããããã®ãšãªã£ãŠããŸãããŠããããã¹ãã®ããã»ã¹ã¯ç¹ã«å¹ççã§æ確ã«èŠããŸããã ãããã« ä»ååããŠtry! Swift Tokyoã«åå ããŠãéåžžã«å
å®ããè¯ãçµéšãšãªããŸããããã®ã«ã³ãã¡ã¬ã³ã¹ã¯æ¥çã®ãªãŒããŒã仲éãšã€ãªããããã®ãã©ãããã©ãŒã ãšãªã£ãŠãããç§ã¯æå
端ã®Swiftæè¡ã«å€¢äžã«ãªããŸããããã¬ãŒã³ã¯ææ矩ã§ãiOSéçºã«ãããçŸå®äžçã®èª²é¡ãšåµé çãªãœãªã¥ãŒã·ã§ã³ã«ã€ããŠæ·±ãæãäžããå
容ãæäŸãããŠããå°è±¡ã§ãããã€ã³ã¿ã©ã¯ãã£ããªããŒã¹äŒç»ãå°éåéã«ç¹åããã¯ãŒã¯ã·ã§ããã¯ãéåžžã«è¯ãåŠç¿ããããã¯ãŒãã³ã°ã®æ©äŒãšãªãããã®ã«ã³ãã¡ã¬ã³ã¹ã®å€§ããªäŸ¡å€ãšãªã£ãŠããŸãããæåŸãŸã§èªãã§ãã ãããããããšãããããŸããïŒãã®èšäºãèªãã§ãèå³ãæãããæ¹ã¯ãã²æ¥å¹Žã®try! Swiftã«ãã²ãåå ãã ããïŒ
Introduction Hello, Tech Blog readers. We have recently decided to implement Marketing Cloud and to use the " Norikae GO email delivery" in it, considering the creation of a Journey to trigger an automated process instead of sending individual emails. A Journey is a feature that automatically deploys multiple marketing strategies when a customer takes a specific action. For example, when a customer clicks on a specific link in an email, the relevant information is automatically delivered as part of an automated marketing process. Unfortunately, we were having troubles finding a way to add Journey Builder as an activity in Automation Studio. So, I have summarized in this article the results of the various trials we did. Email Delivery Partner There are several reasons for using Journey Builder: ã»Can leverage branching, randomness, and engagement ã»Can be integrated with Salesforce, for example, when creating tasks and cases, updating objects, etc. However, Journey Builder does not allow you to execute scripts or SQL queries. For example, you need to merge synced data sources before sending a large volume of emails. In such cases, Journey Builder must be called after these activities are completed in Automation Studio. Therefore, it is desirable to integrate Automation Studio with Journey Builder to send emails. Let's see how to set this up together. Settings Create an Automation, and add the Schedule as the starting source. Configure the Schedule to the future time and save it. Remember to save it, otherwise later settings will not work. Add your desired activity, such as SQL queries and filters. This is essential for integrating with Journey. Journey cannot be triggered if no data extension is selected. Create a Journey. Add a data extension as the entry source. Select the data extension used in Step 2. This is important. If you choose a different data extension, you will not be able to integrate with Automation in Step 1. Note: At this point, even if you save the journey and return to Automation, you will not be able to select the journey from the activities. This is because there is no "Journey" option for Automation activities. But, wait a moment. Now, I'm going to show you some magic!  In Journey, click "Schedule" at the bottom of the canvas, select "Automation" as the schedule type, and then click "Select." Can't choose "Automation" because it is inactive? Why don't you go back to Step 1 and save Automation? In "Schedule Summary," click "Schedule Settings" and select the Automation you created in Step 1. Edit a contact's rating to specify the records to be processed by Journey. Add email, and flow control, etc. Your setup is now complete! Letâs validate and activate the journey. Don't worry, emails will not be sent immediately after activation, as the timing of the transmission depends on Automation. Back to the Automation, now the Journey was added to Automation on its own, right? Don't you think it's amazing? Finally, summon the courage to activate your Automation. See, every time Automation is triggered, Journey will also be triggered! Thank you for reading. Here, I am going to take a break with a cup of coffee. I hope you will all refresh yourselves with your favorite drink and enjoy the automatic email delivery. Happy marketing! Source: https://www.softwebsolutions.com/resources/salesforce-integration-with-marketing-automation.html
Introduction Hello everyone! I am Kin-chan from the KINTO Technologies' Development Support Division. I usually work as a corporate engineer, maintaining and managing IT systems used throughout the company. The other day, I presented the "Study session in the format of case presentations + roundtable discussions, specialized in the corporate IT domain" at the event " KINTO Technologies MeetUp!" 4 case studies for information systems shared by information systems - " In this article, I will introduce the content of the case study presented at that study session, along with supplementary information. The Presentation You can check below for the full presentation material (in Japanese): [An Introduction to AGILE SaaS] The Secrets to Achieving Maximum Results Quickly with Minimum Workload In addition to the slides I used in my presentation, I will provide additional information to clarify any difficult parts and cover topics I couldn't address at the event. Title Selection First of all, I'd like you to examine the title. Many people interpret "Agile" in different ways, making it daunting to include in the title of a presentation. However, I chose to have it anyway because I hope that someone who listened to or saw my presentation might gain insights like "Oh, so this can also be considered Agile" or "It's not such a difficult topic," and inspire them to take new actions. (Of course, the fact that it's an "attractive" keyword was also a factor in my decision.) What I Will vs. Will Not Speak About Today Since I used the keyword "Agile" in the title, I thought it would be good to focus on content that can be linked to the value of Agile software development. If you're interested in hearing more detailed information about processes or the small stories that occurred during projects, please consider joining KINTO Technologies. Background The introduction of IT Service Management (ITSM) tools, which include inquiry and request management, began with the IT team. Due to its relatively smooth implementation, there was a basis for extending it to management departments beyond IT. Before this flow was established, there wasnât many opportunities to interact with "other managing departments beyond IT" within the company. Personally, I had previous project experiences with many non-IT departments, including before my previous job. So, when I was appointed to drive this project, I felt glad because I thought I could leverage my past experiences. The decision to opt for an Agile approach stemmed from the background of having a rough goal in mind but not having concrete set of requirements or functions established, and wanting to achieve success with minimal workload while still creating value. Instead of a rigidly defined phased implementation (as one would do in a Waterfall model), the Agile approach, which involves iterating through dialogue and course corrections while building minimal viable products, seemed more suitable. I have this slide here that says, "I think it's better to go Agile!" It might seem like we had already decided on Agile from the project's inception, but in reality, it was more like, "Hmm, how should we move forward? Let's start by listening to what the stakeholders have to say." It was after conducting hearings with the Administration Department team members that we gained a sense of, "With them, we could proceed with this style!" which led us to adopt the Agile approach mentioned later. About Agile When someone asks me "What is Agile?" within the company, I typically respond with something like, "It's a state where work progresses by focusing on value while iterating Kaizen (continuous improvement) in short cycles." While those familiar with software development may understand the values and principles outlined in the Agile Manifesto, others might not resonate with it. Lately, I've noticed that explaining Agile has become easier with the publication of books like 'The Agile Kata' and other Agile books targeting non-IT audiences. As for the progress of the project... For the next slides, I made a conscious effort to explain "What makes it Agile?" in a way that links back to the values outlined in the Agile Manifesto as much as possible. The message I wanted to convey with this slide is the establishment of mechanisms to minimize unnecessary communication and facilitate immediate engagement in essential conversations. In typical software development scenarios, one common question might be, "What tasks are currently being performed?" and for clarifying "What do we want to accomplish?" . Given that this is a "SaaS implementation with a certain degree of framework already established," I deemed it more appropriate to explore "effective usage based on the existing framework" rather than "defining requirements based solely on current tasks." Furthermore, one of the strengths of low-code tools is their significantly lower cost for the build-break-fix process in the initial stages. This made it feasible to create a prototype providing minimal value before the first meeting. As a result, instead of starting the conversation with "So, what kind of product do you want to create?" during the initial meeting, we were able to begin with discussions focused on specific functional prototypes, asking questions like "How about a system that works like this? Do you notice any issues with it?" This allowed us to engage in discussions centered around tangible, functional examples right from the start. These aspects focus on the following values in the Manifesto for Agile Software Development: Individuals and interactions over processes and tools Working software over comprehensive documentation What I wanted to convey in this slide is âto create value at short intervals, get feedback, and create a mechanism to provide a system that makes senseâ. One common aspect in meetings is taking points as homework for internal discussion later. For example, "consider what kind of menu structure is good" or "discuss internally what kind of process flow is best". But this time, rather than leaving such "takeaway considerations" entirely to the other party, we opted to participate in these discussions by being invited as guests to their alignment sessions. By doing so, we can immediately address any questions, concerns, or discrepancies that arise during the conversation, and we can swiftly provide answers or even start making system adjustments on the spot. As a result, despite being in a "separate discussion" setting, we were able to progress not only with specification changes based on the discussions but also with actual functional improvements. Furthermore, I mentioned here that "significant specification changes emerged at this point," but what I meant was that we were able to detect a situation where it was more beneficial to essentially "start over" rather than modify what has been done so far. Of course, this meant discarding what has been built till that point. However, by actively participating in the discussions, we were able to fully understand the necessity and value of rebuilding. This allowed us to make this decision with confidence. These aspects focus on the following values in the Manifesto for Agile Software Development: Customer collaboration over contract negotiation Responding to change over following a plan Finishing the project Through this project, one of the most significant gains I feel I've obtained is "trust." It's just my unilateral opinion, but I feel that I've contributed to creating opportunities where people think, "Working with this person leads to good results," and "I'd like to consult with them again if there's something next time." Certainly, I believe there are many approaches to project management that can yield positive results, not just those aligned with Agile practices like the example we discussed. But If you ever find yourself stuck on how to proceed, I recommend considering the values inherent in Agile as a reference and trying to adjust your actions just a little: Envision your desired outcomes and apply small changes to achieve them. Observe the results of those small changes in behavior and use that feedback to further refine your vision of the desired outcome. Continue to make further small changes in your behavior. Once you're able to repeat this process, it's safe to say you've adopted an 'Agile' mindset. Conclusion As mentioned at the beginning, I hope to inspire anyone who has gone through this material to gain insights such as "Oh, this is also Agile" or "It's not such a difficult topic". I would be happy if this can serve as encouragement for your next actions.
Introduction Greetings, this is Morino from KINTO Technologies. On June 29th (Thursday) to the 30th (Friday) in 2023, I attended with a colleague the Cyber Security Symposium Dogo 2023 held in Matsuyama City, Ehime Prefecture. The purpose of the event is to recognize the importance of countermeasures against cyberattacks as digitalization accelerates with the development of society that coexists with the coronavirus, and to fight cyberattacks with the power of local security. The purpose of the seminar was to deepen discussions on policy trends, technological trends, and examples of cyber attacks. We were able to get a lot of inspiration and knowledge from the lectures and other participants. When I arrived at Matsuyama Airport, we were greeted by Mican, a mascot promoting the image of Ehime Prefecture. There was also a mikan (mandarin orange) juice tower and a mikan juice faucet. There were many interesting talks and presentations at the symposium, but I would like to introduce some of the ones that left an impression on me. (See a full list of talks and presentations here .) Japan's Cybersecurity Policy First of all, Mr. Tomoo Yamauchi (Director-General, Cybersecurity Office, Ministry of Internal Affairs and Communications) gave a keynote speech on "Japan's Cybersecurity Policy." Under the theme of "leaving no one behind," Mr. Yamauchi explained the country's efforts to secure a free, fair and safe cyberspace. This included changes in targets during Cybersecurity Awareness Month, and improvements in cloud usage within government agencies, etc. I felt that the theme of âleaving no one behindâ was wonderful. Security (Security + Community) and Generated AI As for the night session, I listened to a lecture on "Security (Security + Community) and Generated AI" by Mr. Tsuneyoshi Hamamoto (IT Integration Department, Energia Communications, Inc.) and Mr. Matcha Daifuku (Risk Consulting Department, luck Technology, Inc.). Mr. Hamamoto explained the concept of secuminity , a term coined by combining security with community. Secuminity is where people concerned with security interact, share knowledge and experiences, as well as collaborate and learn from each other online and offline. I understood it to be a community that contributes to improving security. Next, he shared his knowledge on Generative AI. The presentation materials are available here (in Japanese). From a security perspective, while we had expectations for its use in detecting suspicious activity from logs, we were also concerned about its use in generating sophisticated phishing emails. Student Research Award Winning Research Presentation Finally, on the second day, outstanding students presented their research findings at the Student Research Award Presentation. I voted for the presentation titled "Proposal of KP-less Method for Individual Cyber Exercises Based on Tabletop Role-Playing Games (TRPG)" as it was the one I found most compelling in the symposium, whereas participants voted for the best presentation. This presentation was made by Ms. Erika Fujimoto (Graduate School of Regional Design and Development, University of Nagasaki), who proposed an exercise method for individuals based on TRPG (Tabletop Role-Playing Games) in âKP-lessâ style as a cyber exercise scenario. âKP-lessâ means that there is no one in the TRPG to take on the role of the Game Master, the organizer. I was drawn to it due to my ongoing interest in information security education as a security officer. When I was in elementary school and junior high school, game books became very popular. So I understood that it was an exercise incorporating that method. Summary These were some of the talks and presentations at the Cybersecurity Symposium Dogo 2023. There were many other useful lectures and presentations. The symposium was a valuable opportunity not only to learn about the latest insights on cybersecurity, but also to interact with people who are interested in the same field. I want to thank the organizers, sponsors, and attendees.
Introduction Hello! Thank you for reading! My name is Nakamoto and I develop the front end of KINTO FACTORY ('FACTORY' in this article), a service that allows you to upgrade your current car. In this article, I would like to introduce a method of how to detect errors that occur in clients such as browsers using AWS CloudWatch RUM. Getting Started The reason why we introduced it was due to an enquiry we received by our Customer Center (CC), where a user tried to order products from the FACTORY website, only to encounter an error where the screen did not transition. This prompted an investigation request. I immediately parsed the API log and checked if there were any errors, but I could not find anything that would lead to an error. Next, I checked what kind of model and browser was being used to access the front end. When examining the access logs from Cloud Front, I looked into the access of the relevant user and checked the User-Agent where I could see: Android 10; Chrome/80.0.3987.149 It was accessed from a relatively old Android device. With that in mind, while analyzing the source of the page where the problem occurred, a front end development team member advised that replaceAll in JavaScript might be the culprit... This function requires compatibility with Chrome version 85 or higher... (Since FACTORY recommends using the latest version of each browser, we hadn't tested cases with old versions such as this case in QA.) *Other members of the team also told me that you can easily search for functions here to see which browsers and versions are supported! Until now, monitoring in FACTORY has detected errors in the BFF layer and notified PagerDuty and Slack, but it has not been possible to detect errors in the client-side, so it was the first time we noticed them through communication from customers. If we continued as-is, we would not be able to notice such errors on the client side unless we received customer feedback, so we decided to take countermeasures. Detection Method Originally, FACTORY's frontend had been loading client.js from AWS's CloudWatch RUM (Real-time User Monitoring). However, this function was not being used for anything in particular (user journeys, etc. are analyzed separately with Google Analytics), so it was a bit of a waste. As I investigated, I learned that RUM allows JavaScript to send events to CloudWatch on a client such as a browser. So using this mechanism, I decided to create a system to send and detect custom events when some kind of error occurs. Notification Method The general flow of notifications are as follows: When an error is detected in the browser, CloudWatch RUM sends a custom event with the error description in the message window.crm("recordEvent", { type: "error_handle_event", data: { /* Information required for analysis. The contents of the exception error */ }, }); Cloud Watch Alerm detects the above events and sends the error details via SNS when the event occurs The above SNS notifies SQS, Lambda picks up the message and notifies the error to OpenSearch (this mechanism uses the existing API error detection and notification mechanism) After Implementation After implementing this mechanism in the production environment and operating it for several months, I can luckily say that critical issues, such as the JavaScript error that resulted in its introduction, have not occurred. However, I have been able to detect cases where errors occur due to unintended access from search engine crawlers and bots, and I have become aware of accesses that I did not pay particular attention to until I introduced it, so it became a reminder of the importance of monitoring and being vigilant. Conclusion In order to enable the best online purchase experiences on websites such as FACTORY, it's very important to prevent as many errors as possible (such as problems when buying items, viewing pages, etc.). However, there is unfortunately a limit as to how much we can guarantee that it works on all customers' devices and browsers. That is why, if an error occurs, it is necessary to show easy to understand messages for the customers (with what they should do next), and a mechanism in place for us, the developers on the operation side, so that we can quickly identify the occurrence and details of the problem. I would like to continue using different tools and mechanisms to ensure stable website operation.
ã¯ããã« ããã«ã¡ã¯ïŒKTCã°ããŒãã«éçºéšã«æå±ããŠããåŽã§ãã çŸåš KINTO FACTORY ã®éçºã«åå ããŠãããä»å¹Žã¯ããŒã ã¡ã³ããŒãšäžç·ã«WebãµãŒãã¹å
ã®ã¡ã¢ãªãªãŒã¯ã®åå ã調æ»ããç¹å®ããåé¡ç¹ãä¿®æ£ããŠè§£æ±ºããŸããã ãã®ããã°ã§ã¯ã調æ»ã¢ãããŒãã䜿çšããããŒã«ã調æ»çµæããããŠã¡ã¢ãªãªãŒã¯ã«å¯ŸåŠããããã®æªçœ®ã«ã€ããŠè©³ãã説æããŸãã èæ¯ ç§ãã¡ãçŸåšéçºã»éçšããŠããKINTO FACTORYãµã€ãã«ã¯ãAWSã®ECSäžã§åäœããŠããWebãµãŒãã¹ããããŸãã ãã®ãµãŒãã¹ã§ã¯ãåœç€Ÿãéçºã»éå¶ããŠããèªèšŒãµãŒãã¹ã§ããäŒå¡PF(Platform)ãšæ±ºæžãµãŒãã¹ã§ãã決æžPF(Platform)ãå©çšããŠããŸãã ä»å¹Ž1æã«ããã®WebãµãŒãã¹ã§ECSã¿ã¹ã¯ã®CPU䜿çšçãç°åžžã«é«ãŸããäžæçã«ãµãŒãã¹ã«ã¢ã¯ã»ã¹ã§ããªãäºæ
ãçºçããŸããã ãã®éãKINTO FACTORYãµã€ãã§ç¹å®ã®ç»é¢é·ç§»ãæäœãè¡ããš404ãšã©ãŒããšã©ãŒãã€ã¢ãã°ã衚瀺ãããã€ã³ã·ãã³ããçºçããŸããã æšå¹Ž7æã«ãé¡äŒŒã®ã¡ã¢ãªãªãŒã¯ãçºçããŠãããFull GCïŒOldé åã®ã¯ãªã¢ïŒãé »ç¹ã«çºçããããã«äŒŽãCPU䜿çšçã®å¢å ãåå ã§ããããšãå€æããŸããã ãããã®äºè±¡ãçºçããå Žåãäžæ察çãšããŠECSã¿ã¹ã¯ã®åèµ·åã§è§£æ±ºã§ããŸãããã¡ã¢ãªãªãŒã¯ã®æ ¹æ¬åå ã究æãã解決ããå¿
èŠããããŸãã æ¬èšäºã§ã¯ããããã®äºäŸãèžãŸããçŸè±¡ã®èª¿æ»ã»åæãšããã«åºã¥ãã解決çãèšèŒããŠããŸãã 調æ»å
容ãšçµæã®èŠçŽ 調æ»å
容 æåã«ãæ¬ä»¶ã§çºçããäºè±¡ã®è©³çŽ°ãåæãããšãWebãµãŒãã¹ã®CPU䜿çšçãç°åžžã«é«ãŸãã®ã¯ãFull GCïŒOldé åã®ã¯ãªã¢ïŒãé »ç¹ã«çºçããããšã§èµ·ããåé¡ããããšãåãããŸããã éåžžãFull GCãäžåºŠè¡ããããšãå€ãã®ã¡ã¢ãªã解æŸããããã°ããã®éã¯å床çºçããããšã¯ãããŸããã ã«ãããããããFull GCãé »ç¹ã«çºçããã®ã¯ã䜿çšäžã®ã¡ã¢ãªãéå°ã«æ¶è²»ãããŠããå¯èœæ§ãé«ããããã¯ã¡ã¢ãªãªãŒã¯ãçºçããŠããããšã瀺åããŠããŸãã ãã®ä»®èª¬ãæ€èšŒããããã«ãã¡ã¢ãªãªãŒã¯ãçºçããæéäžã«å€ãåŒã°ããAPIãäžå¿ã«é·æéAPIãåŒã³åºãç¶ãã ã¡ã¢ãªãªãŒã¯ãåçŸãããŸããããã®åŸãã¡ã¢ãªã®ç¶æ³ããã³ããåæããŠåå ãæ¢ããŸãã 調æ»ã«äœ¿çšããããŒã«ã¯ä»¥äžã®éãã§ãïŒ JMeter ã§ã®APIã®ãã©ãã£ãã¯ã·ãã¥ã¬ãŒã·ã§ã³ VisualVM ãš Grafana ãçšããã¡ã¢ãªç¶æ
ã®ç£èŠïŒããŒã«ã«ç°å¢ããã³æ€èšŒç°å¢ïŒ OpenSearch ã§é »ç¹ã«åŒã³åºãããAPIã®ãã£ã«ã¿ãªã³ã° ãŸããæ¬æã«ããçŸããŠããã¡ã¢ãªã®ãOldé åãã«ã€ããŠä»¥äžã®éãã«ç°¡åã«èª¬æããŸãïŒ Javaã®ã¡ã¢ãªç®¡çã§ã¯ãããŒãé åãYoungé åãšOldé åã«åãããŠããŸãã Youngé åã«ã¯æ°ããäœæããããªããžã§ã¯ããæ ŒçŽãããããã§äžå®æéåç¶ãããªããžã§ã¯ãã¯Survivoré åãçµãŠOldé åã«ç§»åããŸãã Oldé åã«ã¯é·æéåç¶ãããªããžã§ã¯ããæ ŒçŽãããããããã£ã±ãã«ãªããšFull GCãçºçããŸãã Survivoré åã¯Youngé åå
ã®äžéšã§ããªããžã§ã¯ããã©ãã ãé·ãçåããŠãããã远跡ããŸãã 調æ»çµæ å€éšãµãŒãã¹ã®ãªã¯ãšã¹ãæã«æ¥ç¶ã€ã³ã¹ã¿ã³ã¹ã倧éã«æ°èŠäœæãããŠãããã¡ã¢ãªãç¡é§ã«å æãããŠããããšã«ããã¡ã¢ãªãªãŒã¯ãçºçããŠããŸããã 調æ»å
容ã®è©³çŽ° 1. åŒã³åºãåæ°ãå€ãã£ãAPIã®æŽãåºã æåã«ãå€ãåŒã°ããŠããåŠçãšã¡ã¢ãªäœ¿çšç¶æ³ãç¥ããããOpenSearchã§APIåŒã³åºããµããªã®ããã·ã¥ããŒããäœæããŸããã 2. æŽãåºãããAPIãããŒã«ã«ç°å¢ã§30åéåŒã³åºãç¶ããçµæãåæ 調æ»æ¹æ³ ã¡ã¢ãªãªãŒã¯ãããŒã«ã«ç°å¢ã§åçŸããããã³ããåãåå åæãè¡ãããã以äžã®èšå®ã§JMeterã䜿çšããŠAPIã30åéåŒã³åºãç¶ããŸããã JMeterã®èšå® ã¹ã¬ããæ°ïŒ100 Ramp-upæé(â»)ïŒ300ç§ ãã¹ãç°å¢ Mac OS JavaããŒãžã§ã³ïŒopenjdk 17.0.7 2023-04-18 LTS Javaèšå®ïŒ-Xms1024m -Xmx3072m â»Ramp-upæéãšã¯ïŒèšå®ããã¹ã¬ããæ°ãäœç§ä»¥å
ã«èµ·åã»å®è¡ãããã®æå®ãããç§æ°ã§ãã çµæãšä»®èª¬ ã¡ã¢ãªãªãŒã¯ã¯èµ·ããŸããã§ãããå®éã®ç°å¢ãšç°ãªãããã¡ã¢ãªãªãŒã¯ãåçŸããªãã£ããšèããŸãããå®éã®ç°å¢ã¯Dockerã§åäœããŠãããããã¢ããªã±ãŒã·ã§ã³ãDockerã³ã³ããã«å
¥ããŠå床æ€èšŒããããšã«ããŸããã 3. Dockerç°å¢ã§å床APIãåŒã³åºãç¶ããçµæãåæ 調æ»æ¹æ³ ã¡ã¢ãªãªãŒã¯ãããŒã«ã«ç°å¢ã§åçŸãããããã以äžã®èšå®ã§JMeterã䜿çšããŠAPIã1æéåŒã³åºãç¶ããŸããã JMeterã®èšå® ã¹ã¬ããæ°ïŒ100 Ramp-upæéïŒ300ç§ ãã¹ãç°å¢ ããŒã«ã«Dockerã³ã³ããïŒMacäžïŒ ã¡ã¢ãªå¶éïŒ4 GB CPUå¶éïŒ4ã³ã¢ çµæ ããŒã«ã«ç°å¢ã§ç°å¢ãå€ããŠãã¡ã¢ãªãªãŒã¯ã¯èµ·ããŸããã§ããã 仮説 å®éã®ç°å¢ãšç°ãªã å€éšAPIãåŒã³åºããŠããªã é·æéã«ãããAPIåŒã³åºãã§å°ããã€ã¡ã¢ãªãèç©ãããå¯èœæ§ããã 倧ãããããªããžã§ã¯ããSurvivorã«å
¥ãããOldé åã«å
¥ã£ãŠããŸãå¯èœæ§ããã ãã¯ãããŒã«ã«ç°å¢ã§ã¯åçŸã§ããªããããæ¬çªç°å¢ã«è¿ãæ€èšŒç°å¢ã§å床æ€èšŒããããšã«ããŸããã 4. æ€èšŒç°å¢ã§å€éšAPIé¢é£ãé·æéå©ãç¶ããçµæãåæ 調æ»æ¹æ³ ã¡ã¢ãªãªãŒã¯ãæ€èšŒç°å¢ã§åçŸãããããã以äžã®èšå®ã§JMeterã䜿çšããŠAPIãåŒã³åºãç¶ããŸããã åŒã³åºã察象APIïŒããããèš7æ¬ ç¶ç¶æéïŒ5æé ãŠãŒã¶ãŒæ°ïŒ2 ã«ãŒãïŒ200ïŒ1000ãäºå®ããŠããããå®éã®Orderã¯å°ãªããã200ã«å€æŽïŒ Factory APIåèšåŒã³åºãåæ°ïŒ4000 圱é¿ãããå€éšPFïŒäŒå¡PFïŒ1600åïŒã決æžPFïŒ200åïŒ çµæ Full GCãçºçãããã¡ã¢ãªãªãŒã¯çŸè±¡ã¯åçŸããŸããã§ããã 仮説 ã«ãŒãåæ°ãå°ãªããã¡ã¢ãªäœ¿çšéãå¢å ããŠãããäžéã«éããŠããªãããFull GCãçºåãããªãã£ããåŒã³åºãæ°ãå¢ãããã¡ã¢ãªäžéãäžããŠFull GCãçºçãããããã«ããŸãã 5. ã¡ã¢ãªäžéãäžããAPIãé·æéå©ãç¶ãã 調æ»æ¹æ³ æ€èšŒç°å¢ã§ã¡ã¢ãªäžéãäžããŠãJMeterã§äŒå¡PFé¢é£APIã4æéåŒã³åºãç¶ããŸããã æéïŒ4æé APIïŒååãšåã7ã€ã®API é »åºŠïŒ12ã«ãŒã/åïŒ5ç§/ã«ãŒãïŒ äŒå¡PFåŒã³åºãé »åºŠïŒ84å/å 4æéã®äŒå¡PFåŒã³åºãåæ°ïŒ20164å ãã³ãååŸèšå®: export APPLICATION_JAVA_DUMP_OPTIONS='-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/app/ -XX:OnOutOfMemoryError="stop-java %p;" -XX:OnError="stop-java %p;" -XX:ErrorFile=/var/log/app/hs_err_%p.log -Xlog:gc*=info:file=/var/log/app/gc_%t.log:time,uptime,level,tags:filecount=5,filesize=10m' ECSã®ã¡ã¢ãªäžéèšå®ïŒ export APPLICATION_JAVA_TOOL_OPTIONS='-Xms512m -Xmx512m -XX:MaxMetaspaceSize=256m -XX:MetaspaceSize=256m -Xss1024k -XX:MaxDirectMemorySize=32m -XX:-UseCodeCacheFlushing -XX:InitialCodeCacheSize=128m -XX:ReservedCodeCacheSize=128m --illegal-access=deny' çµæ ã¡ã¢ãªãªãŒã¯ã®åçŸã«æåãããã³ããååŸã§ããŸããã IntelliJ IDEAã§ãã³ããã¡ã€ã«ãéããšãã¡ã¢ãªã®è©³çŽ°æ
å ±ãèŠãããšãã§ããŸãã ãã³ããã¡ã€ã«ã詳ããåæãããšãããå€éšAPIé¢é£éšåã§ãªã¯ãšã¹ãããšã«å€§éã®ãªããžã§ã¯ããæ°èŠäœæãããŠããããšãUtilç³»ã¯ã©ã¹ã®äžéšãSingletonãšããŠæ±ãããŠããªãããšãå€æããŸããã 6. Heap Dumpã®åæçµæ reactor.netty.http.HttpResources å
ã« HashMap$Node ã5,410åäœæãããŠããã352,963,672ãã€ãïŒ83.09%ïŒãå°æããŠããããšãåãããŸããã ã¡ã¢ãªãªãŒã¯çºçç®æç¹å® reactor.netty.resources.PooledConnectionProvider å
ã® channelPools(ConcurrentHashMap) ã§ãªãŒã¯ãçºçããŠãããæ ŒçŽãšååŸã®ããžãã¯ã«çç®ããŸããã poolFactory(InstrumentedPool) ååŸç®æ remote(Supplier<? extends SocketAddress>) ãš config(HttpClientConfig) ããååŸãã channelHash 㧠holder(PoolKey) ãäœæ holder(PoolKey) 㧠channelPools ãã poolFactory(InstrumentedPool) ãååŸããåæ§ã®ããŒãååšããã°è¿ãããªããã°æ°èŠäœæ ãªãŒã¯ã®åå ã¯ãåäžèšå®ã§ãåäžããŒãšå€æãããªãããšã§ãïŒ reactor.netty.resources.PooledConnectionProvider public abstract class PooledConnectionProvider<T extends Connection> implements ConnectionProvider { ... @Override public final Mono<? extends Connection> acquire( TransportConfig config, ConnectionObserver connectionObserver, @Nullable Supplier<? extends SocketAddress> remote, @Nullable AddressResolverGroup<?> resolverGroup) { ... return Mono.create(sink -> { SocketAddress remoteAddress = Objects.requireNonNull(remote.get(), "Remote Address supplier returned null"); PoolKey holder = new PoolKey(remoteAddress, config.channelHash()); PoolFactory<T> poolFactory = poolFactory(remoteAddress); InstrumentedPool<T> pool = MapUtils.computeIfAbsent(channelPools, holder, poolKey -> { if (log.isDebugEnabled()) { log.debug("Creating a new [{}] client pool [{}] for [{}]", name, poolFactory, remoteAddress); } InstrumentedPool<T> newPool = createPool(config, poolFactory, remoteAddress, resolverGroup); ... return newPool; }); channelPoolsã¯å称ã®éãChannelæ
å ±ãä¿æããŠãããªããžã§ã¯ãã§åæ§ã®ãªã¯ãšã¹ããæ¥ãéã«åå©çšãè¡ã£ãŠããã PoolKeyã¯ãã¹ãåãšæ¥ç¶èšå®ã®HashCodeãå
ã«äœæãããæŽã«ãã®HashCodeã䜿çšãããã channelHash ååŸç®æ reactor.netty.http.client.HttpClientConfig ã®éå±€ Object + TransportConfig + ClientTransportConfig + HttpClientConfig PooledConnectionProviderã«æž¡ãããLambdaåŒ com.kinto_jp.factory.common.adapter.HttpSupport L5 ããã§å®çŸ©ãããLambdaåŒã PooledConnectionProvider ã« config#doOnChannelInit ãšããŠåŒãæž¡ãããã abstract class HttpSupport { ... private fun httpClient(connTimeout: Int, readTimeout: Int) = HttpClient.create() .proxyWithSystemProperties() .doOnChannelInit { _, channel, _ -> channel.config().connectTimeoutMillis = connTimeout } .responseTimeout(Duration.ofMillis(readTimeout.toLong())) ... } 7. channelPoolsååŸæã®æåïŒå³è§£ïŒ ããŒãäžèŽããã±ãŒã¹ïŒæ£åžžïŒ channelPools ã«ååšããæ
å ±ãããŒãšãªãã InstrumentedPool ãåå©çšãããã ããŒãäžäžèŽã®ã±ãŒã¹ïŒæ£åžžïŒ channelPools ã«ååšããªãæ
å ±ãããŒãšãªãã InstrumentedPool ãæ°èŠäœæãããã ä»åçºçããã±ãŒã¹ïŒç°åžžïŒ channelPools ã«ååšããæ
å ±ãããŒãšãªããã InstrumentedPool ãåå©çšãããæ°èŠäœæãããŠããŸãã åé¡ç®æã®ä¿®æ£ãšæ€èšŒ ä¿®æ£ç®æ åé¡ãšãªã£ãŠããLambdaåŒãããããã£åŒã³åºãã«æžãæãã ä¿®æ£å abstract class HttpSupport { ... private fun httpClient(connTimeout: Int, readTimeout: Int) = HttpClient.create() .proxyWithSystemProperties() .doOnChannelInit { _, channel, _ -> channel.config().connectTimeoutMillis = connTimeout } .responseTimeout(Duration.ofMillis(readTimeout.toLong())) ... } ä¿®æ£åŸ abstract class HttpSupport { ... private fun httpClient(connTimeout: Int, readTimeout: Int) = HttpClient.create() .proxyWithSystemProperties() .option(ChannelOption.CONNECT_TIMEOUT_MILLIS, connTimeout) .responseTimeout(Duration.ofMillis(readTimeout.toLong())) ... } æ€èšŒ åææ¡ä»¶ MembersHttpSupport#members(memberId: String) ã1000ååŒã³åºãã PooledConnectionProvider#channelPools ã«æ ŒçŽãããŠãããªããžã§ã¯ãã®ä»¶æ°ã確èªããã ä¿®æ£åã®çµæ ä¿®æ£åã®ç¶æ
ã§å®è¡ãããšããã PooledConnectionProvider#channelPools ã«1000åã®ãªããžã§ã¯ããæ ŒçŽãããŠããããšãåãããŸããïŒãªãŒã¯ã®åå ïŒã ä¿®æ£åŸã®çµæ ä¿®æ£åŸã®ç¶æ
ã§å®è¡ãããšããã PooledConnectionProvider#channelPools ã«1åã®ãªããžã§ã¯ããæ ŒçŽãããŠããããšãåãããŸããïŒãªãŒã¯è§£æ¶ïŒã ãŸãšã ä»åã®èª¿æ»ã§ã¯ãKINTO FACTORYã®WebãµãŒãã¹ã«ãããã¡ã¢ãªãªãŒã¯ã®åå ãç¹å®ããé©åãªä¿®æ£ãè¡ãããšã§åé¡ã解決ããããšãã§ããŸãããç¹ã«ãå€éšAPIåŒã³åºãæã«å€§éã®ãªããžã§ã¯ããæ°èŠäœæãããŠããããšãã¡ã¢ãªãªãŒã¯ã®åå ã§ãããšå€æããLambdaåŒãããããã£åŒã³åºãã«å€æŽããããšã§è§£æ¶ãããŸããã ãã®ãããžã§ã¯ããéããŠã以äžã®éèŠãªæèšãåŸãããšãã§ããŸããïŒ æç¶çãªã¢ãã¿ãªã³ã° ïŒECSãµãŒãã¹ã®CPU䜿çšçã®ç°åžžãFull GCã®é »ç¹ãªçºçãéããŠãç¶ç¶çãªã¢ãã¿ãªã³ã°ã®éèŠæ§ãèªèããŸãããã·ã¹ãã ã®ããã©ãŒãã³ã¹ãåžžã«ç£èŠããããšã§ãåé¡ã®å
åãæ©æã«å¯ç¥ããè¿
éã«å¯ŸåŠããããšãã§ããŸãã æ©æã®åé¡ç¹å®ãšå¯Ÿç ïŒWebãµãŒãã¹ã®ã¡ã¢ãªãªãŒã¯ãçããé·æéAPIãåŒã³åºããŠã¡ã¢ãªç¶æ³ãåçŸãããããšã§ãå€éšãµãŒãã¹ã®ãªã¯ãšã¹ãæã«å€§éã®ãªããžã§ã¯ããæ°èŠäœæãããŠããããšãç¹å®ããŸãããããã«ãããåé¡ã®åå ãè¿
éã«ç¹å®ããé©åãªä¿®æ£ãå®æœã§ããŸããã ããŒã ã¯ãŒã¯ã®éèŠæ§ ïŒè€éãªåé¡ã«å¯ŸåŠããéã«ã¯ãããŒã å
šå¡ãååããŠåãçµãããšãæåãžã®éµãšãªããŸããä»åã®ä¿®æ£ãšæ€èšŒã¯ãéçºããŒã å
šå¡ã®ååãšåªåã«ãã£ãŠéæãããŸãããç¹ã«ã調æ»ãåæãä¿®æ£ãæ€èšŒãšãã£ãåã¹ãããã§ã®ååãææãäžããŸããã 調æ»ãã§ãŒãºã§ã¯ãå€ãã®èŠåŽããããŸãããäŸãã°ãã¡ã¢ãªãªãŒã¯ã®åçŸãããŒã«ã«ç°å¢ã§ã¯é£ãããå®éã®ç°å¢ã«è¿ãæ€èšŒç°å¢ã§å床æ€èšŒãè¡ãå¿
èŠããããŸããããŸããå€éšAPIãé·æéã«ããã£ãŠåŒã³åºãç¶ããããšã§ãã¡ã¢ãªãªãŒã¯ãåçŸãããã®åå ãç¹å®ããã®ã«å€ãã®æéãšåŽåãèŠããŸããããããããããã®å°é£ãä¹ãè¶ããããšã§ãæçµçã«ã¯åé¡ã解決ããããšãã§ãã倧ããªéææãåŸãããšãã§ããŸããã ãã®èšäºãéããŠãã·ã¹ãã ã®ããã©ãŒãã³ã¹åäžãšå®å®æ§ãç¶æããããã®å®è·µçãªã¢ãããŒããæèšãå
±æããŸãããåæ§ã®åé¡ã«çŽé¢ããŠããéçºè
ã®æ¹ã
ã®åèã«ãªãã°å¹žãã§ãã 以äžã§ãã
ã¯ããã« ããã«ã¡ã¯ïŒKTCã°ããŒãã«éçºéšã«æå±ããŠããåŽã§ãã çŸåš KINTO FACTORY ã®éçºã«åå ããŠãããä»å¹Žã¯ããŒã ã¡ã³ããŒãšäžç·ã«WebãµãŒãã¹å
ã®ã¡ã¢ãªãªãŒã¯ã®åå ã調æ»ããç¹å®ããåé¡ç¹ãä¿®æ£ããŠè§£æ±ºããŸããã ãã®ããã°ã§ã¯ã調æ»ã¢ãããŒãã䜿çšããããŒã«ã調æ»çµæããããŠã¡ã¢ãªãªãŒã¯ã«å¯ŸåŠããããã®æªçœ®ã«ã€ããŠè©³ãã説æããŸãã èæ¯ ç§ãã¡ãçŸåšéçºã»éçšããŠããKINTO FACTORYãµã€ãã«ã¯ãAWSã®ECSäžã§åäœããŠããWebãµãŒãã¹ããããŸãã ãã®ãµãŒãã¹ã§ã¯ãåœç€Ÿãéçºã»éå¶ããŠããèªèšŒãµãŒãã¹ã§ããäŒå¡PF(Platform)ãšæ±ºæžãµãŒãã¹ã§ãã決æžPF(Platform)ãå©çšããŠããŸãã ä»å¹Ž1æã«ããã®WebãµãŒãã¹ã§ECSã¿ã¹ã¯ã®CPU䜿çšçãç°åžžã«é«ãŸããäžæçã«ãµãŒãã¹ã«ã¢ã¯ã»ã¹ã§ããªãäºæ
ãçºçããŸããã ãã®éãKINTO FACTORYãµã€ãã§ç¹å®ã®ç»é¢é·ç§»ãæäœãè¡ããš404ãšã©ãŒããšã©ãŒãã€ã¢ãã°ã衚瀺ãããã€ã³ã·ãã³ããçºçããŸããã æšå¹Ž7æã«ãé¡äŒŒã®ã¡ã¢ãªãªãŒã¯ãçºçããŠãããFull GCïŒOldé åã®ã¯ãªã¢ïŒãé »ç¹ã«çºçããããã«äŒŽãCPU䜿çšçã®å¢å ãåå ã§ããããšãå€æããŸããã ãããã®äºè±¡ãçºçããå Žåãäžæ察çãšããŠECSã¿ã¹ã¯ã®åèµ·åã§è§£æ±ºã§ããŸãããã¡ã¢ãªãªãŒã¯ã®æ ¹æ¬åå ã究æãã解決ããå¿
èŠããããŸãã æ¬èšäºã§ã¯ããããã®äºäŸãèžãŸããçŸè±¡ã®èª¿æ»ã»åæãšããã«åºã¥ãã解決çãèšèŒããŠããŸãã 調æ»å
容ãšçµæã®èŠçŽ 調æ»å
容 æåã«ãæ¬ä»¶ã§çºçããäºè±¡ã®è©³çŽ°ãåæãããšãWebãµãŒãã¹ã®CPU䜿çšçãç°åžžã«é«ãŸãã®ã¯ãFull GCïŒOldé åã®ã¯ãªã¢ïŒãé »ç¹ã«çºçããããšã§èµ·ããåé¡ããããšãåãããŸããã éåžžãFull GCãäžåºŠè¡ããããšãå€ãã®ã¡ã¢ãªã解æŸããããã°ããã®éã¯å床çºçããããšã¯ãããŸããã ã«ãããããããFull GCãé »ç¹ã«çºçããã®ã¯ã䜿çšäžã®ã¡ã¢ãªãéå°ã«æ¶è²»ãããŠããå¯èœæ§ãé«ããããã¯ã¡ã¢ãªãªãŒã¯ãçºçããŠããããšã瀺åããŠããŸãã ãã®ä»®èª¬ãæ€èšŒããããã«ãã¡ã¢ãªãªãŒã¯ãçºçããæéäžã«å€ãåŒã°ããAPIãäžå¿ã«é·æéAPIãåŒã³åºãç¶ãã ã¡ã¢ãªãªãŒã¯ãåçŸãããŸããããã®åŸãã¡ã¢ãªã®ç¶æ³ããã³ããåæããŠåå ãæ¢ããŸãã 調æ»ã«äœ¿çšããããŒã«ã¯ä»¥äžã®éãã§ãïŒ JMeter ã§ã®APIã®ãã©ãã£ãã¯ã·ãã¥ã¬ãŒã·ã§ã³ VisualVM ãš Grafana ãçšããã¡ã¢ãªç¶æ
ã®ç£èŠïŒããŒã«ã«ç°å¢ããã³æ€èšŒç°å¢ïŒ OpenSearch ã§é »ç¹ã«åŒã³åºãããAPIã®ãã£ã«ã¿ãªã³ã° ãŸããæ¬æã«ããçŸããŠããã¡ã¢ãªã®ãOldé åãã«ã€ããŠä»¥äžã®éãã«ç°¡åã«èª¬æããŸãïŒ Javaã®ã¡ã¢ãªç®¡çã§ã¯ãããŒãé åãYoungé åãšOldé åã«åãããŠããŸãã Youngé åã«ã¯æ°ããäœæããããªããžã§ã¯ããæ ŒçŽãããããã§äžå®æéåç¶ãããªããžã§ã¯ãã¯Survivoré åãçµãŠOldé åã«ç§»åããŸãã Oldé åã«ã¯é·æéåç¶ãããªããžã§ã¯ããæ ŒçŽãããããããã£ã±ãã«ãªããšFull GCãçºçããŸãã Survivoré åã¯Youngé åå
ã®äžéšã§ããªããžã§ã¯ããã©ãã ãé·ãçåããŠãããã远跡ããŸãã 調æ»çµæ å€éšãµãŒãã¹ã®ãªã¯ãšã¹ãæã«æ¥ç¶ã€ã³ã¹ã¿ã³ã¹ã倧éã«æ°èŠäœæãããŠãããã¡ã¢ãªãç¡é§ã«å æãããŠããããšã«ããã¡ã¢ãªãªãŒã¯ãçºçããŠããŸããã 調æ»å
容ã®è©³çŽ° 1. åŒã³åºãåæ°ãå€ãã£ãAPIã®æŽãåºã æåã«ãå€ãåŒã°ããŠããåŠçãšã¡ã¢ãªäœ¿çšç¶æ³ãç¥ããããOpenSearchã§APIåŒã³åºããµããªã®ããã·ã¥ããŒããäœæããŸããã 2. æŽãåºãããAPIãããŒã«ã«ç°å¢ã§30åéåŒã³åºãç¶ããçµæãåæ 調æ»æ¹æ³ ã¡ã¢ãªãªãŒã¯ãããŒã«ã«ç°å¢ã§åçŸããããã³ããåãåå åæãè¡ãããã以äžã®èšå®ã§JMeterã䜿çšããŠAPIã30åéåŒã³åºãç¶ããŸããã JMeterã®èšå® ã¹ã¬ããæ°ïŒ100 Ramp-upæé(â»)ïŒ300ç§ ãã¹ãç°å¢ Mac OS JavaããŒãžã§ã³ïŒopenjdk 17.0.7 2023-04-18 LTS Javaèšå®ïŒ-Xms1024m -Xmx3072m â»Ramp-upæéãšã¯ïŒèšå®ããã¹ã¬ããæ°ãäœç§ä»¥å
ã«èµ·åã»å®è¡ãããã®æå®ãããç§æ°ã§ãã çµæãšä»®èª¬ ã¡ã¢ãªãªãŒã¯ã¯èµ·ããŸããã§ãããå®éã®ç°å¢ãšç°ãªãããã¡ã¢ãªãªãŒã¯ãåçŸããªãã£ããšèããŸãããå®éã®ç°å¢ã¯Dockerã§åäœããŠãããããã¢ããªã±ãŒã·ã§ã³ãDockerã³ã³ããã«å
¥ããŠå床æ€èšŒããããšã«ããŸããã 3. Dockerç°å¢ã§å床APIãåŒã³åºãç¶ããçµæãåæ 調æ»æ¹æ³ ã¡ã¢ãªãªãŒã¯ãããŒã«ã«ç°å¢ã§åçŸãããããã以äžã®èšå®ã§JMeterã䜿çšããŠAPIã1æéåŒã³åºãç¶ããŸããã JMeterã®èšå® ã¹ã¬ããæ°ïŒ100 Ramp-upæéïŒ300ç§ ãã¹ãç°å¢ ããŒã«ã«Dockerã³ã³ããïŒMacäžïŒ ã¡ã¢ãªå¶éïŒ4 GB CPUå¶éïŒ4ã³ã¢ çµæ ããŒã«ã«ç°å¢ã§ç°å¢ãå€ããŠãã¡ã¢ãªãªãŒã¯ã¯èµ·ããŸããã§ããã 仮説 å®éã®ç°å¢ãšç°ãªã å€éšAPIãåŒã³åºããŠããªã é·æéã«ãããAPIåŒã³åºãã§å°ããã€ã¡ã¢ãªãèç©ãããå¯èœæ§ããã 倧ãããããªããžã§ã¯ããSurvivorã«å
¥ãããOldé åã«å
¥ã£ãŠããŸãå¯èœæ§ããã ãã¯ãããŒã«ã«ç°å¢ã§ã¯åçŸã§ããªããããæ¬çªç°å¢ã«è¿ãæ€èšŒç°å¢ã§å床æ€èšŒããããšã«ããŸããã 4. æ€èšŒç°å¢ã§å€éšAPIé¢é£ãé·æéå©ãç¶ããçµæãåæ 調æ»æ¹æ³ ã¡ã¢ãªãªãŒã¯ãæ€èšŒç°å¢ã§åçŸãããããã以äžã®èšå®ã§JMeterã䜿çšããŠAPIãåŒã³åºãç¶ããŸããã åŒã³åºã察象APIïŒããããèš7æ¬ ç¶ç¶æéïŒ5æé ãŠãŒã¶ãŒæ°ïŒ2 ã«ãŒãïŒ200ïŒ1000ãäºå®ããŠããããå®éã®Orderã¯å°ãªããã200ã«å€æŽïŒ Factory APIåèšåŒã³åºãåæ°ïŒ4000 圱é¿ãããå€éšPFïŒäŒå¡PFïŒ1600åïŒã決æžPFïŒ200åïŒ çµæ Full GCãçºçãããã¡ã¢ãªãªãŒã¯çŸè±¡ã¯åçŸããŸããã§ããã 仮説 ã«ãŒãåæ°ãå°ãªããã¡ã¢ãªäœ¿çšéãå¢å ããŠãããäžéã«éããŠããªãããFull GCãçºåãããªãã£ããåŒã³åºãæ°ãå¢ãããã¡ã¢ãªäžéãäžããŠFull GCãçºçãããããã«ããŸãã 5. ã¡ã¢ãªäžéãäžããAPIãé·æéå©ãç¶ãã 調æ»æ¹æ³ æ€èšŒç°å¢ã§ã¡ã¢ãªäžéãäžããŠãJMeterã§äŒå¡PFé¢é£APIã4æéåŒã³åºãç¶ããŸããã æéïŒ4æé APIïŒååãšåã7ã€ã®API é »åºŠïŒ12ã«ãŒã/åïŒ5ç§/ã«ãŒãïŒ äŒå¡PFåŒã³åºãé »åºŠïŒ84å/å 4æéã®äŒå¡PFåŒã³åºãåæ°ïŒ20164å ãã³ãååŸèšå®: export APPLICATION_JAVA_DUMP_OPTIONS='-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/app/ -XX:OnOutOfMemoryError="stop-java %p;" -XX:OnError="stop-java %p;" -XX:ErrorFile=/var/log/app/hs_err_%p.log -Xlog:gc*=info:file=/var/log/app/gc_%t.log:time,uptime,level,tags:filecount=5,filesize=10m' ECSã®ã¡ã¢ãªäžéèšå®ïŒ export APPLICATION_JAVA_TOOL_OPTIONS='-Xms512m -Xmx512m -XX:MaxMetaspaceSize=256m -XX:MetaspaceSize=256m -Xss1024k -XX:MaxDirectMemorySize=32m -XX:-UseCodeCacheFlushing -XX:InitialCodeCacheSize=128m -XX:ReservedCodeCacheSize=128m --illegal-access=deny' çµæ ã¡ã¢ãªãªãŒã¯ã®åçŸã«æåãããã³ããååŸã§ããŸããã IntelliJ IDEAã§ãã³ããã¡ã€ã«ãéããšãã¡ã¢ãªã®è©³çŽ°æ
å ±ãèŠãããšãã§ããŸãã ãã³ããã¡ã€ã«ã詳ããåæãããšãããå€éšAPIé¢é£éšåã§ãªã¯ãšã¹ãããšã«å€§éã®ãªããžã§ã¯ããæ°èŠäœæãããŠããããšãUtilç³»ã¯ã©ã¹ã®äžéšãSingletonãšããŠæ±ãããŠããªãããšãå€æããŸããã 6. Heap Dumpã®åæçµæ reactor.netty.http.HttpResources å
ã« HashMap$Node ã5,410åäœæãããŠããã352,963,672ãã€ãïŒ83.09%ïŒãå°æããŠããããšãåãããŸããã ã¡ã¢ãªãªãŒã¯çºçç®æç¹å® reactor.netty.resources.PooledConnectionProvider å
ã® channelPools(ConcurrentHashMap) ã§ãªãŒã¯ãçºçããŠãããæ ŒçŽãšååŸã®ããžãã¯ã«çç®ããŸããã poolFactory(InstrumentedPool) ååŸç®æ remote(Supplier<? extends SocketAddress>) ãš config(HttpClientConfig) ããååŸãã channelHash 㧠holder(PoolKey) ãäœæ holder(PoolKey) 㧠channelPools ãã poolFactory(InstrumentedPool) ãååŸããåæ§ã®ããŒãååšããã°è¿ãããªããã°æ°èŠäœæ ãªãŒã¯ã®åå ã¯ãåäžèšå®ã§ãåäžããŒãšå€æãããªãããšã§ãïŒ reactor.netty.resources.PooledConnectionProvider public abstract class PooledConnectionProvider<T extends Connection> implements ConnectionProvider { ... @Override public final Mono<? extends Connection> acquire( TransportConfig config, ConnectionObserver connectionObserver, @Nullable Supplier<? extends SocketAddress> remote, @Nullable AddressResolverGroup<?> resolverGroup) { ... return Mono.create(sink -> { SocketAddress remoteAddress = Objects.requireNonNull(remote.get(), "Remote Address supplier returned null"); PoolKey holder = new PoolKey(remoteAddress, config.channelHash()); PoolFactory<T> poolFactory = poolFactory(remoteAddress); InstrumentedPool<T> pool = MapUtils.computeIfAbsent(channelPools, holder, poolKey -> { if (log.isDebugEnabled()) { log.debug("Creating a new [{}] client pool [{}] for [{}]", name, poolFactory, remoteAddress); } InstrumentedPool<T> newPool = createPool(config, poolFactory, remoteAddress, resolverGroup); ... return newPool; }); channelPoolsã¯å称ã®éãChannelæ
å ±ãä¿æããŠãããªããžã§ã¯ãã§åæ§ã®ãªã¯ãšã¹ããæ¥ãéã«åå©çšãè¡ã£ãŠããã PoolKeyã¯ãã¹ãåãšæ¥ç¶èšå®ã®HashCodeãå
ã«äœæãããæŽã«ãã®HashCodeã䜿çšãããã channelHash ååŸç®æ reactor.netty.http.client.HttpClientConfig ã®éå±€ Object + TransportConfig + ClientTransportConfig + HttpClientConfig PooledConnectionProviderã«æž¡ãããLambdaåŒ com.kinto_jp.factory.common.adapter.HttpSupport L5 ããã§å®çŸ©ãããLambdaåŒã PooledConnectionProvider ã« config#doOnChannelInit ãšããŠåŒãæž¡ãããã abstract class HttpSupport { ... private fun httpClient(connTimeout: Int, readTimeout: Int) = HttpClient.create() .proxyWithSystemProperties() .doOnChannelInit { _, channel, _ -> channel.config().connectTimeoutMillis = connTimeout } .responseTimeout(Duration.ofMillis(readTimeout.toLong())) ... } 7. channelPoolsååŸæã®æåïŒå³è§£ïŒ ããŒãäžèŽããã±ãŒã¹ïŒæ£åžžïŒ channelPools ã«ååšããæ
å ±ãããŒãšãªãã InstrumentedPool ãåå©çšãããã ããŒãäžäžèŽã®ã±ãŒã¹ïŒæ£åžžïŒ channelPools ã«ååšããªãæ
å ±ãããŒãšãªãã InstrumentedPool ãæ°èŠäœæãããã ä»åçºçããã±ãŒã¹ïŒç°åžžïŒ channelPools ã«ååšããæ
å ±ãããŒãšãªããã InstrumentedPool ãåå©çšãããæ°èŠäœæãããŠããŸãã åé¡ç®æã®ä¿®æ£ãšæ€èšŒ ä¿®æ£ç®æ åé¡ãšãªã£ãŠããLambdaåŒãããããã£åŒã³åºãã«æžãæãã ä¿®æ£å abstract class HttpSupport { ... private fun httpClient(connTimeout: Int, readTimeout: Int) = HttpClient.create() .proxyWithSystemProperties() .doOnChannelInit { _, channel, _ -> channel.config().connectTimeoutMillis = connTimeout } .responseTimeout(Duration.ofMillis(readTimeout.toLong())) ... } ä¿®æ£åŸ abstract class HttpSupport { ... private fun httpClient(connTimeout: Int, readTimeout: Int) = HttpClient.create() .proxyWithSystemProperties() .option(ChannelOption.CONNECT_TIMEOUT_MILLIS, connTimeout) .responseTimeout(Duration.ofMillis(readTimeout.toLong())) ... } æ€èšŒ åææ¡ä»¶ MembersHttpSupport#members(memberId: String) ã1000ååŒã³åºãã PooledConnectionProvider#channelPools ã«æ ŒçŽãããŠãããªããžã§ã¯ãã®ä»¶æ°ã確èªããã ä¿®æ£åã®çµæ ä¿®æ£åã®ç¶æ
ã§å®è¡ãããšããã PooledConnectionProvider#channelPools ã«1000åã®ãªããžã§ã¯ããæ ŒçŽãããŠããããšãåãããŸããïŒãªãŒã¯ã®åå ïŒã ä¿®æ£åŸã®çµæ ä¿®æ£åŸã®ç¶æ
ã§å®è¡ãããšããã PooledConnectionProvider#channelPools ã«1åã®ãªããžã§ã¯ããæ ŒçŽãããŠããããšãåãããŸããïŒãªãŒã¯è§£æ¶ïŒã ãŸãšã ä»åã®èª¿æ»ã§ã¯ãKINTO FACTORYã®WebãµãŒãã¹ã«ãããã¡ã¢ãªãªãŒã¯ã®åå ãç¹å®ããé©åãªä¿®æ£ãè¡ãããšã§åé¡ã解決ããããšãã§ããŸãããç¹ã«ãå€éšAPIåŒã³åºãæã«å€§éã®ãªããžã§ã¯ããæ°èŠäœæãããŠããããšãã¡ã¢ãªãªãŒã¯ã®åå ã§ãããšå€æããLambdaåŒãããããã£åŒã³åºãã«å€æŽããããšã§è§£æ¶ãããŸããã ãã®ãããžã§ã¯ããéããŠã以äžã®éèŠãªæèšãåŸãããšãã§ããŸããïŒ æç¶çãªã¢ãã¿ãªã³ã° ïŒECSãµãŒãã¹ã®CPU䜿çšçã®ç°åžžãFull GCã®é »ç¹ãªçºçãéããŠãç¶ç¶çãªã¢ãã¿ãªã³ã°ã®éèŠæ§ãèªèããŸãããã·ã¹ãã ã®ããã©ãŒãã³ã¹ãåžžã«ç£èŠããããšã§ãåé¡ã®å
åãæ©æã«å¯ç¥ããè¿
éã«å¯ŸåŠããããšãã§ããŸãã æ©æã®åé¡ç¹å®ãšå¯Ÿç ïŒWebãµãŒãã¹ã®ã¡ã¢ãªãªãŒã¯ãçããé·æéAPIãåŒã³åºããŠã¡ã¢ãªç¶æ³ãåçŸãããããšã§ãå€éšãµãŒãã¹ã®ãªã¯ãšã¹ãæã«å€§éã®ãªããžã§ã¯ããæ°èŠäœæãããŠããããšãç¹å®ããŸãããããã«ãããåé¡ã®åå ãè¿
éã«ç¹å®ããé©åãªä¿®æ£ãå®æœã§ããŸããã ããŒã ã¯ãŒã¯ã®éèŠæ§ ïŒè€éãªåé¡ã«å¯ŸåŠããéã«ã¯ãããŒã å
šå¡ãååããŠåãçµãããšãæåãžã®éµãšãªããŸããä»åã®ä¿®æ£ãšæ€èšŒã¯ãéçºããŒã å
šå¡ã®ååãšåªåã«ãã£ãŠéæãããŸãããç¹ã«ã調æ»ãåæãä¿®æ£ãæ€èšŒãšãã£ãåã¹ãããã§ã®ååãææãäžããŸããã 調æ»ãã§ãŒãºã§ã¯ãå€ãã®èŠåŽããããŸãããäŸãã°ãã¡ã¢ãªãªãŒã¯ã®åçŸãããŒã«ã«ç°å¢ã§ã¯é£ãããå®éã®ç°å¢ã«è¿ãæ€èšŒç°å¢ã§å床æ€èšŒãè¡ãå¿
èŠããããŸããããŸããå€éšAPIãé·æéã«ããã£ãŠåŒã³åºãç¶ããããšã§ãã¡ã¢ãªãªãŒã¯ãåçŸãããã®åå ãç¹å®ããã®ã«å€ãã®æéãšåŽåãèŠããŸããããããããããã®å°é£ãä¹ãè¶ããããšã§ãæçµçã«ã¯åé¡ã解決ããããšãã§ãã倧ããªéææãåŸãããšãã§ããŸããã ãã®èšäºãéããŠãã·ã¹ãã ã®ããã©ãŒãã³ã¹åäžãšå®å®æ§ãç¶æããããã®å®è·µçãªã¢ãããŒããæèšãå
±æããŸãããåæ§ã®åé¡ã«çŽé¢ããŠããéçºè
ã®æ¹ã
ã®åèã«ãªãã°å¹žãã§ãã 以äžã§ãã
To Be Event Staff at try! Swift Tokyo 2024 With my childcare duties now more manageable, I decided to get more involved in activities and signed up for try! Swift Tokyo 2024! When I noticed they were looking for staff for try! Swift Tokyo 2024, I took the leap and submitted my application. To tell the truth, I had never been to try! Swift Tokyo, even as a participant, so I applied without really knowing what the atmosphere of the venue would be likeð
So in this article, I will share my experiences as a staff member at this event. What is try! Swift Tokyo 2024 try! Swift Tokyo 2024, held in March 2024, is a conference for iOS developers in Japan. Since its inception in 2016, it has consistently served as the largest gathering for professionals in the iOS development community. After a long pause due to COVID-19, this year marked its return for the first time in five years. Please visit the official website for more information. In my experience, iOSDC, another event that is also famous for its large iOS conferences, is largely driven by open speaker requests within Japan to shape the event's schedule. On the other hand, try! Swift Tokyo sources proposals internationally and invites renowned engineers from abroad to enrich its schedule, so there were many situations where we needed to communicate in English. Staff Activities This time, on the day, I worked as a staff member on the organizing side. It was my first time working behind the scenes, but it was a very exciting and enjoyable experience. One week before the event, all the staff gathered for a meeting where responsibilities were assigned. I was assigned to manage the venue, and was asked to do the following: Set up the venue Guiding the participants Venue guidance Handing out lunch boxes Collect garbage Venue teardown Other tasks within the venue  I usually spend most of my time writing code, so I was worried about whether my body could handle three days of physical work. However, I found it surprisingly refreshing to be active and interact with people In particular, I enjoyed talking to the attendees during reception and venue guidance. With many speakers and participants from abroad, try! Swift Tokyo needed English communication, which made me very aware of my limited language skills. Given that it was the first one in five years, there were many newcomers, myself included. Despite the occasional uncertainty about how to do things, everyone was able to work together and enjoy the activities, ending our first day successfully.  On the second day during the venue teardown, it was nice to see that some people had left their signatures on the sponsor boards that remainedð During the after party which followed the teardown, the participants and staff were able to have fun together, and it was very nice to meet new people there. On the third day, a workshop was conducted for participants, and witnessing their enthusiasm was truly inspiring, leaving me feeling upliftedðª I had some free time too, so I took the opportunity to exchange information with other staff members. The churrasco I ate at the post-teardown celebration was also deliciousð Conclusion  I wanted to take more pictures, but I regret that I couldn't because I was so focused on work... By joining as a staff member, I was able to encounter new people and experiences that I never would have gotten by joining as a participant, which made me feel a sense of fulfillment. I feel that it was a great experience. I'd love to join as staff again if I get the chance next time! If you are reading this article, I encourage you to challenge yourself and consider being a conference staff member as well! Finally, I'd like to say THANK YOU to all the organizers, speakers, and other participants!!! See you againð
ã¯ããã« ããã«ã¡ã¯ãKINTOãã¯ãããžãŒãºã¢ãã€ã«ã¢ããªã±ãŒã·ã§ã³éçºã°ã«ãŒãã® Rasel ã§ããç§ã¯çŸåšã my route Androidã¢ããªã®éçºã«åãçµãã§ããŸãã my route ã¯ãå€åºæã«å©çšãããã«ãã¢ãŒãã«ã¢ããªã§ãç®çå°ã®æ
å ±åéãå°å³äžã®ããŸããŸãªå Žæã®æ¢çŽ¢ãããžã¿ã«ãã±ããã®è³Œå
¥ãäºçŽãä¹è»æéã®æ¯æãåŠçãªã©ãè¡ãããšãã§ããŸãã ããŸãã¢ãã€ã«ã¢ããªã¯ç§ãã¡ã®æ¥åžžç掻ã«æ¬ ãããªããã®ã§ããæã
ã®ãããªãšã³ãžãã¢ã¯ãAndroidãšiOSã¢ããªãããããå¥ã§äœæãããããäž¡æ¹ã®ãã©ãããã©ãŒã ãéçºããããã«ã¯ããã«ã³ã¹ããçºçããŸãããããã®éçºã³ã¹ããåæžããããã«React NativeãFlutterãªã©ãæ§ã
ãªã¯ãã¹ãã©ãããã©ãŒã ãã¬ãŒã ã¯ãŒã¯ãç»å ŽããŸããã ããããã¯ãã¹ãã©ãããã©ãŒã ã¢ããªã®ããã©ãŒãã³ã¹ã«ã¯åžžã«èª²é¡ããããŸãããã€ãã£ãã¢ããªã®ãããªããã©ãŒãã³ã¹ã§ã¯ãããŸããããŸãããã©ãããã©ãŒã åºæã®æ°æ©èœãAndroidãiOSãããªãªãŒã¹ããããšããã¬ãŒã ã¯ãŒã¯éçºè
ãããµããŒããåããªããã°ãããªãå Žåããããããã«æéãããããŸãã ãã㧠Kotlin Multiplatform (KMP) ãå©ãã«ãªããŸãããã€ãã£ãã¢ããªäžŠã¿ã®ããã©ãŒãã³ã¹ã§ããã©ãããã©ãŒã éã§å
±æããã³ãŒããèªç±ã«éžæã§ããã®ã§ããKMPã§ã¯ãAndroidã®ãã€ãã£ã第äžèšèªã§ããKotlinã§Androidã¢ããªãéçºãããŠããŠãå®å
šã«ãã€ãã£ããªã®ã§ãããã©ãŒãã³ã¹äžã®åé¡ã¯ã»ãšãã©ãããŸãããiOSã®éšå㯠Kotlin/Native ã䜿çšããŠãããä»ã®ãã¬ãŒã ã¯ãŒã¯ãšæ¯èŒããŠããã€ãã£ãã¢ããªãšããŠéçºããããã®ã«è¿ãããã©ãŒãã³ã¹ããããŸãã æ¬èšäºã§ã¯ãSwiftUIã³ãŒããCompose Multiplatformãšçµ±åããæ¹æ³ã玹ä»ããŸãã KMPïŒã¢ãã€ã«ãã©ãããã©ãŒã ã§ã¯KMMãšããŠãç¥ãããŠããŸãïŒã§ã¯ããã©ãããã©ãŒã éã§å
±æããã³ãŒãã®éãšããã€ãã£ãã¢ããªã«å®è£
ããã³ãŒããèªç±ã«éžæã§ãããã©ãããã©ãŒã ã®ã³ãŒããšã·ãŒã ã¬ã¹ã«çµ±åãããŸãã以åã¯ãããžãã¹ããžãã¯ã®ã¿ããã©ãããã©ãŒã éã§å
±æã§ããŸããããä»ã§ã¯ UI ã³ãŒããå
±æã§ããããã«ãªããŸããã Compose Multiplatform ã«ãããŠãã UIã³ãŒãã®å
±æãå¯èœã«ãªããŸãããäžã«ãã以åã®èšäºãèªããšãã¢ãã€ã«ã¢ããªéçºã«ãããKotlin MultiplatformãšCompose Multiplatformã®äœ¿çšæ³ãããããç解ã§ããŸãã Kotlin Multiplatform Mobile (KMM)ã䜿ã£ãã¢ãã€ã«ã¢ããªéçº Kotlin Multiplatform MobileïŒKMMïŒããã³Compose Multiplatformã䜿çšããã¢ãã€ã«ã¢ããªã±ãŒã·ã§ã³ã®éçº ããã§ã¯ãå§ããŸãããïŒ æŠèŠ æã
ã¯UIéçºã§Compose Multiplatformã䜿çšããKMPãçšããŠã¢ããªéçºãããŠããŸããä»åã¯SwiftUIãCompose Multiplatformã«çµ±åããæ¹æ³ã瀺ãããããšãŠãã·ã³ãã«ãªGeminiãã£ããã¢ããªã䜿çšããŸãããŸãããã£ããã§ã®ãŠãŒã¶ãŒã®ã¯ãšãªãžã®è¿ä¿¡ã«ã¯ãGoogleã® Gemini Pro APIã䜿çšããŸãããã¢ããããšãç®çãªã®ã§ãã·ã³ãã«ã«ããããã«ããããã¹ãã¡ãã»ãŒãžã®ã¿ãèš±å¯ãããããç¡æçã® API ã䜿çšããŸãã Compose ãš SwiftUI ãã©ã®ããã«é£æºããã ãŸããæåã«å€§äºãªããšãããJetbrainã® Kotlin Multiplatform Wizard ã䜿çšããŠKMPãããžã§ã¯ããäœæããŸãããã®ãŠã£ã¶ãŒãã«ã¯ãå¿
èŠã«ãªãKMPã®åºæ¬çãªã»ããã¢ãããšãCompose Multiplatformãšãããã€ãã®åæSwiftUIã³ãŒããä»å±ããŠããŸãã  Kotlin Multiplatform Mobile pluginãã€ã³ã¹ããŒã«ããŠã Android Studio IDE ã䜿çšãããããžã§ã¯ããäœæããããšãã§ããŸãã ComposeãšSwiftUIãã©ã®ããã«é£æºãããããã¢ããŠã¿ãŸããComposableã³ãŒããiOS ã«çµã¿èŸŒãã«ã¯ãComposableã³ãŒãã ComposeUIViewController å
ã«ã©ããããå¿
èŠããããŸãã ComposeUIViewController 㯠UIKit ãã UIViewController ã®å€ãè¿ãããã®äžã«Composeã³ãŒãã®çµã¿ç«ãŠãã³ã³ãã³ããã©ã¡ãŒã¿ãšããŠå«ããããšãã§ããŸãã äŸ: // MainViewController.kt fun ComposeEntryPoint(): UIViewController { return ComposeUIViewController { Column( modifier = Modifier.fillMaxSize(), horizontalAlignment = Alignment.CenterHorizontally, verticalArrangement = Arrangement.Center ) { Text(text = "Hello from Compose") } } } 次ã«ããã®é¢æ°ã iOS åŽããåŒã³åºããŸãããã®ããã«ã¯ãSwiftUI ã®Composeã³ãŒããè¡šãæ§é ãå¿
èŠã§ãã以äžã®ã³ãŒãã¯ãå
±æã¢ãžã¥ãŒã«ã§ããUIViewController ã³ãŒãã SwiftUI ãã¥ãŒã«å€æããŸãã // ComposeViewControllerRepresentable.swift struct ComposeViewControllerRepresentable :UIViewControllerRepresentable { func updateUIViewController(_ uiViewController:UIViewControllerType, context:Context) {} func makeUIViewController (context:Context)-> some UIViewController { return MainViewControllerKt.ComposeEntryPoint() } } ããã§ã MainViewControllerKt.ComposeEntryPoint() ã®ååã詳ããèŠãŠã¿ãŸããããããã Kotlin ããçæãããã³ãŒãã«ãªããŸãããã®ãããå
±æã¢ãžã¥ãŒã«å
ã®ãã¡ã€ã«åãšã³ãŒãã«ãã£ãŠç°ãªãå ŽåããããŸããå
±æã¢ãžã¥ãŒã«å
ã®ãã¡ã€ã«åã Main.ios.kt ã§ã UIViewController returning function nameã ComposeEntryPoint() ã®å Žåã Main_iosKt.ComposeEntryPoint() ã®ããã«åŒã³åºãå¿
èŠããããŸãããã®ãããã³ãŒãã«ãã£ãŠç°ãªããŸãã 次ã«ããã® ComposeViewControllerRepresentable ãã³ãŒã ContentView() ã®å
éšããã€ã³ã¹ã¿ã³ã¹åããŸããããã§æºåã¯å®äºã§ãã // ContentView.swift struct ContentView:View { var body: some View { composeViewControllerRepresentable () .ignoresSafeArea (.all) } } ã³ãŒããèŠãŠãããããã«ããã®Composeã³ãŒã㯠SwiftUI å
ã®ã©ãã§ã䜿çšã§ããSwiftUI å
ã§å¥œããªããã«ãµã€ãºãå¶åŸ¡ã§ããŸããUI ã¯æ¬¡ã®ããã«ãªããŸã:  SwiftUI ã®ã³ãŒããComposeå
ã«çµ±åãããå Žåã¯ã UIView ã§ã©ããããå¿
èŠããããŸããSwiftUIã®ã³ãŒããKotlinã§çŽæ¥èšè¿°ããããšã¯ã§ããªããããSwiftã§èšè¿°ããŠKotliné¢æ°ã«æž¡ãå¿
èŠããããŸãããããå®è£
ããããã«ã é¢æ° ComposeEntryPoint() ã«ã UIView ã¿ã€ãã®åŒæ°ãè¿œå ããŠã¿ãŸãããã // MainViewController.kt fun ComposeEntryPoint(createUIView: () -> UIView): UIViewController { return ComposeUIViewController { Column( modifier = Modifier.fillMaxSize(), horizontalAlignment = Alignment.CenterHorizontally, verticalArrangement = Arrangement.Center ) { UIKitView( factory = createUIView, modifier = Modifier.fillMaxWidth().height(500.dp), ) } } } ãã㊠CreateUIView ã以äžã®ãã㪠Swift ã³ãŒããžæž¡ããŸãã // ComposeViewControllerRepresentable.swift struct ComposeViewControllerRepresentable : UIViewControllerRepresentable { func updateUIViewController(_ uiViewController: UIViewControllerType, context: Context) {} func makeUIViewController(context: Context) -> some UIViewController { return MainViewControllerKt.ComposeEntryPoint(createUIView: { () -> UIView in UIView() }) } } ããŠãä»ã®Viewãè¿œå ãããå Žåã¯ã以äžã®ããã«èŠªã©ãã㌠UIView ãäœæããŠãã ãã: // ComposeViewControllerRepresentable.swift private class SwiftUIInUIView<Content: View>: UIView { init(content: Content) { super.init(frame: CGRect()) let hostingController = UIHostingController(rootView: content) hostingController.view.translatesAutoresizingMaskIntoConstraints = false addSubview(hostingController.view) NSLayoutConstraint.activate([ hostingController.view.topAnchor.constraint(equalTo: topAnchor), hostingController.view.leadingAnchor.constraint(equalTo: leadingAnchor), hostingController.view.trailingAnchor.constraint(equalTo: trailingAnchor), hostingController.view.bottomAnchor.constraint(equalTo: bottomAnchor) ]) } required init?(coder: NSCoder) { fatalError("init(coder:) has not been implemented") } } 次ã«ãããã ComposeViewControllerRepresentable ã«è¿œå ããå¿
èŠã«å¿ããŠViewãè¿œå ããŸãã // ComposeViewControllerRepresentable.swift func makeUIViewController(context: Context) -> some UIViewController { return MainViewControllerKt.ComposeEntryPoint(createUIView: { () -> UIView in SwiftUIInUIView(content: VStack { Text("Hello from SwiftUI") Image(systemName: "moon.stars") .resizable() .frame(width: 200, height: 200) }) }) } åºåã¯æ¬¡ã®ããã«ãªããŸã:  ãã®æ¹æ³ã§ã¯ãå
±æã®åæå¯èœãªã³ãŒãã«ã奜ããªã ãSwiftUIã³ãŒããè¿œå ã§ããŸãã ãŸãã UIKit ã³ãŒããComposeå
ã«çµ±åãããå Žåãäžéã³ãŒããèªåã§äœæããå¿
èŠã¯ãããŸãããCompose MultiplatformãæäŸããComposableé¢æ° UIKitView () ã䜿çšããŠããã®äžã«UIKitã³ãŒããçŽæ¥è¿œå ã§ããŸãã // MainViewController.kt UIKitView( modifier = Modifier.fillMaxWidth().height(350.dp), factory = { MKMapView() } ) ãã®ã³ãŒã㯠iOS ãã€ãã£ãã®ãããç»é¢ãComposeå
ã«çµ±åããŸãã Gemni Chatã¢ããªã®å®è£
ããã§ã¯ãComposeã³ãŒããSwiftUIå
ã«çµ±åããŠã Gemini Chat ã¢ããªã®å®è£
ãé²ããŸããããJetpack Compose ã® LazyColumn ã䜿çšããŠãåºæ¬çãªãã£ãã UI ãå®è£
ããŸããCompose Multiplatformå
ã«SwiftUIãçµ±åããããšãäž»ãªç®çãªã®ã§ãComposeãããŒã¿ãããžãã¯çãä»ã®éšåã®å®è£
ã«ã€ããŠã¯ããã§ã¯å²æããŸããGemini Pro APIãå®è£
ãããããæã
ã¯Ktorãããã¯ãŒãã³ã°ã©ã€ãã©ãªãå©çšããŸãããKtorã®å®è£
ã«ã€ããŠã®è©³çŽ°ã¯ã Creating a cross-platform mobile application ã®ããŒãžãã芧ãã ããã ãã®ãããžã§ã¯ãã§ã¯ãCompose Multiplatformã§å
šãŠã®UIãå®è£
ããŸãããCompose Multiplatformã®TextFieldã§ã¯iOSåŽã§ããã©ãŒãã³ã¹ã«åé¡ãããã®ã§ãiOSã¢ããªã®å
¥åãã£ãŒã«ãã«ã®ã¿SwiftUIã䜿çšããŸãã ComposeEntryPoint() é¢æ°ã®äžã«Composeã³ãŒããå
¥ããŠã¿ãŸãããããããã®ã³ãŒãã«ã¯ãTopAppBarãå«ããã£ããUIãšã¡ãã»ãŒãžã®ãªã¹ããå«ãŸããŠããŸããããã«ã¯ãAndroidã¢ããªã§äœ¿çšãããå
¥åãã£ãŒã«ãã®æ¡ä»¶ä»ãå®è£
ããããŸãã // MainViewController.kt fun ComposeEntryPoint(): UIViewController = ComposeUIViewController { Column( Modifier .fillMaxSize() .windowInsetsPadding(WindowInsets.systemBars), horizontalAlignment = Alignment.CenterHorizontally ) { ChatApp(displayTextField = false) } } false ã displayTextField ã«æž¡ããã®ã§ãiOS ããŒãžã§ã³ã®ã¢ããªã§ã¯ Compose å
¥åãã£ãŒã«ããã¢ã¯ãã£ãã«ãªããŸããããããŠãAndroidåŽã®TextFieldã«ã¯ããã©ãŒãã³ã¹ã®åé¡ããªããããAndroid å®è£
åŽããComposableé¢æ°ããã® ChatApp () ã®Composableé¢æ°ãåŒã³åºããšã displayTextField ã®å€ã¯ true ã§è¿ã£ãŠããŸããïŒããã¯Android ã®ãã€ãã£ã UI ã³ã³ããŒãã³ãã§ããïŒ ããã§ã¯ãSwift ã³ãŒãã«æ»ã£ãŠSwiftUIã§å
¥åãã£ãŒã«ããå®è£
ããŸãã // TextInputView.swift struct TextInputView: View { @Binding var inputText: String @FocusState private var isFocused: Bool var body: some View { VStack { Spacer() HStack { TextField("ã¡ãã»ãŒãžãå
¥åãã...", text: $inputText, axis: .vertical) .focused($isFocused) .lineLimit(3) if (!inputText.isEmpty) { Button { sendMessage(inputText) isFocused = false inputText = "" } label: { Image(systemName: "arrow.up.circle.fill") .tint(Color(red: 0.671, green: 0.365, blue: 0.792)) } } } .padding(15) .background(RoundedRectangle(cornerRadius: 200).fill(.white).opacity(0.95)) .padding(15) } } } ãããŠã ContentView æ§é äœã«æ»ãã以äžã®ããã«ä¿®æ£ããŸã: // ContentView.swift struct ContentView: View { @State private var inputText = "" var body: some View { ZStack { Color("TopGradient") .ignoresSafeArea() ComposeViewControllerRepresentable() TextInputView(inputText: $inputText) } .onTapGesture { // Hide keyboard on tap outside of TextField UIApplication.shared.sendAction(#selector(UIResponder.resignFirstResponder), to: nil, from: nil, for: nil) } } } ããã§ã¯ ZStack ãè¿œå ãããã®äžã« TopGradient ã«ã©ãŒãšãModifier ignoresSafeArea () ãè¿œå ããŠãã¹ããŒã¿ã¹ããŒã®è²ãä»ã® UI ã®è²ãšäžèŽããããã«ããŸããã 次ã«ãå
±æãããCompose ã³ãŒãã®ã©ãã㌠ComposeViewControllerRepresentable ãè¿œå ããã¡ã€ã³ã®ãã£ããUIãå®è£
ããŸããããããŠã TextInputView() ãšããSwiftUIãã¥ãŒãè¿œå ããŸãããããã«ãããiOSã¢ããªã®ãŠãŒã¶ãŒã«ãiOSãã€ãã£ãã³ãŒãã§ã¹ã ãŒãºãªããã©ãŒãã³ã¹ãæäŸããããšãã§ããŸããæçµçãªUIã¯æ¬¡ã®ããã«ãªããŸãã Gemini Chat iOS Gemini Chat Android   ããã§ã¯ãChatAppã®UIã³ãŒãå
šäœãKMPã®Compose Multiplatformã§AndroidãšiOSã®äž¡æ¹ã«å
±æãããiOSã®å
¥åãã£ãŒã«ãã®ã¿ãSwiftUIã«ãã€ãã£ãã«çµ±åãããŠããŸãã ãã®ãããžã§ã¯ãã®å®å
šãªãœãŒã¹ã³ãŒãã¯ãGitHub ã§å
¬éãªããžããªãšããŠå
¬éãããŠããŸãã GitHubãªããžããª:Compose Multiplatformã«ãããSwiftUI ãããã« ãã®ããã«ãKotlin Multiplatformãš Compose Multiplatform ã䜿ãããšã§ãã¯ãã¹ãã©ãããã©ãŒã ã¢ããªã§ã®ããã©ãŒãã³ã¹ã®åé¡ã解決ããªããããŠãŒã¶ãŒã«ãã€ãã£ãã®ãããªæäœæãšå€èŠ³ãæäŸã§ããŸãããŸãããã©ãããã©ãŒã éã§ã³ãŒãã奜ããªã ãå
±æã§ãããããéçºã³ã¹ããåæžã§ããŸããCompose Multiplatformã§ã¯ããã¹ã¯ãããã¢ããªãšã³ãŒããå
±æããããšãã§ããŸããã§ããããåäžã®ã³ãŒãããŒã¹ããã¹ã¯ãããã¢ããªã ãã§ãªãã¢ãã€ã«ãã©ãããã©ãŒã ã§ã䜿çšã§ããŸããããã«ããã©ãããã©ãŒã éã§ã®ã³ãŒãããŒã¹å
±æãä¿é²ãããããWebãµããŒããé²è¡äžã§ããKotlin Multiplatform (KMP) ã®ãã1ã€ã®å€§ããªå©ç¹ã¯ãã³ãŒããç¡é§ã«ããããšãªãããã€ã§ããã€ãã£ãéçºã«åãæ¿ããããšãã§ããç¹ã§ããAS-ISã®KMPã³ãŒã ã¯Androidãã€ãã£ãã®ãããAndroidã¢ããªã§ã¯ãã®ãŸãŸå©çšã§ããiOSã¢ããªãå¥éåãé¢ããŠéçºããããšãã§ããŸãããŸããKMPã«ãã§ã«å®è£
ãããã®ãšåãSwiftUIã³ãŒããåå©çšããããšãå¯èœã§ãããã®ãã¬ãŒã ã¯ãŒã¯ã¯ãé«æ§èœã®ã¢ããªã±ãŒã·ã§ã³ãæäŸããã ãã§ãªããå
±æããã³ãŒãã®å²åãèªç±ã«å€æŽãããããã€ãã£ãéçºã«ãã€ã§ãåãæ¿ãããã§ããŸãã æ¬èšäºã¯ãããŸã§ãšããŸãããKINTOãã¯ãããžãŒãºã®ããã¯ããã°ã§ã¯ä»åŸããããããèšäºãçºä¿¡ããŠãããŸãïŒHappy Coding!
Introduction Hello! My name is Morimoto, and I am a backend engineer at KINTO Technologies. I am part of the KINTO ONE development Group where I primarily use Java for KINTO ONE. But this time, I would like to introduce a study session of GraphQL that we're conducting separately from our regular work. What is GraphQL? GraphQL is a query language. Unlike other languages such as SQL, GraphQL can interact with multiple data sources, not just a specific one. If the schema is defined on the backend side, the frontend side can freely retrieve the items in the object according to the definition. Unlike the REST API, with GraphQL, you have the flexibility to specify what information the frontend wants to return from the backend. There is no need to get unnecessary information, and there is no need to call the API multiple times to get nested objects. Purpose of the Study Group There were two main purposes: To improve our technical skills To interact beyond our respective teams To Improve Technical Skills We wanted to catch up with new information in addition to the technology we use in our daily work, but each team member felt that it was a high hurdle to overcome alone. For example, our lack of language knowledge could be cited as a barrier. The GraphQL tutorial we decided to follow used Typescript. So we had to learn Typescript first before learning GraphQL. The idea was that by supplementing each other with our different knowledge and experiences, we could overcome challenges and make the learning curve less steep. To Interact Beyond Our Respective Teams We also wanted to make it as an opportunity for members -regardless of group, team, project or different ages-, to interact with each other. Many of us were good friends who already knew each other, but we were determined to get along better by getting together on a regular basis. I also thought that the study session would be an opportunity to learn about new aspects of each other. Content Details Why GraphQL? Those who typically implemented APIs on the backend were struggling with the need to create an API every time a requirement came. Of course, there are times that is faster to process data on the server side, but it is troublesome to increase the number of APIs that return information as it is. As for me, ever since I heard that GraphQL was a good solution for this, I wanted to try it out. Some members already had some experience using GraphQL, but they wanted to understand the overall process flow, so we decided to properly study it together. Tutorials Used for the Study Sessions We chose Apollo GraphQL for the GraphQL library, and used the tutorial linked below. GraphQL Tutorials The reason why we chose it is due to the volume of tutorials available and we felt it was a good introduction. In addition, one of the study group members had used Apollo GraphQL in their work, so we knew there was a track record of being used within the company. Summary of the Study Group Date and Time It was held once a week after 6pm when members had time. Members The group consists of eight young members ranging from 25 to 28 years old. Our background and expertise was diverse, each belonging to different domains such as web application frontend, backend, as well as mobile application frontend and backend. What We Did We completed all five chapters of the tutorial, from Lift-off I to V. It describes the basics of implementing GraphQL. How It Was Conducted and What We Arranged We conducted the study group following the below flow: We opted to go through the tutorials in Mokumoku-kai style. We reinforced our learning by doing presentations to each other of the content from the tutorials we reviewed. We started by holding our series of Mokumoku-Kai . Mokumoku-Kai is a study group method where everyone gathers, sharing questions and ideas when needed, but mainly focuses on their own. As mentioned, some had used Apollo GraphQL before, but none had a complete picture of the process. For that reason, we first completed the same tutorials and then discussed and resolved any points that came up. However, some mentioned they were doubtful if they really understood it, and that maybe it was good to refresh concepts first before moving on. So we decided to present each section to one another on a rotating basis. The presentation format required presenters to understand the tutorial perfectly. At the study session, there were moments where, upon reviewing, we found answers to questions in parts where we had been progressing somewhat aimlessly. During the presentation however, we could ask questions, change the source code and try it out, and there were new discoveries that one would not have found on their own. A glimpse at one of our sessions. In the foreground are boxes of sandwiches prepared for the study group. Conclusion First and foremost, we achieved a deep understanding of GraphQL thanks to these sessions. By using our knowledge and experience to complement each other, we were able to proceed faster and more reliably than anyone could on their own. Having study partners also helped us to persevere through moments when we felt like giving up. We aim to continue with the remaining chapters of Apollo GraphQL tutorials and learn more about other technical topics. We even discussed how we would love to create some kind of application in the process. By exploring the languages, frameworks, and architectures each of us is interested in, I hope to keep getting better with my technical capabilities.
Introduction Hello! My name is Morimoto, and I am a backend engineer at KINTO Technologies. I am part of the KINTO ONE development Group where I primarily use Java for KINTO ONE. But this time, I would like to introduce a study session of GraphQL that we're conducting separately from our regular work. What is GraphQL? GraphQL is a query language. Unlike other languages such as SQL, GraphQL can interact with multiple data sources, not just a specific one. If the schema is defined on the backend side, the frontend side can freely retrieve the items in the object according to the definition. Unlike the REST API, with GraphQL, you have the flexibility to specify what information the frontend wants to return from the backend. There is no need to get unnecessary information, and there is no need to call the API multiple times to get nested objects. Purpose of the Study Group There were two main purposes: To improve our technical skills To interact beyond our respective teams To Improve Technical Skills We wanted to catch up with new information in addition to the technology we use in our daily work, but each team member felt that it was a high hurdle to overcome alone. For example, our lack of language knowledge could be cited as a barrier. The GraphQL tutorial we decided to follow used Typescript. So we had to learn Typescript first before learning GraphQL. The idea was that by supplementing each other with our different knowledge and experiences, we could overcome challenges and make the learning curve less steep. To Interact Beyond Our Respective Teams We also wanted to make it as an opportunity for members -regardless of group, team, project or different ages-, to interact with each other. Many of us were good friends who already knew each other, but we were determined to get along better by getting together on a regular basis. I also thought that the study session would be an opportunity to learn about new aspects of each other. Content Details Why GraphQL? Those who typically implemented APIs on the backend were struggling with the need to create an API every time a requirement came. Of course, there are times that is faster to process data on the server side, but it is troublesome to increase the number of APIs that return information as it is. As for me, ever since I heard that GraphQL was a good solution for this, I wanted to try it out. Some members already had some experience using GraphQL, but they wanted to understand the overall process flow, so we decided to properly study it together. Tutorials Used for the Study Sessions We chose Apollo GraphQL for the GraphQL library, and used the tutorial linked below. GraphQL Tutorials The reason why we chose it is due to the volume of tutorials available and we felt it was a good introduction. In addition, one of the study group members had used Apollo GraphQL in their work, so we knew there was a track record of being used within the company. Summary of the Study Group Date and Time It was held once a week after 6pm when members had time. Members The group consists of eight young members ranging from 25 to 28 years old. Our background and expertise was diverse, each belonging to different domains such as web application frontend, backend, as well as mobile application frontend and backend. What We Did We completed all five chapters of the tutorial, from Lift-off I to V. It describes the basics of implementing GraphQL. How It Was Conducted and What We Arranged We conducted the study group following the below flow: We opted to go through the tutorials in Mokumoku-kai style. We reinforced our learning by doing presentations to each other of the content from the tutorials we reviewed. We started by holding our series of Mokumoku-Kai . Mokumoku-Kai is a study group method where everyone gathers, sharing questions and ideas when needed, but mainly focuses on their own. As mentioned, some had used Apollo GraphQL before, but none had a complete picture of the process. For that reason, we first completed the same tutorials and then discussed and resolved any points that came up. However, some mentioned they were doubtful if they really understood it, and that maybe it was good to refresh concepts first before moving on. So we decided to present each section to one another on a rotating basis. The presentation format required presenters to understand the tutorial perfectly. At the study session, there were moments where, upon reviewing, we found answers to questions in parts where we had been progressing somewhat aimlessly. During the presentation however, we could ask questions, change the source code and try it out, and there were new discoveries that one would not have found on their own. A glimpse at one of our sessions. In the foreground are boxes of sandwiches prepared for the study group. Conclusion First and foremost, we achieved a deep understanding of GraphQL thanks to these sessions. By using our knowledge and experience to complement each other, we were able to proceed faster and more reliably than anyone could on their own. Having study partners also helped us to persevere through moments when we felt like giving up. We aim to continue with the remaining chapters of Apollo GraphQL tutorials and learn more about other technical topics. We even discussed how we would love to create some kind of application in the process. By exploring the languages, frameworks, and architectures each of us is interested in, I hope to keep getting better with my technical capabilities.
ãããã〠çããŸããã«ã¡ã¯ãããã¯ããã°ããŒã æ¹ãæè¡åºå ±ã°ã«ãŒãã®æ£®ã§ãã å®ã¯ãã®4æãããããã¯ããã°ããŒã ã¯ãæè¡åºå ±ã°ã«ãŒãããšããŠçãŸãå€ãããŸããâš ä»åŸãšããããããé¡ãããŸãðââïž æè¡åºå ±ä»¥å€ã®ãä»äºã¯å¥èšäºã§æžããŠãããŸãã®ã§ããããèå³ããã°ãã²ãäžèªãã ãã ð KINTOã®ã°ããŒãã«å±éã«ãããGDPRçå人ããŒã¿é¢é£æ³å¯Ÿå¿ GDPR察å¿! Cookieåæãããã¢ãããã°ããŒãã«ãµã€ãã«èšçœ®ãã話 å°å
¥ 2024幎1æ31æ¥ãKINTOãã¯ãããžãŒãºïŒKTCïŒã§ã¯åãšãªãã®å
šç€Ÿãªãã©ã€ã³ããŒãã£ã³ã°ãéå¬ããããŸããð 2024幎ã®Kick Offãšããäœçœ®ã¥ãã§ããå®ã¯ãã®ã€ãã³ããå®å
šããã ã¢ããã§äŒç»ã»éå¶ãããŸããããã®å€§èŠæš¡ããŒãã£ã³ã°ãã©ã®ããã«äœãããããæ¬èšäºã§è£åŽãã玹ä»ããŸããä»åŸã®ããã®åå¿é²ã®ãããªãã®ã§ããããèªç€Ÿã§å
補ã€ãã³ãããããšã«ãªã£ããã©ã©ããããïŒïŒããšããæ¹ã«å°ãã§ãåèã«ãªãã°äœããã§ãã æ¬æ¥ãªãããã«ã¬ããŒããããšããããç§ã®é
çã«ããçŽå幎åŸã®èšäºå
¬éãšãªã£ãŠããŸã£ãããšããèš±ããã ããðââïž (ã€ãã³ãéå¶ã®èšäºã¯é®®åºŠã倧äºãªã®ã«âŠ ð) äŒç»ã®ãã£ãã ã³ããçŠäžã«åŒç€ŸåŸæ¥å¡æ°ã¯çå¢ããããŸãçŽ350åã®ç€Ÿå¡ãæå±ããŠããŸãã ãã®èŠæš¡ã«ãªããšãã¯ã暪ã®ç¹ãããäžäœæãçã¿åºãããšã¯ãªããªãé£ããã以åãããªãã©ã€ã³ã€ãã³ããããŒã ãã«ãã£ã³ã°ã€ãã³ããæ±ãã声ãå€ããããŸããããŸãããããå±€ããã®ã¡ãã»ãŒãžçºä¿¡ã®å Žãå€ãã¯ãªãã®ã§ãå
šäœããžã§ã³ã®æµžéã«ã¯æéãèŠããŠããŸããã ãããã£ã課é¡ãèžãŸãããã¢ãã¿ãŒã³ããã ããå
šç€Ÿå¡ãéãŸããæ©äŒãããã°å°ãã¯ãã®èª²é¡ãã¯ãªã¢ã«ãªãããããšã€ãã³ãéå¶ã«ããæºãã3åã§äŒç»ãå§ãŸããŸãããããã11æåæ¬ã®ã話ã ãŸãã¯å€§æ ã 11æã«3人ã§äŒç»ãéå§ããã®ã§ãã1æéå¬ãªã®ã§å®æœãŸã§3ãµæããæéããªããã¹ã±ãžã¥ãŒã«ã¯ããªãã¿ã€ãã§ããã ã©ããªã¹ã±ãžã¥ãŒã«ã以äžã®ããã«åŒããŠé²ããããšã«ãªããŸããã ãŸãã¯éå¬ããããšèªäœã«è³åãåŸããããäŒç»ã®å€§æ ã以äžã®ããã«æ€èšããŸããã éå¬ç®ç 2023幎1幎ã®ç·æ¬ãš2024幎ã®ããã¯ãªã å
±éã®ããžã§ã³ãå
±æããããšã»ä»éšçœ²é亀æµã«ããçµç¹ã®äžäœæéžæ äŒç»å
容 æ¯æã®å
šç€Ÿå¡ããŒãã£ã³ã°ïŒéçºç·šææ¬éšäŒïŒã®æ¡å€§ç ååã¯ãªã³ã©ã€ã³åå å¯èœïŒæ¥åå
ïŒ æ芪äŒã¯ãªãã©ã€ã³åå ã®ã¿ïŒæ¥åå€ïŒ ã³ã³ãã³ã Category Time Contents Note ãªã 15:00-16:00â äŒå Žèšå¶/ãªããŒãµã« é³é¿æºåãé²è¡ã®èª¿æŽãªã© 16:00â-16:30â å
¥å Žéå§ãåä»â åå è
ã®åä» æ¬ç·š 16:30-16:35â éå ŽããªãŒããã³ã° 16:35â-16:40â 2023幎ã®æ¯ãè¿ãââïŒå¯ç€Ÿé·ïŒ 2023幎ã®æ¯ãè¿ããš2024幎ã®å±æ ãã·ã§ã¢ 16:40-17:30â 2023幎ã®æŒ¢åââ 2022幎æ«ã«ãå®æœããŸãããåã°ã«ãŒãã®æ¯ãè¿ãã³ãŒã㌠17:30â-17:40â äŒæ© / ãã¬ãŒã³æºåâââ 17:40-18:35â K-1ã°ã©ã³ããªââââ åéš2023幎ã®ä»£è¡šæ¡ä»¶ããã¬ãŒã³ããè¡šåœ°ïŒ 18:35â-18:45â äŒæ©âââââ 18:45-19:00ââ K-1ã°ã©ã³ããªãçµæçºè¡šââââââ 衚地ãšåè³è
ããã®ã³ã¡ã³ã 19:00â-19:05â ç·æ¬âãš2024幎ã«åããŠïŒç€Ÿé·ïŒ 2023幎ç·æ¬ãš2024幎ãžã®æåŸ
ãã·ã§ã¢ æèŠªäŒ 19:05-19:20â åçæ®åœ± / äŒæ© / 転æâ 19:20â-20:50â æ芪äŒââ ã»ä¹Ÿæ¯ïŒé¡éã ã»ããã²ãŒã ãå
¥ããŠå
šç€Ÿäº€æµã®æéïŒâ 20:50-21:00ââ æ€åäœæ¥âââ 21:00å®å
šéåºâ åã°ã«ãŒããå·»ã蟌ãïŒ å€§æ ã決å®ããã®ã§ãå
šäœã®äººæ°ãææ¡ãã¹ã瀟å
ã«å
¬ç€ºããŸããã æ®æ®µã®ç€Ÿå
ã€ãã³ãã¯Slackã§å
šç€Ÿã«åããŠäžåºŠã¢ããŠã³ã¹ããããšãå€ãã®ã§ãããä»åã¯ãªã«ãå
šç€Ÿã€ãã³ããåã°ã«ãŒãã®ååãªãããŠã¯çµ±çãåããŸããð€Šââïž ããã§ãåã°ã«ãŒãããæ
åœè
ãç«ãŠãŠããã ããåã°ã«ãŒãã®åããŸãšãããé¡ãããŸããã æ®æ®µã¯äœåºŠãäœåºŠãéå¶ããã¢ããŠã³ã¹ããªããšãªããªãååããããªãåçããåã°ã«ãŒãæ
åœè
ã«åããŸãšããŠããã ããããšã§æ¯èŒçã¹ã ãŒãºã«ããåãŸã§ã«ååããããšãã§ããŸãããåGæ
åœã®çæ§ãæ¬åœã«ããããšãããããŸããïŒå€§æè¬ ðâ€ïž  ç§ã®éšã§ã®åç¥ã®æ§å æ³å以äžã®ãªãã©ã€ã³åå çïŒ ä»åã®ã€ãã³ãã¯éçºç·šææ¬éšäŒãã€ãŸãå
šç€Ÿå¡ããŒãã£ã³ã°ãšãã建ä»ãã§ãã®ã§ãåºæ¬ã¯å
šå¡åå å¿
é ã§ãã 家åºã®éœåãåºåŒµãªã©ã§ã©ãããŠããªã³ã©ã€ã³åå ã«ãªãæ¹ãããã£ããããŸãããããã§ã300åèŠæš¡ã®äŒå Žãå¿
èŠã§ããã ãªãã£ã¹è¿éã§ã®äŒå Žæ¢ãã¯ããªãèŠæŠããŸããããçã£ç«¯ããæ€çŽ¢ããŠã¯é»è©±ãç¹°ãè¿ããå¥è·¡çã«ç¥ä¿çºãªãã£ã¹ããåŸæ©5åã® ãç¥ç°ã¹ã¯ãšã¢ããŒã«ã ãæé
ããããšãã§ããŸããã  ãšã£ãŠãããããªäŒå Žãç¥ç°ã¹ã¯ãšã¢æ§ãããããšãããããŸãã ãããåŸããªã³ã©ã€ã³åå ã«ãªã£ãæ¹ãè±èªéèš³ãã£ãã«ïŒåŸè¿°ïŒã®ãããæ¬éšäŒããŒãã¯Webinaré
ä¿¡ãè¡ããŸãããé
ä¿¡æ
åœã®æ¹ã
ãæ¬åœã«ãã€ãããããšãðâ€ïžã®æ°æã¡ã§ãã åæ
åœã§äžŠè¡ããŠã¿ã¹ã¯ãéè¡ïŒ ã€ãã³ããè¡ãéã¯éå¶ããŒã ãåããŠããããã§ã¿ã¹ã¯ãåãããŸããKINTOãã¯ãããžãŒãºã®ããããšããã¯ã¢ãµã€ã³ããããããããèªèµ°ããŠããããšããâŠïŒïŒåã®ããã«åããŠããããæèŠããŠããããããã®ã§ãéåžžã«å©ãããŸãã ä»åã¯åè¿°ã®åG代衚è
ã®äžããæ°åãè€æ°ã®åœ¹å²ã«åããŠã¢ãµã€ã³ããŸããã åœ¹å² ã¿ã¹ã¯è©³çŽ° çµ±æ¬ å
šäœã®åããŸãšããåæ
åœè
ãå°ã£ããšãã®çžè«åœ¹ åžäŒ ã€ãã³ãå
šäœã®ãã¡ã·ãªããŒã·ã§ã³ãçãäžãïŒäžçªéèŠïŒïŒã®æœçæ€èš åä» èªå°ã®æµããæ€èšãæ¡å
ãã¹ãäºé
ã®åããŸãšã éèš³ å€æ°æå±ããNon-Japaneseã«åããéèš³çšã«å€éšéèš³è
æ§ãšã®èª¿æŽæ
åœ ä»å¹Žã®æŒ¢å åGãã2023幎ãè¡šã挢åã»2023幎ã®ææãš2024幎ãžã®ææ°èŸŒã¿ãåããŸãšã K-1ã°ã©ã³ã㪠åéšã®ä»£è¡šæ¡ä»¶ãåããŸãšã 瀟é·ã»å¯ç€Ÿé·æšæ¶åããŸãšã 瀟é·å¯ç€Ÿé·ã®äŒãããã¡ãã»ãŒãžãšã€ãã³ã趣æšãããåãããŠè³æãäœæ æèŠªäŒ ã±ãŒã¿ãªã³ã°ãäœã«ãããïŒæ芪äŒã§äœããããã®æ€èš ããã«ã㣠å
šå¡ã«é
åžãããããã«ãã£ãæ¯åãªã©ã®äœæ åžäŒ åœæ¥ã®æ§åã¯ãŸãå¥ã®èšäºã§ãäŒãã§ãããšæããŸãããä»åã¯ä»¥åããã€ãã³ãã®åžäŒãçãäžããããŠãããŠãã3åã«ç·ååžäŒããé¡ãããŸãããåœæ¥ã®ã¿ã€ã ã©ã€ã³ã«åãããŠããŒãã®æ¯ãåãã§ãã£ãããåœæ¥ã®æµããæ³å®ããŠããã€ã®ã¿ã€ãã³ã°ã§ã©ããã£ãã¹ã©ã€ããå¿
èŠãïŒã©ãçãäžãããïŒãªã©ãèããŠãããŸããããã£ããã¿ã€ã ã©ã€ã³ã¯ãã£ããã®ã®ãå®éã«åžäŒãããã«ããã£ãŠæ°ã«ãªããã€ã³ããæŽãåºããããã¹ã¯ãªãããäœã£ãããäœã®äŸé ŒãããŠããªãã®ã«ãåžäŒãé¡ãããŸãããšèšã£ãã ãã§ãããŸã§ãã£ãŠãããŠããŸãããææ¿ðâ€ïž  é²è¡äžã®æ°ã«ãªããã€ã³ã  åžäŒã¹ã¯ãªãã åä» å
éšã€ãã³ããšã¯ããããã ãå€ãã®äººæ°ãéãŸãã€ãã³ããšãªããšãæéã®ããåä»ãéåžžã«éèŠã§ããåä»æ
åœãšããŠã¡ã€ã³ã§5åãæãæããŠãããŸãããïŒãããŠåœæ¥ã¯ããããã®äººããæäŒãããŠãã ãããŸããâŠïŒïŒïŒïŒ åä»ã§éèŠãªã®ã¯ãªããšãã£ãŠãããã«ã¹ã ãŒãºã«æ¡å
ãããïŒåä»ã§ã€ãã³ãåå è
ã®ç¬¬äžå°è±¡ã決ãŸããããåä»ã«äººãæ»çããã°ããã»ã©ã€ãã³ããžã®äžæºã¯ããŸã£ãŠãããŸãã ããã§ä»å工倫ããã®ã¯åŸæ¥ã®åºåžè
ãªã¹ãã§ãïœãã€ããã®ã§ã¯ãªããåºåžè
ã®äž»äœæ§ã«ä»»ãã以äžã®æµãã§åä»ãè¡ããŸããã äºãå°ç·ãäœã£ãŠããããšã§ãåä»ã§åæ»ããããšãªãéåžžã«ã¹ã ãŒãºã«äŒå Žãžèªå°ããããšãã§ããŸããã äžæ¹ã§ãäŒå ŽãŸã§ã®èªå°ãè¡ãå±ããŠããªãã£ãã®ã¯åçç¹ã次åã®æ¹åç¹ãšããŠã¡ã¢ã§ãð éèš³ KTCã¯å€åœç±ãªã¡ã³ããŒã§æ§æãããŠãããè±èªã®ã»ããåŸæãªã¡ã³ããŒãå€æ°æå±ããŠããŸããä»åã¯2023幎ã®ç·æ¬ãã€2024幎ã®ããã¯ãªããšããããšã§çµå¶å±€ã®å€§äºãªè©±ãå
¥ããããæ¬éšäŒæ¬ç·šã¯å
šã³ã³ãã³ãéèš³ãå
¥ããããšã«ãªããŸããããããã2æéåã«ãåã¶æ¬ç·šãé次éèš³ããã®ã¯çŽ 人ã§ã¯å°åºç¡çã§ãð€Šââïž ããã§ã以åãããªãªãšã³ããŒã·ã§ã³ã®éèš³ãªã©ã§ãäžè©±ã«ãªã£ãŠããéèš³äŒç€Ÿæ§ã«ãé¡ãããããšã«ããŸããã ð»ZOOMã§ã®éèš³ã¯éèš³æ©èœãONã«ããŠãããšèšèªãã£ãã«ãåãæ¿ããããããã«ãªã£ãŠããŸãð» éèš³è
æ§ãè³ã§æ¥æ¬èªãèãðããã®ãŸãŸè±èªãã£ãã«ã§è±èªã§çºè©±ð£ïžããããšã§ãè±èªãã£ãã«ã«ã¯è±èªé³å£°ãæµããä»çµã¿ã§ãã èšå®ã®æ¹æ³ã¯ãã¡ãð ããŒãã£ã³ã°ãŸãã¯ãŠã§ãããŒã§ã®èšèªéèš³ã®äœ¿çš éå¶ããŒã å
ã®éèš³æ
åœã¯çŸå°ã«ããªãéèš³è
æ§ãšã³ãã¥ãã±ãŒã·ã§ã³ãåããé³å£°ã»æ åãã©ãã«ãäŒå Žã®æ§åãªã©ãé©å®ã³ãã¥ãã±ãŒã·ã§ã³ããŸããéèš³ãããããšã§ãçµå¶å±€ã®ã¡ãã»ãŒãžãç確ã«äŒããããšãã§ããŸãããããã®éèš³è
æ§ã«ã¯é ãäžãããŸããðââïž 2023幎ã®æŒ¢å 2022幎æ«ãå®æœãããã®äŒç»ãåã°ã«ãŒããããããŒãžã£ãŒãç»å£ãã1幎ãè¡šã挢åãšç·æ¬ããããŠæ°ãã1幎ã«åããææ°èŸŒã¿ãå
±æããŸãã äºåã«22ã°ã«ãŒãã®åçãåããŸãšããŠåœæ¥ã®è³æã«åæ ãããäœæ¥ãæ
åœè
ã«ãé¡ãããŸããã å¿ãããããŒãžã£ãŒé£ã«ãé¡ãããããšã«ãªãã®ã§ã12æäžæ¬ã«æ¡å
ã1æ19æ¥ã®ãåã§ãã  ð»ãã¡ãã¯æ§ããã¯ããã°ããŒã ïŒçŸæè¡åºå ±ã°ã«ãŒãïŒã®ãã®ã  ðºãããªæãã§Confluenceã«åã°ã«ãŒãã®å
容ããŸãšããŠããã ãã ð»ãããªæãã«è³æã«èœãšã蟌ãã§ãããŸããã  åã°ã«ãŒãã®ã«ã©ãŒãåºãŠããŠãããããã£ãã®ãšãåã°ã«ãŒãã®ãã£ãŠããããšã»ãã£ãŠããããšãç¥ããæ»
å€ã«ãªãæ©äŒã«ãªããŸããïŒ K-1ã°ã©ã³ã㪠äœãšãã£ãŠãä»åã®ç®çäŒç»ã§ããåŒç€Ÿã§ã¯æ¯æãæ¯å±±è³ããšç§°ããŠç¹çãã¹ãæ¡ä»¶ã掻åã衚地ããŠããŸãã ð åèèšäºïŒ å
šç€Ÿå¡ããŒãã£ã³ã°ããã³å
¥ããã話 æ¥åã®æ¯ãè¿ããšæ¥å䟡å€ã®åèªèãããŠéšçœ²ãè¶
ããæ
å ±å
±æãç®çã§ãããããã®å¹ŽåºŠè³çãK-1ã°ã©ã³ããªãšç§°ããŠè¡ãããšã«ãªããŸããã 倧ãŸããªæµãã¯äžå³ã®éãã§ãã æ次è³ã§ã¯ãã¬ãŒã³ã¯è¡ããŸããããä»åã¯å¹ŽåºŠè³ããã¬ãŒã³åãåãããŸãã ã°ã«ãŒãã®æ°ãå€ãããããŸãã¯åã°ã«ãŒãããæ¡ä»¶ããšã³ããªãŒããŠãããããã®äžããåéšä»£è¡šæ¡ä»¶ãã²ãšã€ãã€éžåºããŠããããŸããã ç§ã¯ãã©ãããã©ãŒã éšã®éžèäŒã«è³ããããšããŠåå ãããŠããã ããã®ã§ãããæ®æ®µéãã°ã«ãŒãã§åããŠãã ã¡ã³ããŒãäºãã«ç§°è³ãããå Ž ã«ãªã£ãŠããã®ãå°è±¡çã§ããã ã¢ããŠã³ã¹æãäºéžäŒãåœæ¥ãŸã§éããŠãäŒããç¶ããŠããã®ã¯ãK-1GPã¯å¹ŽåºŠè³ã§ããã決ããŠåªå£ãã€ããããšãç®çã§ã¯ãªããšããããšã§ãã ãã®1幎ãçãããåŸäºããŠããä»äºã¯å
šãŠçŽ æŽããããã®ã§ããããšã¯å€§åæã§ãã K-1GPã®äžçªã®ç®çã¯èªèº«ã®æ¥åãæ¯ãè¿ãããäºãã®ä»äºã称è³ãåãããšã ã£ãã®ã§ãå°ãªããšãç§ã®åå ãããã©ãããã©ãŒã éšã®äºéžäŒã§ã¯ããã® ãäºãã«ç§°è³ãåã姿ã ãèŠãããŠéåžžã«ããããã£ãã§ãã ããããŠäºéžäŒã§éžåºããã代衚æ¡ä»¶ã¯ãããããæ¬éšäŒãŸã§ã®1é±éã§å3åã®ãã¬ãŒã³è³æãæºåããã ãåœæ¥ãè¿ããŸããã éåžžã«ã¿ã€ããªã¹ã±ãžã¥ãŒã«ã§æºåãããã ãããšã«ãªãã代衚è
ã®çããã«ã¯æè¬æè¬ã§ãðââïž éãŸã£ãŠãããã¬ãŒã³è³æã¯ããããåæ§ã«æº¢ããŠããŠãæ¯æ¥æ ŒçŽãããè³æãã¯ã¯ã¯ã¯ããŠåŸ
ã£ãŠããŸãããç¬ ç€Ÿé·ã»å¯ç€Ÿé·ãããã〠2024幎ã®ããã¯ãªããšããããšã§ãå°å¯ºç€Ÿé·ãšæ¯å±±å¯ç€Ÿé·ããã®ããããã€ã倧ããªã³ã³ãã³ãã§ããã æ¯æã®å
šäœããŒãã£ã³ã°çŽæ¥ã話ãèãæ©äŒã¯ãªããç¹ã«å°å¯ºããã«é¢ããŠã¯KINTO/KTCååã®å Žã§ããã話ããã ãããšããªãã£ããããéåžžã«éèŠãªå Žã§ããã æ確ãªãããã¡ãã»ãŒãžãå
šå¡ãèãããšã§åãæ¹åãåããŠä»äºãããããšãã§ããŸããããã°è»žã®ãããªãã®ã§ãã éå¶ã¡ã³ããŒã§äºåã«ãKTCã®ãšã³ãžãã¢ã«ã©ã®ããã«ãªã£ãŠã»ããããã2024幎KTCã«ã©ã®ãããªããšãæ±ãããããããåããããã éã«ã¡ã³ããŒç®ç·ã§ããããã£ãããšããã²çºä¿¡ããã ãããããšããããšããäŒããããããŠå
šäœæ§æããŸãšããŠãããŸããã ã¹ã©ã€ãã¯ããäŒããããããããæãããã¶ã€ããŒè»å£ã¯ãªãšã€ãã£ã宀ã«ãåæ·»ãããã ããŸããã å€åœç±ã¡ã³ããŒã«ã誀解ã®ç¡ããããªèšèãéžãã ããããžã¥ã¢ã«ã§è£å®ãããã  瀟é·ã¡ãã»ãŒãžãããžã¥ã¢ã«å ä»åããšã¿ã®æ°ããããžã§ã³ ã次ã®éãçºæãããã (Inventing our path forward together) ãã¿ã€ãã³ã°è¯ãçºè¡šããããã¡ããæ¹ããŠç€Ÿé·ããã·ã§ã¢ãããŸããã  Inventing our path forward together æèŠªäŒ ããŠããªãã©ã€ã³ã€ãã³ãã®ééå³ãšããã°æ芪äŒã§ãã ä»åã¯äŒå Žæå®ã®ã±ãŒã¿ãªã³ã°ãå©çšãããŠããã ããŸããããããŽå
¥ããã³ããŒã¬ãŒã食ãã€ããããããšãã§ãããšãŠã豪è¯ã«ãªããŸãã âš  ã±ãŒã¿ãªã³ã°ã¯ãã¯ã€ãšã«çšæããæ¬äŒå Žã«ã¯äœã眮ããªãã£ãã®ã§ãã飯ã飲ã¿ç©ãåãã«è¡ãã«ããã£ãã®ã¯åçç¹ã§ãã ããŠãä»åã®ä¹Ÿæ¯ã¯ãé¡éããã«ãŠè¡ããŸããã éå¶ã¡ã³ããŒã¿ããªåããŠã®çé¡éãã ã£ãã®ã§ãäºåã«èª¿ã¹ããšãããããŒã«ã倧ããªã«ãã¿ãŒãå¿
èŠããšåºãŠããŠéåžžã«çŠããŸããã ãããªããšãããªå¿
èŠã®ãªãéåžžã«ãæ軜ãªãªãªãžãã«æšœã KURANDæ§ã®ãµã€ã [^1]ã§çºèŠãããã¡ããæ¡çšã [^1]: KURANDæ§ã¯ãã®ãçžããããåŸæ¥åŒç€Ÿäž»å¬ã®ã€ãã³ã ããœãŒã¹ã³ãŒãã¬ãã¥ãŒããŸã€ã ã«ãåè³ããã ããŸããã  ãã¡ããã¡ããããããªãã§ããïŒïŒ ãã®ãªãªãžãã«ãã¶ã€ã³ã¯ãã¡ããæããã¯ãªãšã€ãã£ã宀ã®ãã¶ã€ã³ã§ã ð¯ 也æ¯åŸã¯åºæ¬ããªãŒã§ã¯ãããŸãããããªããšãã£ãŠã260人èŠæš¡ã§ããæ®æ®µäŒè©±ããªã人ãšãäŒè©±ããŠã»ããã®ãéå¶ã®æ³ãã äœã話ã®ãã£ããã«ã§ãããã®ãæ€èšããŸããã åœåã¯ããŒã åãããŠã²ãŒã ãããïŒãšè©±ããŠããŸãããã倧人æ°ããããã匷å¶åå ããããããªãã...ãšæ©ãã§ãããšããã§éå¶ãèŠã€ããã®ã Rally ã§ããã ã¹ããã§ç°¡åã«ã¹ã¿ã³ãã©ãªãŒãã§ãããµãŒãã¹ã§ããQRãèªã¿èŸŒãã§ã¹ã¿ã³ãã©ãªãŒãã§ããã®ã§ããã®QRãåéšããšã«é
åžããã°äº€æµãã§ããã®ã§ã¯...ïŒïŒå³æ±ºã§ããã ããªãŒãã©ã³ã§ããããããšã«ã¹ã¿ãã€ãºã§ãã1é±éã§ãã£ãããªå®æ床ã®ãã®ãã§ããŸããã ð»Rallyã®äœ¿ãæ¹ã¯ãããªæãã  åä»ã§é
åžããQRã³ãŒãã·ãŒã«ãåèªã®IDã±ãŒã¹ã«è²ŒãããŠããã®ã§ããããèªã¿åã£ãŠã¹ã¿ã³ããéãã圢åŒã§ãã æºåã®æ軜ããšã³ãã¥ãã±ãŒã·ã§ã³ã®ä¿é²ãšããæå³ã§ã¯éåžžã«è¯ãã£ãã§ããéåžžã«è¯ãã£ãã 匷å¶åå ãããããšããªããã¹ã ãŒãºã«éãéšçœ²ã®äººã«å£°ããããã£ãŠã姿ããã¯ãæåçã§ããã  åœæ¥æ²ç€ºãããã¹ã¿ãŒ ããã«ã㣠ããŠãäºåæºåç·šãšããããšã§ããäžã€å¿ããŠã¯ãããªãæºåç©ãããã«ãã£ã§ãã ã¿ã€ããªã¹ã±ãžã¥ãŒã«ã ã£ããããå¿
èŠãªãã®ãæåã«æŽãã ããŠããããã¯ãªãšã€ãã£ã宀ã®çæ§ã«ã¯ããªãç¡çãèšã£ãŠããããã®ãã®ãäœã£ãŠããã ããŸãããã K-1 GPããŽ è¡šåœ°ç¶   ã¹ã©ã€ããã¹ã¿ é¡å²ãçšã®æšœãã¶ã€ã³   IDã«ãŒãã±ãŒã¹(å
šå¡é
åž) ã¹ã¿ããTã·ã£ã   ã¿ã³ãã©ãŒïŒã¹ã¿ã³ãã©ãªãŒæ¯åïŒ ãšã³ããã° (ã¹ã¿ã³ãã©ãªãŒæ¯å)   æ¹ããŠèŠãŠããã©ããªãäœãããããïŒïŒããšããã³ããããªãã¬ãã«ã§ãããç¬ ããã«å ããŠç€Ÿå
ãšã³ãžãã¢ã«ã¯åèªã®åæãèªåã§äœæã§ããããŒã«ãäœæããŠããããŸããã ð»Slackã¢ã€ã³ã³ã»éšçœ²ã»ååã»KTCããŽãå
šå¡åå°åãããŸãã  ããããªã®ãã£ãããããªããšè»œãèšã£ãŠã¿ããã»ããšã«ããã«äœã£ãŠãããŸããã èªç€ŸãªãããKTCã¡ã³ããŒã®ä»äºã®éããšã¯ãªãªãã£ã®é«ãã«ã¯æ¯åºŠé©ããããŸãã æ¬æ¥ãããäžã§ããååããã ããæ¹ã
ã«ãã®å ŽããåãããŠæ¹ããŠæ·±ãæè¬ããŸã ðââïžðââïžðââïž éå¶ããŠã¿ãåŠã³ã»æ¬¡åéå¬ã«åã㊠ããå幎ãçµã¡ãŸããããããããŠãã£ãããšãæžãåºããŠã¿ããšãããæºåãããªãâŠç¬ ä»åã®èšäºå·çã§ãã®ããã¯ãªãäŒããµãè¿ã£ãŠã¿ãŠãæ¹ããŠãçµç¹ã®ããžã§ã³ãç®æšãããããããå
šç€Ÿã«å
±æããããšãããªãã©ã€ã³ã§ããŒã ãã«ãã£ã³ã°ãè¡ãããšãã®éèŠæ§ãèªèããŸããã çµå¶å±€ããçŽæ¥ããžã§ã³ãæŠç¥ãäŒããããã ãã§ããã®èãããã€ã¬ã¯ã·ã§ã³ã«åºã¥ããŠåãæ¹åãåããŠæ¥ã
è·åã«åŸäºããããšãã§ããŸãããŸãããã®èãã«å
±æã§ããã°ã瀟å¡ã®ã¢ãããŒã·ã§ã³ã¢ããã«ãã€ãªãããŸããããããªãã©ã€ã³ã§è¡ãããšã«ããããã®ãã€ã¬ã¯ã·ã§ã³ã¯æµžéãããããªãã瀟å¡ãšçµå¶å±€ãããã«ã¯ç€Ÿå¡å士ã«ãä¿¡é Œé¢ä¿ãçãŸããçåãäžå®ã®è§£æ¶ã«ã圹ç«ã¡ãŸãã ç¹ã«åŒç€Ÿã¯KINTOãµãŒãã¹ã¹ã¿ãŒããã5幎çµã¡ãäŒç€ŸãšããŠã次ã®ã¹ããŒãžã«åããæäžããã®ã¿ã€ãã³ã°ã§ãããã£ãã€ãã³ããè¡ãããšããçµç¹å
šäœã®ãšã³ã²ãŒãžã¡ã³ãåäžããäžäœæã®éžæã«ç¹ããã®ã ãšå®æããŸããâš ãŸãå¥ã®èšäºãªã©ã§å®æœçµæããäŒãã§ãããšæããŸãããåå è
ã®å£°ãšããŠããä»äºãžã®ã¢ãããŒã·ã§ã³ãäžãã£ãããä»ã®ããŒã ãäœãããŠããããèªèã匷ãŸã£ãããçµå¶å±€ã®èããç¥ãããšãã§ããããªã©éåžžã«å¥œæçãªåå¿ãå€ããå®æœããç²æããã£ããªããšæããŸããð ãããã£ãã€ãã³ãã¯ãã²1幎ã«äžåºŠã¯éå¬ãããã次åéå¬ã«åããŠéå¶ã®åŠã³ã掻ãããè³ããªãç¹ã¯åçç¹ãšããŠãããªãæ¹åãç®æããŸãðª æ°ã¥ãã°7000æå以äžãæžããŠããŸããŸããããããã ãæãå
¥ãã®ãã£ãã€ãã³ãã ã£ããšããããšã§ãã æåŸãŸã§èªãã§ããã ãããããšãããããŸãïŒKINTOãã¯ãããžãŒãºã§ã¯ä»åŸã瀟å
å€æ§ã
ãªã€ãã³ããèšç»äžã§ãïŒ ç€Ÿå€åãã€ãã³ã㯠åŒç€ŸConnpass ã«ãŠéæåéããŸãã®ã§ããèå³ããã°ãã²ãåå ãã ãã ð
Hello Hi there, my name is Murayama, and I work as an assistant at the CIO office at KINTO Technologies. This article will introduce our employees' office and desk setups in a relaxed manner (ËÏË) Introduction to Our Offices This is our head office in Nagoya. President Kotera-sanâs strong vision is reflected in the interior, emphasizing natural elements and brightness. The fire pit you can see in the bottom right picture -which is Kotera-san's particular point of focus-, is lit during certain times. It's located in the center of the office, where everyone gathers to have lunch together! The second location is the Muromachi office. Our Muromachi office located in Tokyo has two floors. It also has this area we call âthe Junctionâ. It's a very elegant spot, also used for video and photoshoots! It's conveniently located near many shops since it's housed inside of the COREDO Muromachi 2 building. In this area, you can find whatever you want to eat! The third location is the Jimbocho office. I saw the Platform Group gathered in the big conference room so I took a picture of them. The Jimbocho office is popular because it has the largest number of conference rooms. This area offers affordable lunch options, especially there are a lot of delicious curry restaurants! I always have curry whenever I visit ð The photo in the bottom right corner is a vending machine with the KINTO Technologies logo at this office. The fourth site is the Osaka Tech Lab. Not âofficeâ, but âTech Labâ! (This is important) It opened in April and has still few employees, but everyone there shares their opinions to improve it. The rooftop in the bottom right part of this photo is wide and popular. Lunch is also cheap around Shinsaibashi! Plus, Osaka's batter-based dishes are delicious! Although I'm from Kanto, so Iâm not used to okonomiyaki set meals for lunch... Introduction to Our Desk Setups Each person personalizes their seat to work comfortably. Functional desks reflect having a good setup, Iâm sure, but I donât think its only about functionality. This is mine. I have a big cheering squad. It's a great desk setup, right?! Our vice president Kageyama-san also has some on his desk. Every once in a while, one of them rolls off somewhere and I find it heartwarming and funny to see Kageyama-san search for it. It's inevitable when you hold a Sylvanian Families figurine in your hands, it brings out your nurturing instincts. Before I make this blog all about Sylvanian Families, let's move on to the next desk around here.  Cool keyboard! She enjoys building her own PCs and Gunpla. Great hobby! In her home desk setup, she has many Gunplas watching her. She seems to have also brought a small one into the office today. I gave her a Sylvania so she has even more friends now. By now, I'm one of the Sylvanian Families evangelists in office!  I'm sharing all this informally, but please know that I also perform well at my job. Thereâs an e-sports club in the KINTO Technologies community, and we all played Splatoon together the other day. As I work at an IT company, I naturally (I guess?) love games as well. The recent trend in the company is playing Mahjong!  Se says she wants Doraemon's Anywhere Door and I can relate. I wish I could easily travel back and forth between the different offices... But setting wishes aside, whenever I am needed, I travel to the other offices too. Each office has its own good points and I enjoy working in all of them!  There are many people here who like books and the company has a system to lend them but It's also common to see employees lending books to each other. Also, I learned about Slack after joining KINTO Technologies. It's a wonderful application filled with cute emoji's and it allows us to communicate with each other in a nice and informal way!  This setup is super engineer-like, with its double display!! It's a wonderful desk with both functional aspects and modest comfort. By now, you should understand that Sylvanian Families are universally appealing, right? Finally Remote work is popular these days, but I think it is best to go to office and work with everyone face to face in an atmosphere that you enjoy (ËÏË) On top of that, you are free to change your hair color, clothes, and desk setup, allowing you to work in a comfortable environment, which makes it more enjoyable! Thank you for reading till the end!