Podcast
Questions and Answers
What key characteristic defines how services communicate within a Service-Oriented Architecture (SOA)?
What key characteristic defines how services communicate within a Service-Oriented Architecture (SOA)?
- Direct memory access
- Shared database connections
- Standardized interface (correct)
- Proprietary protocols
In a layered SOA, what is the role of the 'Wrapper Services Layer'?
In a layered SOA, what is the role of the 'Wrapper Services Layer'?
- To manage security and access controls
- To implement complex business logic
- To directly expose database tables to consumers
- To expose functionalities of existing IT systems as services (correct)
Why is it considered beneficial for microservices to be 'loosely coupled'?
Why is it considered beneficial for microservices to be 'loosely coupled'?
- To reduce network latency
- To simplify inter-service communication
- To allow independent development and deployment (correct)
- To maximize resource utilization on shared servers
In the context of microservices, what does 'atomic' typically imply?
In the context of microservices, what does 'atomic' typically imply?
What is the primary function of an Enterprise Service Bus (ESB) in a SOA?
What is the primary function of an Enterprise Service Bus (ESB) in a SOA?
Which layer in a typical SOA is responsible for providing interfaces for user interaction?
Which layer in a typical SOA is responsible for providing interfaces for user interaction?
How does implementing a business process as a composite microservice relate to reusability?
How does implementing a business process as a composite microservice relate to reusability?
What is a key benefit of using microservices related to continuous integration and continuous deployment (CI/CD)?
What is a key benefit of using microservices related to continuous integration and continuous deployment (CI/CD)?
Which of the following is a characteristic of a composite microservice?
Which of the following is a characteristic of a composite microservice?
What distinguishes a business process layer from other layers in a Service-Oriented Architecture?
What distinguishes a business process layer from other layers in a Service-Oriented Architecture?
Which of the following is NOT a typical responsibility of the atomic microservice?
Which of the following is NOT a typical responsibility of the atomic microservice?
What role do container management systems like Docker Compose and Kubernetes play in microservices architectures?
What role do container management systems like Docker Compose and Kubernetes play in microservices architectures?
In a microservice architecture, what is the purpose of an API Gateway?
In a microservice architecture, what is the purpose of an API Gateway?
What impact do standards-based interfaces have on the interaction between microservices?
What impact do standards-based interfaces have on the interaction between microservices?
Which of the following is a typical characteristic of a 'wrapper service'?
Which of the following is a typical characteristic of a 'wrapper service'?
Flashcards
Service Definition
Service Definition
A unit providing one or more functionalities to support business needs, accessible over a network through a standard interface, independent of programming languages and platforms.
Service-Oriented Architecture
Service-Oriented Architecture
Turning all IT systems into services for flexibility.
Microservice
Microservice
Small, independent service providing limited functionalities to support business needs.
Atomic Microservice
Atomic Microservice
Signup and view all the flashcards
Composite Microservice
Composite Microservice
Signup and view all the flashcards
Wrapper service
Wrapper service
Signup and view all the flashcards
Layers in SOA
Layers in SOA
Signup and view all the flashcards
Benefits of Microservices
Benefits of Microservices
Signup and view all the flashcards
Microservice benefits
Microservice benefits
Signup and view all the flashcards
Business Process Layer definition
Business Process Layer definition
Signup and view all the flashcards
Atomic Microservice Layer
Atomic Microservice Layer
Signup and view all the flashcards
Wrapper Service Layer
Wrapper Service Layer
Signup and view all the flashcards
Study Notes
Layers of a Service-Oriented Architecture
- This module explains the concept of atomic/simple and composite/complex microservices
- To illustrate sample layers in a Service- Oriented Architecture (SOA)
- To describe where microservices reside within an SOA layered architecture
- Understand the benefits of a layered SOA for developing enterprise solutions
Definition of a Service in the Software World
- A service provides multiple functionalities needed to support business requirements
- Services are utilized by other applications or services over the network via a standard interface
- Standard interfaces are independent of programming languages and platforms
- The Service Provider Interface and the Service Consumer Interface refer to code at the provider and consumer end
- These interfaces enable data exchange between the provider and the consumer
Service-Oriented Architecture
- Consider turning all IT systems into services
- Services can be small, simple, large, or complex
- Develop and maintain enterprise solutions as assemblies of loosely-coupled services
- Assemblies are managed at layers by either functionality or complexity
Microservices and MSA
- A microservice is a service that can be independently developed and deployed
- Has one or few functionalities needed to support business needs
- Enterprise solutions consisting of assemblies of loosely-coupled microservices can be developed and maintained
- Provides all functionalities as microservices, where microservices are relatively small and simple
Types of (Micro)Services
- Atomic (Micro)Service (a.k.a. Simple (Micro)Service) implies single implementation
- Atomic microservices are independent of other microservices/applications within an enterprise context, except commonly used applications
- An atomic microservice is simple by providing limited functionality related to one kind of entity, where operations are simple CRUD of the data entities
- Wrapper Service mainly exposes functionalities of another application, such as a legacy system
- Composite (Micro) Service (a.k.a. Complex (Micro)Service) implies implementation of the expected functionalities by composing a sequence of services/applications according to a business process
- Inter-process communication (IPC) technologies will often implement composition
- A composite process (micro) service is is used to implement a business process involving more than one kind of data entities
Microservice Attributes
| Attribute | Atomic/Simple | Composite/Complex |
|---|---|---|
| Independently Deployable | Yes | Yes |
| Independently Scalable | Yes | Yes |
| Language | Yes | Yes |
| Encapsulates | single "atomic" entity (e.g., Customer, Product) | single process (orchestrates atomic/composite (micro)services) |
| Naming Convention | Noun such as book, order, shipping_record | Verb such as Place order, Process shipping |
| Can Invoke Other Services | Never | Yes, it's their main purpose |
Sample SOA Layers & Support Infrastructure for an Enterprise
- User Interface Layer(s) provides the interfaces for interactive activities and can trigger a business process
- Business Process Layer(s) can be long-running involving user interactions or straight-through
- The Business process can be implemented as a (micro)service, usually composite
- Composite (Micro) Services Layer(s) can directly communicate to other (micro) services and not IT systems or monoliths
- An Atomic Microservices Layer(s) communicates with another atomic (micro)services
- Wrapper Services Layer(s) expose a functionality of an IT system or a monolith or an external system and/service
- IT Systems Layer(s) Applications (COTS, Custom or Legacy) providing functionalities that are NOT microservices
- The API Gateways is managing accesses to microservices, usually for external service consumers
- The Business Process Management Software Suites (BPMS) manages designs, modeling, analysis, implementation, execution & monitoring etc.
- Enterprise Service Buses is managing accesses to microservices of internal uses in an enterprise, while Communication Technologies uses message brokers and HTTP servers
- Container Management involves deploying and managing containers with tools like Docker
Benefits of Microservices and SOA Layers
- Enforces a high degree of modularity and help to manage complexity in large enterprise solutions
- Wrapper services have direct dependency on (monolithic) applications, making them modular than atomic microservices
- (Micro)services interact with each other through standards-based interfaces based on programming languages or platforms
- Common errors may be handled in a standard way
- It is easier to change a (micro) service than change a monolith and support continuous integration and deployment (CI/CD) for changing business requirements
Studying That Suits You
Use AI to generate personalized quizzes and flashcards to suit your learning preferences.
