Transducers are composable reducers. A transducer takes a reducer and returns another reducer. Transducers compose via simple function composition. But, there is a tiny difference between function and transducer composition: functions compose bottom-to-top while transducers top-to-bottom.
Software architecting is about tradeoffs. Even when the theory is good the implementation details can break it. In this article I try to find the best from two architectural approaches: Package by component and Clean architecture (a variety of Ports and adapters).
After some time of developing serverless systems (especially on AWS) I take a look back and try to summarize what I have learned so far.
Why shouldn't we test the implemetation? How to decouple our tests from the code? What is the reason to add a new test? Why is mocking a code smell? In this article I will try to find answers to those questions.
Blue-Green Deployment is a very good technique which has been successfully used for managing releases of cloud applications. Now it's time to rethink it a bit for serverless systems.
Thinking about a deployment strategy for a microservices-based system it's natural to consider a rollback. Before looking for a technical solution, let's discuss this idea conceptually. Is it even possible to roll microservices back?
Talking about serverless microservices, functions are the basic building blocks of the service functionality. How to design them from the code and deployment perspektive?
Designing a system architecture is always about making tradeoffs. Microservices resp. serverless architecture has a lot of benefits, but some drawbacks as well. One of them is testing. Testing serverless systems is hard. In this article I will discuss some practices which work for my project.