Reactive Systems Architecture allows Application Teams to focus on the functional business requirements, leaving the task of addressing various non-functional requirements to the underlying framework, platform components and infrastructure. The functional business logic layer deals in messages, the delivery of which is an event that invokes some processing on that message. Specific to Mastercard / payment systems, these are typically financial messages. The non-functional requirements include, but are not limited to, security, traffic management, infrastructure-independent deployment, scalability, resiliency, high availability, consistent message delivery, delivery auditing, message delivery for failed/absent consumers, application lifecycle management, live/silent mode testing, stateful stream processing, strong consistency, observability, root cause detection and recovery.
Stand Out From the Crowd
Upload your resume and get instant feedback on how well it matches this job.
Job Type
Full-time
Career Level
Mid Level
Education Level
No Education Listed
Number of Employees
5,001-10,000 employees