Architectural Decisions - CSCI-360-2023/smh GitHub Wiki

Technical Memo: Recovery from remote service failure

Solution Summary: Automate the reestablishment of connectivity to remote services within 1 minute of their detected unavailability, utilizing local client-side simplified services during the downtown.

Factors

  • Robust recovery from remote service failure
  • Robuse recovery from remote database failure

Solution

In order to achieve optimal service with failure there needs to be backup service available. Instead of storing data in a MySQL database solely, the college should consider storing customer and event data within a cloud-based system that allows for accessibility from multiple zones and regions. If one data center fails, then another should be accessible for the system. It is also important to not only rely on local-client server sides but to make sure the current systems are optimal enough to support the use of many users at once.

Motivation

The college wants to ensure minimal downtime and a seamless experience for users during remote service failures. Local client-side services act as a temporary workaround to maintain critical functionality.

Unresolved Issues

None are identified.

Alternatives Considered

The different tiers of service agreements, based off of cloud-based or connectivity services selected. Each tier improves reliability and efficiency, but some might be too costly.

Technical Memo: Adaptability of other services into the system

Solution Summary: Facilitate easy integration of new third-party systems via both front-end and back-end development, with plans to implement a more user-friendly system for administrators in the future.

Factors

  • Integration of new third-party systems should be almost immediate via front-end or back-end development.

Solution

There should be a self automating system that allows for administrators to log onto an admin website to input new events and ticket prices. Once input and submitted, the ticketing system page should update promptly with the new events and their varying factors that come with it.

Motivation

Enable quick and flexible integration of diverse third-party services. Plan for future scalability with an administrator-friendly input system.

Unresolved Issues

Specify details for the administrator-friendly input system.

Alternatives Considered

No alternatives are considered.

Technical Memo: Legal tax rule compliance

Solution Summary: Purchase a tax calculator component.

Factors

  • Current taxes must be applied

Solution

Government, state, and local tax authorities and regulations are consistently changing. These occurances happen as often as weekly, biweekly, and/or monthly. In order to keep up with these regulatory changes the college should consider purchasing a tax calculator that changes according to the laws and regulations at any given time.

Motivation

Ensure legal compliance and transparent user experience during ticket purchases. Plan for a phased implementation of tax rules to coincide with the system’s public release.

Unresolved Issues

There are no identified unresolved issues.

Alternatives Considered

No alternatives are considered