Microservice Workshop Hands On
1 like71 views
This document provides an agenda and overview for a microservices workshop focusing on hands-on experience. The agenda includes discussing code repository styles, API design with Spring Boot, microservice deployment, and hands-on breakout sessions to build sample microservices. Repository options like mono vs multiple are presented along with pros and cons. Spring Boot basics are explained including conventions, non-functional features, and packaging. Microservice deployment considerations and using Docker are also covered. Participants will then work in teams to build microservices for an e-commerce application.
Microservice Workshop Hands On
- 1. Microservice Workshop Hands on Ram G Suri / Rajat
- 2. Agenda ● Different Styles of maintaining code repositories ● Around API’s ● Spring Boot Overview ● Deployment of Microservices ● Hands On - Let’s spin up services
- 3. Different Styles Of Maintaining Code Repository(s) Mono Repository / Multiple Repositories
- 4. What we are trying to achieve We are working on an ECommerce application using microservice architecture. We used technologies like Java / Go for our microservices. We created DevOps pipeline for those services independently. The main problem was whether to keep all the services in the same repository in separate folders (Mono repository) or to keep separate repositories for each of the services (Multiple repositories).
- 6. Pros / Cons Multiple Repo Mono Repo ● Clear ownership Better development and debugging ● Smaller codebase Easy sharing of common codes ● Narrow clones Easy reactoring and reviews ● Small artifact size Huge artifact size ● Difficult development and debugging Large code base ● Sharing of common codes Greater Clone time
- 7. Around API’s
- 8. “Bootiful” Applications With Spring Boot
- 9. Convention Over Configuration Be opinionated out of the box, but get out of the way quickly as requirements start to diverge from the defaults. No code generation / No XML configuration. Standalone-Spring applications. Automatic configuration.
- 10. Non functional features Provide a range of non-functional features that are common to large classes of projects ( e.g. embedded servers, security, metrics, externalized configuration {spring profiles} ) ….no need to deploy war files
- 11. Spring boot actuator ~ Production Ready features You can choose to manage and monitor your application by using HTTP endpoints or with JMX. Auditing, health, and metrics gathering can also be automatically applied to your application. Monitoring endpoints ● /health ● /info ● /metrics ● /mappings
- 12. Starter Pom
- 13. Packaging For Production $ java -jar yourapp.jar No unpacking or start scripts required Typical REST app ~10Mb Cloud Foundry friendly (works & fast to upload)
- 14. How it helps ? ● Dramatically reduces boilerplate code ● Simplifies integration testing ● Simplifies environment maintenance ● Simplifies configuration
- 15. Pain Areas ? When number of microservices increases ? Communication between microservices / Integrating Microservices Distributed tracing a request among microservices.
- 16. Deployment of Microservices ● Ability to deploy/undeploy independently of other microservices. ● Must be able to scale at each microservices level (a given service may get more traffic than other services). ● Building and deploying microservices quickly. ● Failure in one microservice must not affect any of the other services.
- 17. Docker : ● Package the microservice as a (Docker) container image. ● Deploy each service instance as a container. ● Scaling is done based on changing the number of container instances. ● Building, deploying, and starting microservice will be much faster as we are using Docker containers.
- 19. Hands On Agenda : 1. Create Standalone app 2. Create RESTful Controller ● GET ● POST 3.
- 20. Team 1 Catalogue - save a new item - get all items from catalogue
- 21. Team 2 Shipping - save shipping address - get shipping address
- 22. Team 3 Proceed to checkout - Create an order - Cancel an order
- 23. Thank You
Editor's Notes
- #10: Auto-configures the beans that are present in the classpath. This simplifies the developers work by guessing the required beans from the classpath and configure it to run the application.