Instruments to play microservice
Download as PPTX, PDF1 like151 views
This document discusses microservices architecture and the various tools needed to build microservices. It begins by explaining the pros and cons of monolith applications versus microservices. It then covers requirements for building microservices like security, asynchronous communication, monitoring, logging, tracing, service discovery, configuration management, and circuit breakers. Specific open source tools are mentioned for each requirement area, including RabbitMQ, Kafka, Prometheus, Zipkin, Elasticsearch, Eureka, Spring Cloud Config, and Kubernetes. The document concludes by asking if the audience has any additional questions.
![[WSO2Con Asia 2014] Accelerating Mobile App Development with MBaaS](https://cdn.slidesharecdn.com/ss_thumbnails/mbaas-wso2conasia-2014-140325234640-phpapp02-thumbnail.jpg?width=560&fit=bounds)
More Related Content
What's hot (20)
Similar to Instruments to play microservice (20)
![[WSO2Con EU 2018] Decentralized Data Architectures](https://cdn.slidesharecdn.com/ss_thumbnails/wso2coneu2018-decentraliseddataarchitectures-181113104248-thumbnail.jpg?width=560&fit=bounds)
More from Chandresh Pancholi (8)
Recently uploaded (20)
Instruments to play microservice
- 1. Instruments to play Microservices Symphony Chandresh Pancholi
- 2. About me ● Senior Software Engineer at Arvind Internet ● Ex-Flipkart Engineer ● Apache committer ● Technical book reviewer Email: [email protected] Linkedin: https://www.linkedin.com/in/chandresh-pancholi-467a8015
- 3. What is Monolith ?
- 4. Pros ● Simpler build and deployment ● Lower latency for Inter-process communication ● Simpler logging and monitoring ● Easy testing ● Reduce agility over time ● Single tech stack. Easy to understand and build
- 5. Cons ● Coordination overheads as team grows ● All or nothing deployment ● Too much merge conflicts ● Large code base ● Tightly-coupled architecture ● Application downtime will bring down everything
- 6. Microservice A Microservice architecture means that your app is made up of lots of smaller, independent applications capable of running in their own memory space and scaling independently from each other across potentially many separate machines
- 7. Pros ● Independence of development and tech stack ● Easy to onboard new functionality ● Faster development and deployment ● Easy to scale individual service ● Reliability ● Design autonomy ● High cohesion ● Isolation increases speed
- 8. Cons ● Costly inter-process communication ● Achieving and maintaining high availability ● Coordination overheads as team grows ● Lack of tooling ● Security ● Testability ● Increase configuration management
- 9. Requirements to build microservice ● Security ● Async communication among services ● Monitoring & Alerting ● Centralising logging ● Tracing ● Service discovery ● Configuration management ● Circuit breaker ● Containerization ● Orchestrator ● Bonus
- 10. Netflix OSS
- 11. Async communication Requirements ● Microservices can communicate asynchronously with delivery guarantee ● Loose coupling between microservices ● Consistency Tools ● RabbitMQ ● Kafka ● Kinesis
- 12. Monitoring & Alerting Monitoring Requirement: ● Server metrics CPU, RAM, Disk, I/O, Network ● Application metrics JVM, GC, API performance, DB connections, Query performance ● Kubernetes metrics Pod CPU, RAM, Node CPU, RAM, Replica sets status ● Framework metrics Kafka, RabbitMQ, Cassandra, MongoDB ● Application health check from multiple region
- 13. Alerting Requirement ● Email alert ● Slack alert ● Pagerduty alert Tools ● Prometheus ● Sensu ● Graphite ● Grafana ● Pingdom
- 14. Tracing Requirement ● Trace inter-process communication among microservices ● Trace Database queries ● Trace exception trace of every error ● Trace JVM and GC for Java application Tools ● Pinpoint ● Zipkin ● Open Tracing ● Jaeger
- 15. Centralised logging Requirement ● Store Insights about user, order, payment etc ● Store history of an event. Create order event, user signup event ● Run batch processing ● Alert on errors ● Database logs
- 16. Collection ● File, syslog, database Transport ● Kafka, Logstash, Flume, FluentD Storage ● S3, HDFS Analysis ● Hadoop, Spark, Elasticsearch/Kibana
- 17. Service Discovery Requirement ● Discover network location of service instance ● Load balancing request ● Discovery of newly added instances Tools ● Eureka ● Kubernetes services ● Zookeeper ● etcd
- 18. Configuration Management Requirements ● Centrally managed application configuration ● Dynamically reload configuration ● Secure application config Tools ● Spring cloud config ● Netflix archaius ● Hashicorp vault ● Zookeeper ● Consul ● Etcd
- 19. Circuit breaker Requirement ● Failure Isolation ● Graceful degradation ● Avoid cascade failure Tools ● Hystrix ● Turbine
- 20. Containerization Requirement ● Standard way to package containers ● Isolation between microservices ● Efficient application development ● Resource Efficiency Tools ● Docker ● Rkt
- 21. Orchestration Requirements ● Manage containers ● Automating scaling and self scaling ● Automating deployment Tools ● Kubernetes ● Marathon/Mesos ● Docker swarm ● Nomad
- 22. Bonus Istio
- 23. Questions?