From the course: Microservices Foundations
Join today to access over 24,900 courses taught by industry experts.
An argument for edge services
From the course: Microservices Foundations
An argument for edge services
- If you remember when we discussed SOA, the beep layer allowed you to expose various services over a common bus. This bus brought about significant problems in managing your code as often it became bloated with code itself and that bloat decrease the ability to manage the infrastructure. In a microservices architecture, you often leverage an API proxy to hide your service implementations behind a common layer. But again, this layer can become bloated if you start transforming your service offerings based on client needs, which is a common approach many are tempted to take. With all of this, you may ask how you can solve multiple client needs which brings us to edge services. The really are two distinct types of edge services in my view, and we will talk about them separately. The first and most common is the outbound edge service. These services are used to expose your client's specific needs to the outside world. The other edge service, often called inbound or translation services…
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.