Transactions in Microservices Architecture

Transactions are an easy technique for software developers to achieve data consistency. Changes are all committed or rollback, so your data is always aligned and other sessions see no incomplete information. But in distributed microservices environments, this cannot be achieved because data can be spread over several data sources and types of data sources, or …

Transactions in Microservices Architecture Read More »

Common Mistakes When Moving to Microservices

Here are some of the common mistakes when moving to microservices that are discussed in this presentation, with provided solutions for:* No realistic architecture process (architecture decisions too rigid, or not taken; infra vs domain; architecture guild vs no cooperation, knowledge sharing ); * QA thinks testing end-to-end is possible; Management wants to control deployment; …

Common Mistakes When Moving to Microservices Read More »

Monoliths Between Microservices

Ruby on Rails applications tend to turn into giant monoliths software architecture. Keeping the codebase maintainable usually requires architectural changes. Microservices? A distributed monolith is still a monolith. What about breaking the code into pieces and rebuild a monolithic puzzle out of them?