Building APIs as micro-services

A talk on micro-services by a friend at the Andela Institute.

Transcript

1. Building APIs as Micro- services Sokari, Tams
2. What are Micro-Services?
3. Micro-services are simply component units of a larger service.
4. A Sound System with different components Example Illustration
5. If we wish to be technical, Micro-services are a software architecture style in which complex apps are composed of small independent processes communicating with each other. Micro-services implement the much talked about Single Responsibility Principle (SRP).
6. Why Micro-services?
7. Pros of Micro-services • Ease of Development. • Ease of Deployment. • Scalability. • Flexibility with Choice of Tools. • Ease of Maintenance.
8. Cons of Micro-services • Costs more to start up. • Increased number of requests. • Takes more memory.
9. How we build Micro-service APIs
10. Building APIs in the Micro-Service pattern requires two main layers: 1. The Service/Resource APIs. 2. The Gateway API.
11. Micro-services API structure
12. When do we build Micro- Service APIs?
13. • Micro-Service APIs can be used when you have a large API. • If you envision a large API, it is best to start by building in the Micro-services pattern.
14. Note-Worthy • Service APIs may or may not be made public for consumption. • Cross Origin Resource Sharing (CORS) is a means of limiting access. • It is best practices to limit access to the Gateway API when building APIs in the Micro-service Pattern.
15. Questions???
16. Resources • www.microservices.io • Software Architecture Patterns: http:// www.oreilly.com/programming/free/files/software- architecture-patterns.pdf