You plan to meet with the Enterprise Architecture team to discuss the architectural landscape at Front Stage and how the event-booking application fits into that landscape. You cover the following topics:
- Application access
- Application server technology
- Integration and web services
- Data storage and warehousing
Front Stage plans to offer prospective customers the ability to initiate a quote from the Front Stage cloud-based web portal. Front Stage wants to allow event attendees to get basic event information from a chat interaction. New sales prospects can create new Event Booking requests through social channels. Sales executives also have access to a mobile application to track all open event bookings to follow up with the prospect. This booking event details need to be available offline since sales executives travel frequently. Front Stage uses an open-source SAML single sign-on (SSO) package for user access to all applications.
Application server technology
Front Stage deploys an enterprise archive on its application servers for all web applications. In the past, Front Stage used container-managed transactions with an MDB listener to ensure messages entering the booking application from external sources are retried if not successful. In the future, with new ways of initiating booking cases from offline mobile and social channels, the use of an MDB may no longer be necessary.
Integration and web services
Front Stage provides access to REST services to gather weather reports and traffic reports. The weather report request/response is in JSON format. The traffic report uses XML. Front Stage protects all customer contact and payment information through secure services.
Data storage and reporting
Front Stage uses a data warehouse to store and report historical event information such as hotel bookings and parking records. The new booking application feeds the warehouse for executive reporting. Warehouse reports are available from the Pega application.
Produce a high-level architecture diagram and describe each application component. Use Visio, PowerPoint, Image, or hand-draw your diagram. Assume an on-premises deployment.
In the diagram, illustrate the:
- Components that are in Front Stage's virtual private network (VPN) and which are external to the network
- Components of the application, including web services and the components of the Booking application
- Relationship of booking application architectural components
As the alternative solution, describe any differences in design choices for the same set of Pega Cloud requirements.
1 Identify design options
Any options allowed by the Pega Platform™ support guide are valid. For more information, see the Platform Support Guide.
2 Consider alternative approaches
If the application is deployed on Pega Cloud™ instead of on-premise, you must also consider:
- Pega Cloud services networking – Work with the Pega Cloud team to configure the application to access secured Front Stage resources.
- Integrating Pega applications in Pega Cloud with external systems – Review options available in Pega Cloud.
- Pega Cloud Security Overview – Examples include whitelisting and data residency.
- Business Intelligence Exchange (BIX) for Pega Cloud applications – Pega Cloud uses a separate node for BIX processing.