Reviews for 'Application Development, Integration and Management - Others'
Gartner defines banking payment hub as a configurable platform that enables financial institutions to centrally process incoming and outgoing payments. Banking payment hubs are deployed with a software-only on-premises model or in the cloud as software only, software as a service (SaaS), or payments as a service (PaaS). They have three layers: an input layer, a processing layer and an output layer.
Gartner defines a core banking system (CBS) as the financial institution’s back‐office software that performs real-time or end-of-day processing for deposits and loans. Apart from advancing the processing dates, representative capabilities include transaction posting, interest accrual/payment, service charge calculation and cash management (zero balance, target balance). CBSs provide deposit and loan product servicing with interfaces to other applications, such as customer-facing channels, general ledger systems and reporting tools. CBSs can be deployed on the bank’s premises or run from the cloud or any hosted environment. Bank employees and customers either directly or indirectly use the bank’s CBS.
Gartner defines digital banking platforms (DBPs) as a set of modular capabilities that enable the bank to create and customize employee and customer digital journeys. DBPs sit between the bank core and the engagement layer (i.e., multichannel solutions or employee applications) and provide a unified environment for four main technology categories: (1) bank-specific composable business services that constitute user journeys, (2) common platform services that support the composable business services, (3) developer tools for journey creation and customization and (4) modern data and analytics for business intelligence, customer insights and continuous improvement. DBPs are consumed as private cloud SaaS, public cloud SaaS or on-premises.
Gartner defines enterprise low-code application platforms (LCAPs) as software platforms for the accelerated development and maintenance of applications, using model-driven development tools, generative AI and prebuilt component catalogs for the entire application’s technology stack. Enterprise LCAP features include support for the collaborative development of all application components; runtime environments for high performance, availability and scalability of applications; and application deployment and monitoring with detailed usage insights. Enterprise LCAP platforms feature governance controls and insights, self-service capabilities, APIs for integration with external DevOps tooling, success management with exhaustive technical documentation, training programs and a comprehensive global partner network. Enterprise LCAPs provide the foundation for developing a wide range of applications and application components with distributed data architectures, including complex multimodal front ends, business workflows, agentic AI and integration capabilities. The enterprise LCAP market is closely related to the citizen application development platform (CADP) market, as they both aim to address the use cases listed below. However, they are distinctively different in terms of the target audience and complexity of the applications built on the platform.
An MXDP is an opinionated, integrated set of front-end development tools and “backend for frontend” (BFF) capabilities. It enables a distributed, scalable development approach (in terms of both teams and architecture) to build fit-for-purpose apps across digital touchpoints and interaction modalities. At minimum, an MXDP must support cross-platform development and building of both custom iOS and Android app binaries, responsive web apps, and at least one of the following: PWAs, chatbots, voice apps, wearables and Internet of Things (IoT) apps, and augmented-reality (AR) and mixed-reality (MR) apps.