Microservice architecture is one of the recent buzzwords in the world of software development. It can help create scalable, robust software even in complex business domains. However, it introduces additional operational complexity among which is communication between many services.
Payment Services Directive 2 was passed almost three years ago on 25. November 2015. However, as with most European directives it had a pretty long transition period. September 2019 was the final deadline for implementing strong customer authentication (SCA).
We guess we can all agree that European directives are not the buzz topics for most people; but it so happens they are for us. Having said that, let us explain why PSD2 is something worth knowing.
In addition to being one of Clutch’s top firms in Eastern Europe, we are currently ranked as the No. 1 Custom Software Developer in Warsaw.
Looking around, you certainly notice that we are making more and more non-cash transactions. There is a great deal of options available: debit and credit cards, mobile applications of our banks, smart watches. There is no coming back to the old days, when you always had to carry cash with you.
Continuing with my previous post, let's try to implement some simple rate limiting for our application using Micronaut's caching and Resilience4j.
Micronaut makes creating web applications a breeze. The most interesting thing about it is that it does not use any runtime reflection and still provides a clean and enjoyable API, among others, thanks to compile time annotation based dependency injection.
Kotlin 1.3 introduces inline classes. They are declared using inline keyword, placed before the class keyword. An inline class must have a single property initialized in the primary constructor.
I wanted to try out Kotlin + Spek 2 testing framework combination. So here it is a step-by-step guide to build a simple application.