As mentioned in my previous post, A path to microservices, adopting a microservices architecture is not simple. It requires many prerequisites to be managed successfully. With multiple services you quickly realize how many resources they use. Even the smallest service has a run-time footprint and consumes CPU cycles, even when sitting idle. Multiply this by number of services and you quickly get the picture. This post explores how this can be improved, and if it is possible to go beyond microservices to a serverless architecture.
Developers today most likely can’t imagine not having source control and continuous integration systems. However, one area enterprises may still be struggling with is how to integrate an automated test solution for native mobile applications into a continuous integration workflow. This article provides suggestions on how to do so along with an example of how we did it at Devbridge Group.
If you are a software developer, you already know what Node.js is. You know how to create an API and may feel like Superman while implementing new features. However, as you attract more users, response time gets slower, and with workloads increasing, your application may start to fail. For those with existing applications, this article explores the most likely issues and how message queues, specifically with RabbitMQ in Node.js, effectively helps applications connect and scale. For others planning to build a new application, I incorporate useful tips to help you avoid issues up front.
There are many benefits that a microservices architecture brings if implemented correctly. However, there are many parts involved that should be taken into consideration before going down the path of adopting a microservices architecture environment. This post delves into the details and highlights several areas to consider to ensure any organization has a successful plan in place.