InfoQ ホームページ 設計/アーキテクチャ に関するすべてのコンテンツ
-
モノリス対マイクロサービスという誤った二分法
AWSがマイクロサービスを捨ててモノリスに戻ったという最近のブログ投稿で、モノリス対マイクロサービスの古い戦争が再燃している。 あなたの立場は? マイクロサービス派かモノリス派か? マイクロサービス対モノリスは、より大きなストーリーの一部に過ぎず、その区別は幻想のようなもので、人々は虚構の上で争っているのだと言ったらどうだろう。
-
APIデザインレビューは死んだ。APIデザインレビュー万歳!
To design APIs at scale, it takes deliberate effort to create consistency and make several discrete APIs feel like a platform. This requires an efficient and useful API design review process.
-
Amazon DynamoDBで大規模な分散トランザクションを実現
Amazon DynamoDB supports transactions without sacrificing performance or availability. Akshat Vig explains how DynamoDB introduced TransactGetItems and TransactWriteItems for atomic operations, proving full ACID support in distributed transactions.
-
データ転送オブジェクトを超えてJavaレコードを探る
Records are a concise and easy-to-use syntax for creating immutable classes. By using Records, you can ensure that your APIs are bulletproof and less prone to errors. Additionally, Records can be applied with Domain-Driven Design (DDD) principles to create more robust and maintainable code. Learning to use Records and apply them with DDD can help you make more resilient and scalable applications.
-
NetflixにおけるFederated GraphQLプラットフォームの進化
This article describes the journey of the migration towards a Federated GraphQL architecture. Specifically, it shows the GraphQL platform Netflix has built consisting of the Domain Graph Services framework for implementing GraphQL services in Java using Spring Boot and graphql-java, and tools for schema development. It also describes how the ecosystem has evolved at various stages of adoption.
-
DevOpsとクラウドのInfoQトレンドレポート - 2023年7月
InfoQ editorial staff and friends of InfoQ are discussing the current trends in the domain of cloud and DevOps as part of the process of creating our annual trends report. These reports provide InfoQ readers with a high-level overview of the topics to pay attention to and help the editorial team focus on innovative technologies.
-
アーキテクチャ決定のためのシンプルなフレームワーク
This article describes a framework for making architectural decisions using three building blocks: The company's own Technology Radar; Technology Standards; and Architecture Decision Records (ADRs). The framework clarifies decision-making, team involvement, and information on already made decisions and aligns with the company's needs and culture.
-
メディエーター・トポロジーによるイベント駆動型アーキテクチャの事例
This article tells the story about a business case using Event-Driven Architecture with Mediator topology and an implementation that provided elastic scalability, reliability, and durable workflows. All were built using Kubernetes, KEDA, AWS, and .NET technologies.
-
ソフトウェア・アーキテクチャとデザインのInfoQトレンドレポート - 2023年4月
Daprのようなフレームワークがクラウドネイティブの抽象化モデルに焦点を当て、アーキテクトがビジネスロジックを実装の詳細から切り離せるようにするため、移植性を考慮したデザインが採用されつつある。
-
効果的なリモートワークを可能にする - チーム・トポロジーからの原則とパターン
This article shares ideas, principles, and practices from Team Topologies (and related topics) to help organizations approach their structures' design and evolution to better support interactions in remote working. It also shares examples to showcase their impact when used to better approach organizational design, in general, and particularly to support remote working.
-
CloudflareにおけるKafkaの話 ~ メッセージ1兆件に至るまでに学んだ教訓
Cloudflare uses Kafka clusters to decouple microservices and communicate the creation, change or deletion of various resources via protobuf, a common data format in a fault-tolerant manner. The authors suggest investing in metrics for problem detection, prioritizing clear SDK documentation, and balancing flexibility and simplicity for standardized pipelines.
-
静かなるプラットフォーム革命 ~ クラウドネイティブ・プラットフォームを根底から変革するeBPF
There is a silent eBPF revolution reshaping platforms and the cloud-native world in its image, and this is its story.