Cardlay Architecture – Part 1

3 min READ

Posted 26. Sep 2017

To meet the needs and requirements of our customers, Cardlay utilizes a modern technology stack using proven industry components. We focus on providing our customers with the best possible user experience, while at the same time adhering to all the security standards expected within the field of financial services.

New feature development at Cardlay always starts with the customer in mind, but this series of blog posts will only focus on the technical choices, and you as a reader will have to be patient about how our design process works for a later blog post.

From the very beginning, the principles for guiding our technical architecture is based on a foundation that must enable us to deliver a truly unique and first class user experience.

The readers who are familiar with TOGAF will understand how some of our Enterprise Architecture drivers like Compliance with Law, Business Continuity, and Service Orientation influenced our later architecture choices regarding the Cardlay platform. With this in mind, we carefully consider functional and non-functional requirements and let those guide our architecture choices as we design new products.

As a FinTech company with a broad and varied landscape of partners, we need to integrate with a high level of adaptability and scalability is key. Our platform is therefore based on a domain driven design using a Microservices Architecture. To us, a natural consequence of this is that we remain open to new technology choices if they prove to be better for solving the problem at hand, and we are always exploring the landscape of new and emerging technologies to constantly innovate and push boundaries to improve our products.

Although new emerging technologies can be exciting, we at Cardlay must always carefully consider the possible impact a new choice of technology might have on compliance in for example a PCI DSS context. This remains an interesting challenge where not only the choice of programming language or database should be evaluated but in fact, the entire environment where our solution is hosted. On-premise, Cloud hosted, hybrid – we operate in all, and constantly monitor new directives like PSD2 and their impact on our architecture and our entire operating model. Scalability possibilities and a true cloud architecture vision drive our architecture design and therefore we naturally prefer hosting our platform in the cloud.

From a technical standpoint, it is a very exciting time with huge leaps being taken within the financial industry, and we at Cardlay are thrilled to be part of the journey.

The topic of a future blog post will be a more in-depth description of our infrastructure, the orchestration of how we schedule our services using technologies like Docker and various other tools.

About the author

← View all articles