25 Questions
True or false: In teleprocessing architecture, all processing is performed within the boundaries of the same physical computer.
True
True or false: The file server in a file-server architecture holds the applications and the DBMS.
False
True or false: In file-server architecture, the processing is distributed about the network, typically a wide area network (WAN).
False
True or false: In teleprocessing architecture, the central computer had to carry out a significant amount of work on behalf of the terminals.
True
Multi-tier architecture can only be split into web server tiers
False
JEE application servers handle transactions, security, scalability, and management
True
.NET Framework is Oracle's offering for middle-tier development
False
Message-oriented middleware (MOM) supports synchronous calls between client and server applications
False
Client–server architecture requires a full copy of DBMS on each workstation.
False
N-tier architectures provide less flexibility and scalability compared to three-tier architecture.
False
Traditional two-tier client–server architecture was addressed by three-tier design in 1995 for enterprise scalability.
True
Three-tier architecture eliminates concerns of software distribution in traditional two-tier client–server model.
True
ORBIX is an open-source middleware product.
False
SQL-oriented data access middleware translates SQL requests to database-specific languages.
True
Transaction Processing Monitors (TP Monitors) do not provide load balancing and funneling.
False
Web services always have a user interface for interacting with users.
False
RESTful Web services emphasize moving away from SOAP-based services towards Representational State Transfer (REST) based communications
True
SOA architecture typically involves three processes: Service Scheduling, Order Processing, and Account Management, each accessing a number of databases
True
Amazon S3 charges are based on a 'pay-as-you-go' policy, currently $0.125 per GB for the first 50TB/month of storage used
True
REST services do not require XML, SOAP, WSDL, or UDDI definitions, and are based on an architectural style that specifies constraints for desirable properties
True
Amazon S3 charges are currently $0.125 per GB for the first 50TB/month of storage used
True
RESTful Web services emphasize moving away from SOAP-based services towards Representational State Transfer (REST) based communications
True
Service-Oriented Architectures (SOA) typically involve three processes: Service Scheduling, Order Processing, and Account Management, each accessing a number of databases
False
REST architecture style adopts a client-server architecture and uses a stateful communication protocol
False
Common SOA principles include tight coupling, reusability, and adherence to a communications contract defining information exchange and service description information
False
Study Notes
Web Services, REST, and Service-Oriented Architectures
- Web services examples include Microsoft Bing Maps, Google Maps, Amazon Simple Storage Service (Amazon S3), Geonames, DOTS Web services, and Xignite
- Amazon S3 charges are based on a "pay-as-you-go" policy, currently $0.125 per GB for the first 50TB/month of storage used
- Key technologies and standards in Web services include XML, SOAP (Simple Object Access Protocol), WSDL (Web Services Description Language), and UDDI (Universal Discovery, Description, and Integration)
- RESTful Web services emphasize moving away from SOAP-based services towards Representational State Transfer (REST) based communications
- REST services do not require XML, SOAP, WSDL, or UDDI definitions, and are based on an architectural style that specifies constraints for desirable properties
- REST architecture style adopts a client-server architecture, uses a stateless communication protocol, and exchanges representations of resources using a standardized interface and protocol
- Service-Oriented Architectures (SOA) is a business-centric software architecture for building applications that implement business processes as sets of services published at a granularity relevant to the service consumer
- SOA emphasizes flexibility and reusability as key requirements for businesses in a rapidly changing technological landscape
- SOA architecture typically involves three processes: Service Scheduling, Order Processing, and Account Management, each accessing a number of databases
- SOA aims to design loosely coupled and autonomous services that can be combined to provide flexible composite business processes and applications
- Common SOA principles include loose coupling, reusability, and adherence to a communications contract defining information exchange and service description information
- SOA design approach focuses on building Web services for SOA with an emphasis on loose coupling, reusability, and adherence to communication contracts.
Web Services, REST, and Service-Oriented Architectures
- Web services examples include Microsoft Bing Maps, Google Maps, Amazon Simple Storage Service (Amazon S3), Geonames, DOTS Web services, and Xignite
- Amazon S3 charges are based on a "pay-as-you-go" policy, currently $0.125 per GB for the first 50TB/month of storage used
- Key technologies and standards in Web services include XML, SOAP (Simple Object Access Protocol), WSDL (Web Services Description Language), and UDDI (Universal Discovery, Description, and Integration)
- RESTful Web services emphasize moving away from SOAP-based services towards Representational State Transfer (REST) based communications
- REST services do not require XML, SOAP, WSDL, or UDDI definitions, and are based on an architectural style that specifies constraints for desirable properties
- REST architecture style adopts a client-server architecture, uses a stateless communication protocol, and exchanges representations of resources using a standardized interface and protocol
- Service-Oriented Architectures (SOA) is a business-centric software architecture for building applications that implement business processes as sets of services published at a granularity relevant to the service consumer
- SOA emphasizes flexibility and reusability as key requirements for businesses in a rapidly changing technological landscape
- SOA architecture typically involves three processes: Service Scheduling, Order Processing, and Account Management, each accessing a number of databases
- SOA aims to design loosely coupled and autonomous services that can be combined to provide flexible composite business processes and applications
- Common SOA principles include loose coupling, reusability, and adherence to a communications contract defining information exchange and service description information
- SOA design approach focuses on building Web services for SOA with an emphasis on loose coupling, reusability, and adherence to communication contracts.
Test your knowledge of multi-tier architecture, load balancing, and multi-user DBMS architectures with this quiz. Learn about dividing the architecture into web server and application server tiers, implementing web farms for efficient load balancing, and the role of application servers in hosting API for business logic.
Make Your Own Quizzes and Flashcards
Convert your notes into interactive study material.
Get started for free
