Architecture Concerns

Architecture relies on a monolithic approach atop Oracle platform (database), what in one hand side can bring the best performance, in general; in another hand, can become complex and expensive to scale.  

By leveraging microservice architecture in a cloud native platform, scalability can be achieved more effectively

By leveraging microservice and event-driven architecture in a cloud native platform, scalability can be achieved more effectively

Since the architecture is based on a monolithic approach atop Oracle platform (database), mostly the Cost Efficiency should take into account the licensing model of Oracle. What can become not efficient if, for instance, the most demanding compute power feature is not the most relevant overall.  

By leveraging SaaS components in the most of infrastructure, the Cost Efficiency can achieved more effectively - fine-tuning each application context capacity given the specific demand on it.   

By leveraging SaaS components in the most of infrastructure, the Cost Efficiency can achieved more effectively - fine-tuning each application context capacity given the specific demand on it.   

By leveraging SaaS components in the most of infrastructure, the highest degree of deployability can be achieved at platform level via Infrastructure as Code (IaC), across multiple zones and in a well defined capacity.  

By leveraging SaaS components in the most of infrastructure, the highest degree of deployability can be achieved at platform level via Infrastructure as Code (IaC), across multiple zones and in a well defined capacity.  

Since the solution operates mainly in SaaS mode, some concerns from procurement and regional/legal perspectives can potentially create more complexity for deployment and cost efficiency quality attributes.

Since the solution operates mainly in SaaS mode, some concerns from procurement and regional/legal perspectives can potentially create more complexity for deployment and cost efficiency quality attributes.

The solution is API-First oriented for transactional and batch data layers. From that perspective, interfaces are well organized into a catalog so interfaces can be leveraged easily for integration purposes.

The solution is API-First oriented for transactional and batch data layers. From that perspective, interfaces are well organized into a catalog so interfaces can be leveraged easily for integration purposes.

By leveraging Responsive web design and being backed by a scalable/resilient microservice architecture the User Experience can be achieve at the highest level possible. 

UI identity is close to the status-quo solution and it has a great experience for administrative operations. Also by leveraging Responsive web design and being backed by a scalable/resilient microservice architecture the User Experience can be achieve at the highest level possible. 

By leveraging SaaS components in the most of infrastructure, operate and maintaining can be facilitated with lower cost.

By leveraging SaaS components in the most of infrastructure, operate and maintaining can be facilitated with lower cost.

Change management is facilitated for customization on existing features, also to onboard new features given the API available.

Since the solution is API-First oriented for transactional and batch data layers, onboarding new feature by extending status-quo can be speedup.

Since the solution is API-First oriented for transactional and batch data layers, onboarding new feature by extending status-quo can be speedup.

Audit trail captured for edit and view actions on user-feature level and record level.

Audit trail captured for edit and view actions on user-feature level can be shown in a dashboard (notebook).

There is not audit trail at user-data point level.