Building With Insomnia as a REST API Client

As more companies invest in a cloud native infrastructure, they’re choosing to prioritize their applications as microservices—architecting them into distinct servers. Each component is responsible for one (and only one) feature. For example, you might have Server A responsible for handling billing logic, Server B for handling user interaction and Server C for handling third-party user interactions.

Debugging Microservice Applications with Thundra

Debugging has traditionally been done during the development of software by putting breakpoints to the suspicious lines of the code. And when the execution hits the breakpoint, it stops naturally and you get the outputs you need in order to understand the root cause of a defect. What if your software is a modern application, actively running in production and serving users. In this case, you are mostly left alone with logs.

Microservices vs Monoliths explained

If you’re a dev you’ve no doubt, come across people talking about monolith and microservice application architecture. Perhaps you are involved in designing a new system and have been asked to consider both architectures. The conversations are often regarding how microservices are the successor to monolith architecture, but today I’m going to try and layout why it’s not as simple as one being better than the other.

Faster Microservice-to-Microservice encrypted communication with Kong Mesh and Intel

Service Mesh is an infrastructure layer that has become a common architectural pattern for intra-service transparent communication. By combining Kubernetes a container orchestration framework, you can form a powerful platform for your microservices cluster, addressing the typical technical requirements that occur in highly distributed environments. A service mesh is implemented through a sidecar configuration, or proxy instance, for each service instance.

Mid Atlantic Meetup | May 2021 - What can APIs and Microservices tell us about organizations?

Architects are tasked with seeing that organizations meet their objectives with speed and quality, for a reasonable cost. This simple mission is anything but simple. Security, analytics, and everything in-between present themselves as forces to be acknowledged and considered. Building APIs and Microservices present new puzzles to be solved for architects. Or do they? In this session, we attempt to detect patterns that present themselves in organizations, which have their root in human elements. Yet reliably manifest in technology.

Monolithic vs. Microservices Architecture: A Side-by-Side Comparison

Microservices have gained a lot of traction in the last few years. Ever since the dawn of time, monolithism – packaging all your modules into one colossal codebase – was the default way to go when building software applications. However, as applications have had to cater to increasing volumes (of millions) of users over the internet over the last decade, scalability and flexibility have become ever more critical.

Top 10 Microservices Benefits

Many companies have embarked on microservices software projects in an effort to make modernize their suite of technology systems and reap the benefits that can come from deploying such an architecture. In the microservices model, applications are divided into a series of interconnected services based on operational capabilities. Each service supports a distinct set of functionality, effectively acting as a mini-application with its own operational logic, adapters, and even database schema.

How to Solve Microservices Contracts Issues

Microservice architecture makes it possible for teams to develop services at their own speed. However, any company that adopts a microservice architecture will face challenges in running and evolving their services if they don’t implement a solution to mitigate it. One of the major problems that companies face when they switch to a microservice architecture is maintaining a clean API for each microservice in their application.

5 Best Practices for Successful Microservices Implementation

Microservices are a popular and modern organizational software engineering practice. The guiding principle of any microservices implementation is to develop an application by dividing its business components into smaller services that can be deployed and operated independently of each other. The separation of concerns between services is defined as “service boundaries.”