"AWS OpsWorks helps you deploy and operate applications of all shapes and sizes. With AWS OpsWorks, you can model your application stack with layers that define the building blocks of your application: load balancers, application servers, databases, etc. But did you know that you can also use AWS OpsWorks to run commands or scripts on your instances? Whether you need to perform a specific task or install a new software package, AWS OpsWorks gives you the tools to install and configure your instances consistently and help them evolve in an automated and predictable fashion.
In this session, we dive into how you can create custom layers and a runtime system for your operational tooling, understand the lifecycle events, and show how to develop and test locally."
This document provides an overview of MQTT (MQ Telemetry Transport), a publish-subscribe based "light weight" messaging protocol that is well suited for mobile and IoT applications. Some key points:
- MQTT was designed for connections with remote locations where bandwidth and battery power are limited, such as with mobile apps and sensor devices.
- It uses a small amount of bandwidth compared to traditional HTTP, and allows for bi-directional communication between clients and servers using publish/subscribe messaging.
- Features include support for different qualities of service, last will and testament messages, and lightweight implementation on constrained devices.
- MQTT has been used successfully in large scale mobile apps like Facebook Messenger due to its
マイクロサービス時代の認証と認可 - AWS Dev Day Tokyo 2018 #AWSDevDay都元ダイスケ Miyamoto
?
マイクロサービスが話題を集め、コンポーネントの急速な API 化が進んでいます。
認証や認可は、主にエンドユーザとシステムの間の問題だと認識されますが、今やコンポーネント間のサービス呼び出しにおいても重要な役割を担っています。
複雑に入り組んだマイクロサービス間の認証と認可について、実際に開発している API プラットフォームの実例を元に、実践的な知見をお伝えします。
This document discusses the strategy design pattern. It explains that the strategy pattern allows an algorithm to be selected at runtime based on context. It provides examples of using strategies to sort files differently based on a parameter, and to implement different versions of FizzBuzz using the same client code. The strategy interface and classes demonstrate deferring an algorithm implementation to child classes.
This document provides an overview of domain-driven design (DDD) patterns and principles including:
1. It discusses common DDD patterns such as entities, value objects, aggregates, factories, repositories and services.
2. It explains the differences between entities and value objects and how they are used in a domain model.
3. It covers key DDD concepts like modeling the domain, isolating the domain layer, object life cycles and working with aggregates.
The document discusses a developers summit for the Jiemamy project. It covers several topics related to Jiemamy including the smart build, version control, and model features. It also demonstrates the Jiemamy API and discusses the project's evolution and upcoming version 1.0 release.
DB met with Jiemamy to discuss the Jiemamy project. Jiemamy is an open-source modeling tool that aims to help with database design and development using a DRY approach. It allows modeling the database structure using XML and then generating Java code, SQL scripts, and documentation. DB demonstrated some of Jiemamy's features like the API, model import/export, and discussed plans to improve it and make it more widely available as an open-source project.
This document summarizes a presentation given at the Seasar Conference 2009 Spring. The presentation discussed Jiemamy, an open source project for evolutionary database design. It covered Jiemamy's smart build, version control, and model features. A demo showed how Jiemamy can import and export database schemas to and from XML, Java objects, and SQL. The document also mentioned Jiemamy's Maven plugin and API documentation.
The document discusses different ways to implement a converter class that interacts with business logic code. It mentions creating a StringBuilder and appending a string. It also shows creating a database table with columns for ID, username, and password. The main point is that the business logic interacts with a converter interface, and different implementations of the converter interface can be used depending on the needs, such as an original converter class or an Oracle converter class.
13. Not reproducible
? DBは別途、このSQLを流してください
CREATE TABLE T_GROUP (
ID integer NOT NULL,
NAME varchar(32) NOT NULL DEFAULT 'default group',
STATUS integer NOT NULL,
CREATED_DATE DATE DEFAULT now(),
UPDATED_DATE DATE DEFAULT now(),
DELETED_DATE DATE,
PRIMARY KEY (ID)
);
CREATE TABLE T_USER (
ID integer NOT NULL,
NAME varchar(32) NOT NULL DEFAULT 'default user',
STATUS integer NOT NULL,
CREATED_DATE DATE DEFAULT now(),
(...略...) #cmdevio