Itโs important to thoroughly consider both the benefits and drawbacks of microservices architecture before you implement it. Itโs also important to implement robust testing strategies to ensure the reliability and quality of the overall system.
Over the course of this blog, Iโll explore the good, the bad, and the testing side of microservices. My hope is that this will give you a starting point as you consider whether microservices architecture is right for your project.
Kubernetes, or k8s, is an important container orchestration platform. In this blog, I’ll describe creating a workable Kubernetes cluster implemented on a stack of four Raspberry Pi boards. In the end, I’ll have provided an outline of how I created it and I’ll show how to replicate a stateless app across Kubernetes pods running on the nodes โ the Pi boards.
Microservices has become a catch-all term in the industry used to describe anything from architecture patterns to actual service implementations.
With such a broad spectrum, it can be daunting to know what it is, what it isnโt, and maybe more importantly, why we should care.
In this post, Iโll provide an overview of three kinds of Microservices that I have observed in client architectures: Domain, Integration, and Unit-of-Work. Iโll also discuss specific examples of their purposes and a method to implement each one.
The big three cloud providers (AWS, Azure, and Google Cloud, in that order) have their various strengths and areas of expertise. Most large organizations though typically pick one cloud provider for their cloud computing needs. This works well if youโre a Java shop thatโs on AWS, or a Microsoft shop on Azure. But what if youโre on a large Java project in an organization that wants to use Azure? Youโre in luck.
Microsoft Azure has come a long way, and is very supportive of non-Microsoft technologies. The proof though is in the pudding. Which is where this blog post comes in. I take Josh Longโs Bootiful Microservice Services, a great starting point to get a cloud native Spring microservice application up and running, and show how it can be run on Azure.
This first blog post will be all about setting up our basic microservices by walking through the various parts of Joshโs example application, with some best practices and patterns that Iโve found to be effective. Rather than a simplistic ToDo application, weโll be basing our application off of my favorite bagel shop in New York, Original Bagel Boss in Hicksville, to manage its orders, inventory, etc. If we can run a bagel shop on a Spring application running on Azure, and keep customers happy and full of carbohydrates, then it proves out for applications of a similar size and complexity.
Weโll be staying mostly inside the familiar Java confines, then slowly start working our way out to getting our application deployed to Azure. Then weโll start introducing additional complexity like Spring Batch jobs, a React front end, etc. A setup this complex will show that Azure is ready for prime time when it comes to running applications in production, even if they are built on non-Microsoft technologies…
AWS SQS (Simple Queue Service) can provide developers with flexibility and scalability when building microservice application(s). In this quick start tutorial, we will demonstrate how to configure a FIFO queue for a fictional online marketplace.
What Is A FIFO Queue?
A FIFO (first in, first out) queue is used when the order of items or events is critical, or where duplicates items in the queue are not permitted. For example:
– Prevent a user from buying an item that isn’t available on a marketplace.