The document discusses the importance of a Single Source of Truth (SSOT) for efficient infrastructure operation at DMM.com, highlighting past struggles with scattered data and duplication. It outlines the transition to managing comprehensive information through a unified system called Airone, enabling better data structure, access control, and streamlined operations. Key aspects include overcoming past hardships, ideal information management, and future application use cases for infrastructure deployment.
The document describes different versions of a system that provides authentication for users to access multiple services. Version 2.x allowed a single user "ST2" to access Services A and B. Version 3.0 introduced individual authentication for each service, so attempts by User B to access Services outside their authorization were denied. The document provides example logs of users authenticating and accessing services under different versions of the system.
The document describes an automated workflow system. The system allows users to create workflows by connecting triggers to actions through a graphical user interface. Triggers can come from sensors, other systems, or rules, and initiate checks that dispatch tasks to downstream systems or services. The system provides monitoring, auditing, and reporting to give users visibility into workflow executions and their outcomes.
This document discusses message queues (MQ) and their use for microservices. It defines MQ as a mechanism that supports asynchronous message passing between application processes. The key benefits of using MQ for microservices are that it allows for high availability, scalability, and handling new/stopped services. The document compares different MQ protocols and implementations like AMQP, MQTT, Kafka, and ZeroMQ. It provides examples of how companies like Yahoo Japan, IBM and OpenStack use MQ. Performance-oriented MQs like NewtMQ and NATS are also discussed. The conclusion is that NATS is better for microservices if its restrictions can be permitted, but the best choice depends on the specific application requirements.
The document discusses different types of message-oriented middleware (MOM) technologies. It provides an overview of common MOM protocols including AMQP, MQTT, STOMP, and Kafka. For each protocol, it describes features such as message delivery guarantees, pub/sub capabilities, and performance characteristics regarding traffic and CPU usage.