Vert.X and MSA - DevOps
15 likes1,251 views
Vertx는 모든 면에서 뛰어나지만 혼자서 모든걸 다 하려는건 실수다. 잘 하는것만 집중해도 성공하기 힘든 경우가 많다. 간결한 REST API, 쉬운 WEBSOCKET 에 집중하고, 나머지는 다른 진영에 맡기자.
![[OpenInfra Days Korea 2018] Day 2 - E5-1: "Invited Talk: Kubicorn - Building ...](https://cdn.slidesharecdn.com/ss_thumbnails/e60955buildingsimplekubernetes-180705043459-thumbnail.jpg?width=560&fit=bounds)
Ad
More Related Content
What's hot (20)
Similar to Vert.X and MSA - DevOps (20)
![[DevDay 2017] OpenShift Enterprise - Speaker: Linh Do - DevOps Engineer at Ax...](https://cdn.slidesharecdn.com/ss_thumbnails/linhdoopenshiftenterprises-170420095822-thumbnail.jpg?width=560&fit=bounds)
Ad
Recently uploaded (20)
Ad
Vert.X and MSA - DevOps
- 1. Vert.X and MSA Vert.X로 하는 마이크로서비스 - 기승전 DevOps
- 3. Eclipse Vert.x is event driven and non blocking. This means your app can handle a lot of concurrency using a small number of kernel threads. Vert.x lets your app scale with minimal hardware.
- 4. • Writing TCP clients and servers • Writing HTTP clients and servers including support for WebSockets • The Event bus • Shared data - local maps and clustered distributed maps • Periodic and delayed actions • Deploying and undeploying Verticles • Datagram Sockets • DNS client • File system access • High availability • Clustering
- 5. The END of Vert.X MSA Vert.x Blueprint - Micro Shop http://www.sczyh30.com/ vertx-blueprint-microservice/ index.html
- 6. • Account microservice - provides user account operation functionality. Use MySQL as persistence. • Product microservice - provides product operation functionality. Use MySQL as persistence. • Inventory microservice - provides product inventory operation functionality, e.g. retrieve, increase and decrease. Use Redis as persistence. • Store microservice - provides personal shop operation functionality. Use MongoDB as persistence. • Shopping cart microservice - it manages the shopping cart operations (e.g. add, remove and checkout) and generates orders. Shopping carts are stored and retrieved with event sourcing pattern. Orders are sent on the event bus. • Order microservice(dispatcher and processor) - it receives order requests from the cart service via event bus and then dispatch the orders to the infrastructure services (e.g. processing, storage and logging). • The Micro Shop SPA - the frontend SPA of the microservice (now integrated with api-gateway) • The monitor dashboard - a simple web UI to monitor the status of the microservice system • The API Gateway - The API gateway is the door of the entire system. Every requests must be first sent to the gateway and then dispatched to each service endpoints (reverse proxy). It is also responsible for authentication, simple load- balancing and failure handling (using Vert.x Circuit Breaker).
- 10. 많은 기능이 있다. 다 된다. 좋다. 멋지지 ? There are many functions. It is done. very good. Awesome !!
- 13. • REST API Microservice • SOCKET API Micreservice • URI base router • reverse-proxy • loadbalance (L7) • Service Discovery ? 개발이 필요한 부분 이전엔 해본적 없는 추가로 해야만 하는 개발
- 14. Vert.X MSA is NOT EASY
- 15. We are back now.
- 16. 개발팀이 할 일 • URI base router - Nginx, haProxy • reverse-proxy - Nginx, haProxy • loadbalance (L7) - Nginx, haProxy • Service Discovery ? - Nginx, haProxy • REST API Microservice • SOCKET API Micreservice 누군가가 할 일
- 18. 누군가가 누구야 ?
- 19. Vert.X 로 쉽게 할 수 있지 !! • URI base router - Nginx, haProxy • reverse-proxy - Nginx, haProxy • loadbalance (L7) - Nginx, haProxy • Service Discovery ? - Nginx, haProxy • REST API Microservice • SOCKET API Micreservice 누구도 해주 지 않는 일. 할 사람이 없다.
- 20. • URI base router - Nginx, haProxy • reverse-proxy - Nginx, haProxy • loadbalance (L7) - Nginx, haProxy • Service Discovery ? - Nginx, haProxy 다행히 내가 쫌 알지. 내가 하자. 기승전 DevOps
- 21. Api Gateway ( Nginx ) Load Balancer A ( haProxy ) Load Balancer B ( haProxy ) Load Balancer C ( haProxy ) Api Gateway ( Nginx ) Service A Service A Service AService B Service B Service B Service C Service C DNS, Hardware L4, Hardware L7 개발팀이 할 일
- 22. Service A Service B Service C 개발팀이 할 일 남는 시간에 쥐나 잡으러 가자
- 23. • Cloud, Linux, Wondows Server, Unix • Network • Docker • openstack, openshift, kubernetes, mesos • Nginx • haProxy • Message Queue • DNS • Loadbalance L4, L7 • reverse proxy • In memory Cache • NoSql • sometimes BIGDATA • sometimes AI • sometimes Machine learning • ………… 대략 이정도 알고 있으면 나도 DevOps
- 24. 그래서 DevOps 개발자를 구하기 힘들고, 그들의 몸값이 비싼거지. So DevOps developers are hard to hire and their salary is HIGH.
- 25. 이런 접근을 함께 고민 할 팀이 필요하다. We need a team to deal with this approach. In the future,
- 26. 기승전 DevOps 끝 !
- 27. 발표자 : 이용혁 ( [email protected] ) https://github.com/unlogicaldev https://www.facebook.com/UnLogicalDev