Join David Linthicum for an in-depth discussion in this video Microservices examples, part of Cloud Architecture: Advanced Concepts.
- [Instructor] These are just instances of use cases that we're going to look at when we look at examples of microservices. You need to consider that you can build anything with microservices. It becomes kind of a fundamental base of applications and the use cases in applications are limitless, so it's very difficult for me or somebody else to basically point you to a example where microservices are always going to be leveraged. They're basic, general-purpose development technologies and you're able to leverage them in utilities and business applications and any number of things where we're using fine-grain services are typically services you don't write from scratch.
You're leveraging somebody else's services remotely. That's an example of the application and that's virtually limitless in terms of what you can leverage this technology for. So in the one example here, we have a user interface at the top of the screen and that's able to communicate with sets of microservices. In this case, we have four, update, delete, edit, and validate, and we saw that in the previous example as well. This could be a social security number, for example, doing a credit check or some other form of business processing that we may do as part of building the system.
And then at the bottom we have the data. We have customer data, we have sales data, and we have product data, and those microservices are interacting with that data as well. Keep in mind here that the interface, the user interface on top is going to be the composition application which is going to be made up of the microservices, update, delete, edit, and validate, and we'll assume that those are the same at the microservices level, and those microservices in turn are communicating with the back end databases, in this case customers, sales, and products, and keep in mind that those microservices are reading the data on behalf of the user interface, and they're doing some function with it, such as update, delete, edit, and validate, but they're interacting with the data on the behalf of the composite system and so the composite system is really doing nothing but invoking the microservice.
It's actually calling the URL of the microservice, and that microservice is, as a part of its behavior, its preprogrammed behavior, is reaching to the back end systemss, communicating with one of those three databases, and doing that specific function on the databases, you know, such as updating, deleting, editing, or validating, and then returning the data to the microservice, which in turn returns the data to the composite application, in this case the user interface which is on top of your screen. Sound complex, but it's really kind of a nice decoupled architecture where we're able to kind of place things in their own nice little domains.
They do their own functions, and therefore they're much more easier to maintain and more importantly, they're much more easier to change and much more easier to reuse.
- Microservices and containers
- Complex, disturbed, serverless, and composite architectures
- DevOps integration
- High-performance solutions