Microservices 5 things i wish i'd known java with the best 2018
•
2 likes•350 views
Microservices are hot! A lot of companies are experimenting with this architectural pattern that greatly benefits the software development process. When adopting new patterns we always encounter that moment where we think ‘if only I knew this three months ago’. This talk will be a sneak peak into the world of microservices at Atlassian and reveal what we’ve learnt about microservices: how to arrange, configure and build your code efficiently; deployment and testing; securing communication between them and how to operate effectively in this environment. In this talk you will learn how to immediately apply these five patterns to your environment straight away.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Microservices 5 things i wish i'd known java with the best 2018
Similar to Microservices 5 things i wish i'd known java with the best 2018 (20)
More from Vincent Kok
More from Vincent Kok (9)
Recently uploaded
Recently uploaded (20)
Microservices 5 things i wish i'd known java with the best 2018
- 1. VINCENT KOK | ENGINEERING MANAGER, TRELLO | @VINCENTKOK Microservices 5 things I wish I’d known5 6 things I wish I’d known
- 2. Part-time speaker For fun and zero profit About me: @vincentkok Trello Engineering Manager on the Trello team Dutch You probably heard that already ;)
- 3. Microservices Everybody seems to want them. Do we really know the impact of our choices? Why do we want them so badly? Microservices are messy! https://flic.kr/p/9u5pDA
- 5. Grow Fat Code base grows. All the things slow down. Age Your code base will become a jurassic park introducing new tech becomes hard Ownership Who is responsible for which part and more important: who has the pager Economies of Scale The bigger the team the more they interrupt each other Monolithical issues
- 7. 8100 Build jobs ran last week
- 9. Cause of issues can be extremely hard
- 10. Who is having the pager? INCIDENT RESPONSE
- 11. Remember, we’re not all webscale
- 13. Optimise for rapid and sustainable flow of value. DAN NORD
- 15. Small The size will be reasonable and manageable Independent lifecycle Nothing will hold the team back. Go as fast as you can Optimise for the problem Pick solution and tech based on the problem at hand Replaceable It is easier to replace if there is a need for it The microservice promise
- 18. Creating a call-out Watch the tutorial in the Presentation Guidelines to learn how to create call-outs on screenshots within this template.
- 19. MINIMAL SERVICE Health check 200 app is alive. 500 app is unhealthy, destroy the node Stateless* Run as many nodes as you need Expose a port Only access to the service
- 20. DEEPCHECK Deep check Quickly discover if a service fails to connect to a dependency
- 21. DEEPCHECK EXAMPLE { "avatar": { "details": { "avatarRepository": { "isHealthy": true }, "crowd": { "isHealthy": true }, "deadlock": { "isHealthy": true
- 22. CODE & BUILDS 1 repository 1 build
- 23. Libraries Feel free to use shared libraries but keep them loose Config Be aware of the configuration lifecycle Schemas Make sure that services are resilient to schema changes -> Postel’s law Testing Test in isolation. Keep them decoupled
- 24. Strict separation of config from code. 12 FACTOR APP
- 25. Redeploy Part of the service configuration. Configuration lifecycles Instant change Switches you would like to enable/disable straight away Rebuild Rebuild to apply changes
- 26. Treat them as cattle, not pets. BILL BAKER
- 28. Only one person There is only one person in the team that owns it Deployment smells Takes more then 15 mins Setting it up should be quick and initial deployment should quick Requires a ticket A ticket for the deployment team
- 29. Always deploy an empty service into production ME AND PROBABLY OTHERS
- 30. Developers in control Artifact What is the artifact we’re running. We’re mostly standardising on Docker Resources What resources are requires: RDS, SQS, Dynamo etc.. Compute What EC2 instance do we want how many of those and when to scale Alarms What are the alarm thresholds for this service Ownership Who is owning the service Configuration We will be adding more icons as need arises. Speak up if in need!
- 31. DECLARATIVE DEPLOYMENT name: Confluence description: Confluence Cloud links: binary: type: docker name: docker.atlassian.io/confluence tag: latest healthcheck: uri: /wiki/internal/healthcheck deepcheck: uri: /wiki/internal/deepcheck semanticCheck:
- 32. CONFIGURATION config: environmentVariables: ASAP_AUDIENCE: "foo" ASAP_ISSUER: "foo" CONFLUENCE_VERTIGO_SMTP_HOST: "smtp.foo.com" CONFLUENCE_VERTIGO_SMTP_PORT: "587" LOG4J_EXTRA_RULES: "log4j.logger.org.hiberate=DEBU environmentOverrides: staging: config: environmentVariables: ASAP_PUBLIC_KEY_FALLBACK_REPOSITORY_URL:
- 33. RESOURCES resources: - type: sqs name: default attributes: MaxReceiveCount: 20 VisibilityTimeout: 60 scaling: instance: m3.xlarge min: 7
- 38. TESTING MONOLITHS IS EASY
- 40. TESTING Live service Test agains a real serviceMock service Test against a mock service
- 41. In process A local implementation of your client Out of process Use tools like WireMock and MockServer Two options
- 42. MOCKING SERVICES - IN PROCESS <beans profile=“integration-test"> <bean id="attachmentService" class=“c.a.attachment.AttachmentStub”/> </beans>
- 43. MOCKING SERVICES - WIREMOCK { "request": { "url": “/rest/api/content“, "method": “POST” "Accept": { "matches": “application/json” } }, "response": { "status": 200 } }
- 44. Stable API If it is external it already should have a CTK so rely on it How to trust your mock? Contract testing Internal fast moving API’s an benefit from this Rely on monitoring Small service, low MTTR therefore low impact
- 45. Semantic Check Automated test that runs against a node before it will be added to the load balancer
- 47. OAuth 2.0 Grant a client access to resources based on a newly created set of credentials Common standards OpenID Connect Identity on top of OAuth 2 OpenID Allows identity and some metadata only
- 48. How to secure a set of many services? SECURING SERVICES
- 49. ASAP Atlassian Service Authentication Protocol
- 50. HOW DOES IT WORK? Foo BarJWT
- 51. WHAT’S INSIDE? Foo Bar { "typ": "JWT", "kid": "foo/key1", "alg": "RS256" } { "sub": “32769:87e…” "aud": "bar", "nbf": 1494284564, "iss": "foo", "exp": 1494284624, "iat": 1494284564, "jti": “961253cf-ac…” }
- 52. { "kid": "foo/key1", } { "sub": “32769:87e…” "aud": "bar", "iss": "foo" }
- 55. 100 lbs 99% water dehydrate 98% Guess the weight! https://flic.kr/p/npbxAm
- 56. 50 lbs
- 57. Uptime of a system with 30 services of 99.99? TRANSLATING THIS TO A MICROSERVICE ARCHITECTURE
- 58. 2 hours 99.99 = 99.7 30
- 60. Circuit breakers Write code with failure in mind Three must haves Request tracing Don’t spend hours debugging Log aggregations Stream all logs into one place.
- 61. DO YOU KNOW YOUR SYSTEM?
- 62. CREATE INSIGHT: AGGREGATED LOGGING
- 63. Response times How much time do services spend calling other services. Back pressure Stop putting pressure on a system that is in trouble and fail fast Fallback How do you handle failure. A mandatory step in the programming model. Circuit breakers
- 64. CREATE INSIGHT: CIRCUIT BREAKERS
- 65. Request TracingX-B3-TraceId : 1 X-B3-SpanId : 1 X-B3-TraceId : 1 X-B3-SpanId : 2 X-B3-ParentSpanId : 1 X-B3-TraceId : 1 X-B3-SpanId : 3 X-B3-ParentSpanId : 2 X-B3-TraceId : 1 X-B3-SpanId : 4 X-B3-ParentSpanId : 3
- 66. TRACE ID’S
- 67. You Build It You Run It The team who builds it looks after it. Ops Team Handover your services and let them deal with the fun. Don’t do this.
- 69. The monolith is deprecated MAKE A STATEMENT
- 70. A CONFLUENCE EXAMPLE Core functionality Scheduler Attachments Operational Transformation Platform Services Front end
- 71. Code Team is responsible for the codebase.Focus on ownership Pipeline Team responsible for CI and Deployment Incidents You built it you run it
- 72. Decomposing core functionality GraphQL service
- 73. What should you take home? Basics Services are cattle not pets. Testing Testing a monolith is “easy” think about your service testing strategy Deployment Deploying a service shouldn’t take longer then 15 minutes Operations You build it you run it. Security Think how you would like to secure service to service communications Focus on value Optimise for rapid and sustainable flow of value
- 74. VINCENT KOK | ENGINEERING MANAGER, TRELLO | @VINCENTKOK Thanks!