Technology Infrastructure

ABOUT THE
PRESENTER
•Amber Ayaz

•Manager Application Design at Jazz Cash

•17 Years of Experience in Technology
Architecture, Development & Management
•Fintech & Telecom Industry

•Masters In Business Administration NUST

•Computer Systems Engineering NUST

•[email protected]
•+92 307 1414 236
What is fintech?
What is FinTech?
FINTECH ECOSYSTEM
Channels

Payment
Mobile App Web Channels USSD Third Parties
Gateways

Users
Consumer Merchant Retailer

Services

Account Utility Bill Government

Money Transfer QR Payments
Management Payments Payments

Traffic Challans Mobile Recharge Loyalty Insurance Lending

KEY FOCUS AREAS for FINTECH TECHNOLOGY DESIGN

Highly Always High Growth

Accessible Reliable
Regulated Available Performance Oriented
UNDERSTANDING IT ARCHITECTURE
Presentation Pertains to the Application frontend design
Layer Different Technologies for Mobile, web and other channels

Key Design Consideration : Application Responsiveness

Application Pertains to the Application Backend or server side processing

Layer Common Backend services to provide an OMNI CHANNEL experience

Key Design Consideration : Performance, Throughput, Fault Tolerance

Integration Provides communication between the software architecture components.

Layer Can be Synchronous or Asynchronous on case to case basis.

Key Design Consideration : Reliability and high throughput.

Data Layer Pertains to efficient and reliable means of storing and retrieving data.

Data can be of users, applications, transactional, reporting etc.

Key Design Consideration : Efficiency, persistence, archiving.

Architecture Design Patterns

Monolithic Architecture

SOA Based Architecture

Event Driven Architecture

Microservices Architecture
Monolithic
Architecture
Monolithic architecture, a traditional
approach in which contains all application
components into a single codebase.

• Simplistic Design
• Easy to Setup
• Good for ideation and prototyping
• Difficult to scale
• Increased code debt as application grows
SOA Based Architecture

Loose Coupling:
•Services are designed with minimal dependencies on each
other, making them easier to develop, deploy, and
maintain.
Reusability:
•Services can be used across multiple applications and
business processes, reducing redundancy and development
effort.
Interoperability:
•Services can communicate and interact with each other
regardless of their underlying technology or platform.
Modular Design:
•Complex systems are broken down into smaller,
manageable units (services).
Microservices Architecture
Microservices architecture is characterized by small,
independently deployable services, each responsible
for a specific business capability. It consists of a
collection of small, autonomous services.
Microservices allow a large application to be
separated into smaller independent parts, with each
part having its own realm of responsibility.

Small Teams: A microservice should be

Data Isolation : It is much easier to
small enough that a single feature team
perform schema updates, because only a
can build, test, and deploy it. Small team
single microservice is affected.
sizes promote greater agility.

Built for modern

businesses: Microservices architecture is Scalability is improved: Scalability also
created to focus on fulfilling the makes deploying new features and
requirements of modern, digital updates easier without taking the whole
businesses. Traditional monolithic system offline. In a microservices
architectures have teams work on architecture, only the affected service
developing functions such as UI, needs to be taken offline for changes or
technology layers, databases, and server- updates to be made.
side logic.
Microservic
es
Architectur
e
Event Driven •Event-driven architecture (EDA) is a software design
pattern where systems respond to events in real-time, like
Architecture a message being received or a change in state.
IT ARCHITECTURE FINTECH
What is Cloud?
Cloud computing is the delivery of computing services—such as servers, storage, databases, networking, software, and more
—over the internet ("the cloud"). It enables users to access and use IT resources on-demand, without needing to own and
manage physical infrastructure. Cloud deployments are generally categorized into three main types:

Public Cloud
• Hosted by: Third-party cloud service providers (e.g., AWS, Azure, Google Cloud).
• Access: Shared infrastructure accessible to multiple customers.
• Pros: Cost-effective, scalable, no maintenance by users.
• Example: Google Drive, Microsoft Azure.
Private Cloud
• Hosted by: A single organization (either on-premise or by a third-party).
• Access: Exclusive to one organization.
• Pros: Greater control, security, and customization.
• Example: A company’s in-house data center or a hosted private cloud service.
Hybrid Cloud
• Combination of: Public and private clouds.
• Purpose: Allows data and apps to move between the two environments.
• Pros: Flexibility, optimization of existing infrastructure, improved security.
• Example: A business runs sensitive apps on a private cloud and uses the public cloud for less-critical
resources.
Cloud Native
Technologies
• Horizontal and Vertical Scaling
• Microservices based Design
• Containerized Environment
• Dev Ops Utilizing CI/CD Pipelines
• Open APIs
• Observability & Automation
SOFTWARE
DELIVERY
LIFECYCLE
 •Planning
•Define goals, scope, and requirements.
•Identify resources, risks, timelines, and budget.
•Stakeholders, project managers, and business analysts are heavily involved.
•2. Requirements Gathering & Analysis
•Collect business and user needs.
•Document functional and non-functional requirements.
•Create use cases and workflow diagrams.
•3. Design
•Create the architecture and system design.
•UI/UX design, database schema, and system interfaces are defined.

SDLC
•Design specifications guide the development team.
•4. Implementation / Development
•Developers write the actual code based on the design documents.
•Could involve frontend, backend, database, APIs, etc.
•Usually done in iterations or sprints (in Agile environments).
•5. Testing
•Quality Assurance (QA) team tests the software for bugs, performance, and security.
•Types of testing include unit testing, integration testing, system testing, and user acceptance testing (UAT).
•6. Deployment
•The software is released to a production environment.
•Can be done manually or through automated CI/CD pipelines.
•May involve a phased rollout or full deployment.
•7. Maintenance & Support
•Ongoing updates, bug fixes, and improvements.
•Ensures software continues to meet user needs and remains secure.
Agile Methodology

•Responding to Change
•Iterative Development
• Agile embraces changes in requirements, even late in
• Work is broken into small cycles called sprints (usually development.
1–4 weeks).
• Teams adjust priorities and plans based on evolving
• At the end of each sprint, a working piece of software is needs.
delivered.
•Cross-functional Teams
•Customer Collaboration
• Teams include developers, testers, designers, and
• Continuous involvement of stakeholders and users sometimes even business analysts—all working
throughout the process. together.
• Feedback is gathered frequently and used to refine the •Working Software as the Primary Measure of Progress
product.
• Focus is on delivering functional features over detailed
documentation.
Roles in
an Agile
Team
 •Product Owner:
•The Product Owner is responsible for defining the product vision,
prioritizing the product backlog (a list of features and tasks), and
representing the needs of stakeholders, including end users, says
Indeed. They ensure the team is delivering the most value to the end
Roles in user.
•Scrum Master:
an Agile •The Scrum Master facilitates the Scrum process, ensuring the team
follows Agile principles and practices. They coach the team, remove
Team impediments, and help the team continuously improve their processes.
•Development Team:
•The Development Team is a cross-functional group responsible for
designing, building, testing, and delivering the product. They self-
organize and collaborate to achieve the sprint goals set by the Product
Owner.
 •Business Analyst:
Agile Business Analyst (ABA) acts as a bridge between business
stakeholders and the development team, translating business needs
into actionable user stories, concludes on development effort estimates
and closely interacts with the developers to complete the user stories as
per customer expectations
Roles in
•Stakeholders:
an Agile While not directly involved in the Scrum process, stakeholders are
crucial for influencing the product and ensuring its success. They can be
Team users, business executives, or other individuals who have a vested
interest in the product.

•Agile Coach:
Agile Coaches help organizations and teams adopt Agile practices,
providing guidance and support to ensure successful implementation.
Agile Scrum Framework
Agile
Scrum
Framewo
rk
Requirement Capturing
User Story

•A user story is a short, simple description

of a software feature from the end user's
perspective. It captures what the user
wants to do and why, helping the
development team understand the value
behind a feature. It’s the most granular level
to which a working user scenario can be
considered as a working Feature
Agile
Scrum
Framewo
rk
Requirement Backlog
Agile
Scrum
Framewo
rk
Requirement Backlog
Agile
Scrum
Framewo
rk
Daily Standup Meeting
Agile Scrum Framework
Retrospective Meeting
 Iterative Scope delivery allows to follow an MVP
oriented approach

Agile Collaborative teams taking ownership and

responsibility improving development pace

Scrum Flexible scope to allow for changing business

needs.
Framewo
rk Requires mindset change on organizational level

Risk of scope creep

Agile teams developing
cloud Native
Applications

• Smaller
Autonomy onagile
team cross functional
level team working on
for prioritization
relevant microservices allow for independent
and changes
development and new feature launches
 AI Ops

• AI based observability predicts system failures and raises alarms

• Predictive autoscaling
• Tools such as App Dynamics

AI based Development
AI
Transformati • AI Based code generation
• Generate modular code and integrate manually

on in Fintech • Intelligent code merging and CI/CD

Technology AI in Quality Assurance

• Codeless Automation tools

• Smart waits and auto healing features
• Intelligent Visual testing
• Customer behavior replication
• Example : Katalon True test
Thankyou