マイクロサービス時代の認証と認可 - AWS Dev Day Tokyo 2018 #AWSDevDay都元ダイスケ Miyamoto
マイクロサービスが話題を集め、コンポーネントの急速な API 化が進んでいます。
認証や認可は、主にエンドユーザとシステムの間の問題だと認識されますが、今やコンポーネント間のサービス呼び出しにおいても重要な役割を担っています。
複雑に入り組んだマイクロサービス間の認証と認可について、実際に開発している API プラットフォームの実例を元に、実践的な知見をお伝えします。
マイクロサービス時代の認証と認可 - 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.
The code gets the dialect from a database model, then uses the dialect to create SQL for dropping and altering tables in a schema based on the model and other parameters.
The document reads in a file using a FileInputStream, deserializes it using a serializer, creates an instance of a Porter class, sets a parameter on the porter, executes it on the deserialized model, gets the SQL dialect from the model, generates SQL based on the dialect to drop/insert data, and writes the SQL to a file stream.
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.
The code gets the dialect from a database model, then uses the dialect to create SQL for dropping and altering tables in a schema based on the model and other parameters.
The document reads in a file using a FileInputStream, deserializes it using a serializer, creates an instance of a Porter class, sets a parameter on the porter, executes it on the deserialized model, gets the SQL dialect from the model, generates SQL based on the dialect to drop/insert data, and writes the SQL to a file stream.