Microservices, because everyone wants to be cool
•
0 gefällt mir•197 views
By now, nearly every developer has heard about "microservices", and some may even expect it to be nothing more than "this generations SOA" - nothing more than a passing fad... but what does "making microservices" truly mean? What does "implementing microservices" give us? Why should we move away from our (tried and true) monoliths just to align ourselves with the latest buzzword? What are the benefits of having "microservices" in an actively developed Production environments? In the back-office development teams at Coolblue, this is has been implemented by, you guessed it, utilising microservices. In this session, Pat will present how you too can implement microservices with a "fail fast, fail forward" approach to development. By the end of the evening, we hope you will walk away with the knowledge that "using microservices" isn't just an answer; instead it's the beginning of a journey. A journey that Pat will give you some insight into, and equip you - thanks to his failings - with some tips and tricks to avoid the biggest potholes along the way. If you're a developer that's heard all the fanfare for microservices, and wonder why everyone is so keen to jump on board, then let Pat show you a few reasons why you might want to check microservices out for yourself.
Empfohlen
Weitere ähnliche Inhalte
Ähnlich wie Microservices, because everyone wants to be cool
Ähnlich wie Microservices, because everyone wants to be cool (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Microservices, because everyone wants to be cool
- 1. Microservices A fun session at Betabit.
- 2. 2 @phermens Pat Hermens ● Father of two ● Based here in Rotterdam ● Lead Developer at Coolblue ● Still have a soft-spot for VB6 https://hermens.com.au/ or @phermens
- 3. Elke dag een beetje meer...
- 10. Geniet, dus vraag met mate.
- 12. 12 @phermens Microservices is a variant of the service-oriented architecture architectural style that structures an application as a collection of loosely coupled services. In a microservices architecture, services should be fine-grained and the protocols should be lightweight. - https://en.wikipedia.org/wiki/Microservices Formal definition
- 13. 13 @phermens Formal definition (cont.) There is no industry consensus yet regarding the properties of microservices, and an official definition is missing as well. - https://en.wikipedia.org/wiki/Microservices#Details
- 14. 14 @phermens Also known as: ● “The SOA of this generation” ● “RPC, but with HTTP” ● “ESB, without the bus” ● “CQRS, without the discipline”
- 16. 16 @phermens ...In short, the microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery… - https://martinfowler.com/articles/microservices.html A simpler definition
- 17. 17 @phermens An approach to developing a single application as a suite of services, each running in its own process and communicating with a HTTP API These services are built around business capabilities and are independently deployable by a fully automated deployment pipeline My personal understanding...
- 18. 18 @phermens ● single application ● suite of services ● HTTP API ● business capabilities ● independently deployable ● fully automated deployment pipeline Let’s focus
- 19. Mindset
- 30. 30 @phermens ● single application ● suite of services ● HTTP API ● business capabilities ● independently deployable ● fully automated deployment pipeline Lessons learnt
- 31. 31 @phermens ● single application ● suite of services ● HTTP API ● business capabilities ● independently deployable ● fully automated deployment pipeline Lessons learnt
- 34. Methodology
- 45. Microservices
- 66. 66 @phermens Small repos! net-crm-webservice [OrderLogger]> >> git diff --shortstat (git hash-object -t tree /dev/null) 658 files changed, 47452 insertions(+) ---- 658 files 47452 lines of code
- 79. Short break?
- 81. 1. Complexity
- 89. Wikipedia - Vaska's complex
- 95. 2. Speed
- 102. 3. Development
- 116. 4. Discipline
- 127. 5. Alternatives
- 131. You are not Netflix. #wearenotnetflix
- 137. 137 @phermens How?
- 140. 140 @phermens There are other options...
- 141. 141 @phermens There are other ADVANCED options...
- 143. 143 @phermens Please not at the start!
- 145. 145 @phermens KISS - to start Within a single domain Containing single responsibility Implementing one type of endpoint
- 146. 146 @phermens KISS + Growth Within a single domain Containing single responsibility Implementing a few related endpoints
- 159. 159 @phermens Within a single domain containing single responsibility implementing a few related endpoints Inherent Scale Within a single domain containing single responsibility implementing a few related endpoints Within a single domain containing single responsibility implementing a few related endpoints ServiceAServiceBServiceC
- 166. You are not Netflix. #wearenotnetflix
- 167. Short break?
- 168. A few little gotchas
- 170. 170 @phermens Many options; pick one
- 171. 171 @phermens It’s going to fail
- 172. 172 @phermens Use some tools to help
- 174. 174 @phermens Don’t forget monitoring & alerting
- 175. 175 @phermens Just don’t do it like this
- 178. 178 @phermens ...until you need it
- 179. 179 @phermens “Any colour, so long as it’s black
- 182. 182 @phermens Use a common language
- 183. 183 @phermens Have well defined stakeholders
- 184. 184 @phermens ... and talk with them!
- 190. Gewoon doen!
- 191. Meenemen A few short take-aways
- 192. Complexity
- 193. Autonomy
- 194. Consistency
- 195. Resiliency
- 196. Flexibility
- 197. Necessity
- 198. Zo, vraag met mate...
- 199. 199 @phermens Some additional reading ● https://martinfowler.com/articles/microservices.html - A good discussion of Microservices ● Specifically: https://martinfowler.com/bliki/MicroservicePrerequisites.html - Prerequisites for Microservices ● https://vimeo.com/131632250 - Sam Newman talking about Microservice Principles @ NDC Oslo 2015 ● https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-overview-microservices - Great overview ● https://aadrake.com/posts/2017-05-20-enough-with-the-microservices.html - A good companion to the above. ● https://github.com/Microsoft/api-guidelines/blob/master/Guidelines.md - Microsoft’s REST Guidelines ● http://www.thepollyproject.org/ & https://github.com/App-vNext/Polly - Great tool ● https://github.com/Travix-International/Hystrix.Dotnet - An advanced version of Polly … and many more in Google :)