During a design review for a new enterprise-wide service inventory, an architect proposes a data model that strictly enforces a canonical format for all business entities. Another architect argues this approach will create excessive transformation logic for services that use domain-specific variations of these entities. Which two service-orientation principles are most directly in tension in this scenario? (Select TWO)
A financial services company is building a loan origination process as a service composition. The process involves a credit check service, an underwriting service, and a funding service. To ensure data consistency, the entire process must be atomic; if the funding service fails, the credit check and underwriting actions must be rolled back. However, the credit check service is a third-party API that does not support two-phase commit (2PC) transactions. Which design pattern is most appropriate for managing this long-running, distributed transaction?
An architect is designing a service that retrieves customer profiles. The initial design exposes a rich data model directly from the underlying CRM database. A senior architect flags this as a violation of the Service Abstraction principle, specifically citing that it leaks implementation details. Which meta abstraction type is primarily being violated by exposing the raw database model?
True or False: The application of the Service Discoverability principle is solely concerned with publishing a service's technical endpoint (WSDL or OpenAPI specification) to a central registry.
A logistics company needs to provide a real-time package tracking service to its partners. The underlying system is a legacy mainframe application that processes data in batches every 15 minutes. Direct, real-time queries to the mainframe are not possible. The company wants to expose a modern, stateless REST API for tracking. Which combination of design patterns is the best approach to bridge this gap?
An organization has successfully implemented several autonomous, reusable services. However, business analysts are struggling to create new processes because they don't have a clear, consolidated view of the available business capabilities. The service contracts are highly technical and spread across different repositories. Which design principle has been inadequately applied, leading to this problem?
A sub-controller service capability is distinct from a regular service capability primarily because it is designed to be both a service consumer and a composable part of a larger service composition. It encapsulates a specific, reusable piece of composition logic. Which of the following is the BEST example of a sub-controller's function?
A development team is building a set of microservices that will be deployed in containers managed by Kubernetes. To handle cross-cutting concerns like logging, monitoring, and security, the lead architect suggests using a pattern where these functions are implemented in a separate, attached container within the same pod. Which pattern is being described?
A retail company is migrating its monolithic e-commerce platform to a microservices architecture. They need a centralized way to handle requests from various clients (web, mobile, partner APIs), providing routing, authentication, and protocol translation. Different clients may require different data compositions from the backend services. Which architectural pattern should be implemented at the edge of the system to fulfill these requirements?
**Case Study:** **Company Background:** GlobalExpress Logistics (GEL) is a large shipping company with a mix of modern and legacy IT systems. Their core shipment processing is handled by a 20-year-old mainframe system that is reliable but difficult to integrate with. GEL wants to provide a new 'Premium Partner Portal' that allows key corporate clients to integrate their own systems directly with GEL's for creating shipments, getting quotes, and tracking packages. **Current Situation:** The mainframe exposes its functionality via a proprietary socket-based protocol and processes requests in a stateful manner, requiring a persistent connection for each partner session. The data formats are based on fixed-width text files. GEL's internal development teams have some experience with REST and SOAP but not with the mainframe's protocol. The business demands that the new partner portal be highly available and scalable, and that new partners can be onboarded within days, not months. **Requirements:** 1. Expose GEL's shipping capabilities via standardized, stateless web services (REST/JSON is preferred). 2. Decouple the partner-facing services from the mainframe's proprietary protocol and stateful nature. 3. Ensure the solution does not require any modification to the existing mainframe application code. 4. Provide a consistent data contract (a canonical model) for all partners, regardless of the mainframe's internal data formats. Which architectural approach best meets all of GEL's requirements?