microservices

14 posts
microservices

Implementation of a monitoring strategy for products based on microservices

Proper instrumentation of microservices ensures faster pinpointing and troubleshooting of problems. These include metrics for availability, metrics for capacity planning or to detect resource saturation, and metrics to understand internal states of each instance of a microservice.…

microservices

Microservices architecture as a large-scale refactoring tool

To refactor a monolith into microservices architecture, you need to break it into single responsibilities or services in an incremental fashion…

microservices

Do you have too many microservices? - 5 design attributes that can help

When you are developing microservices, ensure that each service relies on its own underlying data stores. If multiple services reference the same table in a DB, there is a great chance that your DB is a source of coupling. You must avoid such coupling.…

GraphQL

Unique benefits of using GraphQL in microservices

The data structure in GraphQL allows for well-defined & delineated data ownership for each request. You can have great control over the data loading process and therefore control how data is transferred in a very granular way.…

microservices

Walking the wire: Mastering the four decisions in microservices architecture

There should be no shared databases. If updates happen only in one microservice, you can use message queues to share data. If updates happen in two services, either merge the two services or use transactions.…

Issue63

Blue-green deployment: a microservices antipattern

Blue-green deployment is a technique that reduces downtime for your application by running two identical production environments called Blue & Green.…

Issue63

Security traps to avoid when migrating from a monolith to microservices

Rollback to the last known good state after a failure is more complex with microservices, so program in reverts carefully for data integrity.…

Issue55

Happy customers, quality code: the new trends in software development

It takes an average of 3.3 different tools to know the real status of the project and teams use an average of 4.3 tools to move code from development to production. 57% developers reported fewer bugs or outages by adopting CI/CD solutions.…

Issue43

9 tips for a painless microservices migration

Document your URL route domains and ensure everyone follows the one convention. Be explicit about routes and methods. Avoid wildcard routes and wildcard verbs or HTTP methods.…

Issue43

3 easy things to do to make your microservices more resilient

Test your system using chaos strategies. Have a plan to at least partially fulfill your service promise in case of a fault, whether it is a canned message or calling a different service as a backup.…