ebook

Microservices or monolith,

RST Software Masters - Microservices

in other words, how to escape an architecture that blocks development

 

Download RST Software Masters' free ebook and:

 

  • discover advantages of using a microservice architecture,
  • learn what to keep in mind when planning to break a monolith down into microservices,
  • find out if switching to microservices will be beneficial to you.

Microservice architecture is constantly gaining popularity. RST Software Masters is one of few Polish software houses that can boast about having practical experience in implementing architectures based on microservices. We want to share insights from our approach to designing IT systems in the context of multiple years of experience with migrating a monolithic system to one with multiple coexisting microservices. From monolith to microservices – answers on how to overcome this challenge can be found in this ebook!

Important

Things to take care of when switching to Microservices

RST Software Masters - Fast environment creation for new microservices

Fast environment creation for new microservices

RST Software Masters- Documentation of connection architecture

Documentation of connection architecture

RST Software Masters - Independence of microservices

Independence of microservices

RST Software Masters - Indication of the owner

Indication of the owner

RST Software Masters - Automatic implementation of microservices in one step

Automatic implementation of microservices in one step

RST Software Masters - The ability to monitor

The ability to monitor

Microservices as seen through the eyes of RST Software Masters

Microservice architecture is constantly gaining popularity. RST Software Masters is one of few Polish software houses that can boast about having practical experience in implementing architectures based on microservices. We want to share insights from our approach to designing IT systems in the context of multiple years of experience with migrating a monolithic system to one with multiple coexisting microservices.

Naturally, microservices are no panacea – however, in terms of business, they can provide many advantages. These include the possibility to have numerous programming teams working on system development at the same time, which allows for simultaneous development in multiple fields. It's worth remembering that microservices facilitate control over system upgrades, if only by wider automated testing of code.

Also, the option to build separate microservices using various technologies is very valuable. Every microservice built using a different technology? Monolith wouldn't allow that. However, within a microservice architecture a given technology – if better suited – can be individually used with a single feature or type of service that it needs to support.

Keeping control over a monolith that has grown throughout the years is hard despite keeping extensive documentation on team management and knowledge distribution levels – simply said, within a team of several dozen of developers building a complex monolith, it would be hard to find a single person that would still have a good grasp of the construction of the system after a month or two of work.

Microservices – who is this ebook aimed at?

RST Software Masters - Microservices

Although the contents focus on technical aspects and are mainly aimed at IT Architects and people working as Chief Technical Officers or Chief Information Officers, we also hope to reach people holding positions such as Product Owner, Product Manager or Chief Executive Officer. Additionally, other people working in management who are building digital products or are undergoing digital transformation might also want to pick it up. This ebook should especially pique the interest of people standing before a tough decision: how to strategically deal with a system that amassed big popularity and has a stable user base, but has become hard and costly to maintain throughout the years. Sometimes an update to one feature causes unexpected behavior in other areas. In such cases, switching to microservices seems the most obvious and long-term beneficial course of action.

Our ebook should also be happily picked up by people responsible for developing new projects and initiatives such as start-up companies. However, in the case of systems which only aim for user feedback or test a market hypothesis and are built in a quick and dirty model on purpose, an architecture based on microservices will not be that financially efficient. The primary stage of breaking down into microservices entails high costs, which are later reimbursed in the form of maintaining a desirably low level of technical debt. As many start-up companies incur this debt on purpose, an approach utilizing this architecture might not necessarily be the best choice for them.

What topics are raised?

This paper aims to define microservices, guiding its readers through practical aspects – what to pay attention to when planning to break down a monolith – and, ultimately, summarizes contexts in which migration is definitely beneficial. In this ebook, among other things, we propose a definition (although no formal definition exists, it is worth pondering about the conditions and criteria that a service would need to meet in order to be called “micro”), present essential criteria while breaking down a monolithic system and introduce a short list of contexts in which it is worth to migrate and when it is not.

What's worth remembering when planning a transition from a monolith

RST Software Masters - Microservices - Remember about that

While thinking about a migration scenario, you should keep in mind a few key points. These are: appointing the owner of the microservices, monitoring the quality of the work of the microservices work and identifying relations that support the independence of the individual microservices ahead of time. In our ebook, we delve deeper into the aforementioned topics and talk about standardization. At the same time, we don't broaden the subject of tools related to implementing RabbitMQ that allow the AMQP protocol to be used. We also don't mention detailed issues concerning REST API, another tool we work with. It would definitely be worth introducing Consul, a tool supporting dynamic scaling and configuration, however, there will be a different time and place for that. In business terms, transitioning to microservices means initially higher costs – these stem from breaking down the monolith and rewriting the code to microservices. However, the benefits of this investment are: lowered risk of vendor lock-in, possibility to have numerous developers working simultaneously on one system, and more. For that reason, it would be good to decompose many systems currently being developed as monoliths – it would allow for easier development, especially if the systems are commercially available in many versions on numerous markets.

Download the free ebook “From monolith to microservices” and find out when is it viable to migrate to microservices, and when said change is profitable. In this paper, we share practical knowledge that we gained while transitioning a system from monolith to microservices, one that processes hundreds of thousands of transactions a month and supports tens of thousands of simultaneous users on a daily basis.

Download free ebook

RST Software Masters - Download free ebook about microservices

To get the ebook, send us your email address.

You’ll receive an email with the download link.

Field required. Maximum length: 256
There was an unexpected error. Please try again later.

WE’VE SENT AN EMAIL WITH THE DOWNLOAD LINK TO OUR FREE EBOOK TO YOUR MAILBOX.

Thank you for your interest in our material.

 

If this is the first resource you download, you will receive an email with a request to confirm the subscription to our mailing list. Confirm it in order to receive an email with the download link.