Building microservices .net - Dublin Microservices UG 20160928
•Download as PPTX, PDF•
1 like•739 views
In this talk, I will demo how we can build deploy and monitor a couple of (micro) services using the .NET platform. On the Java platform, we have a LOT of options to implement micro services, this is not the case on the .Net platform, let's look how we can do this using .Net tools like NServiceBus and Octopus Deploy
Recommended
Recommended
More Related Content
More from Sean Farmar
More from Sean Farmar (11)
Recently uploaded
Recently uploaded (20)
Building microservices .net - Dublin Microservices UG 20160928
- 1. Building (micro) Services On .Net Sean Farmar @farmar
- 2. Why Microservices? Break down the monolith
- 3. Fallacies of Distributed Computing 1. The network is reliable. (Bill Joy and Tom Lyon) 2. Latency is zero. (Bill Joy and Tom Lyon) 3. Bandwidth is infinite. (Bill Joy and Tom Lyon) 4. The network is secure. (Bill Joy and Tom Lyon) 5. Topology doesn’t change. (Peter Deutsch) 6. There is one administrator. (Peter Deutsch) 7. Transport cost is zero. (Peter Deutsch) 8. The network is homogeneous. (James Gosling)
- 4. The Fallacies EBook • Go to: http://go.particular.net/dublinmu
- 5. Why SOA / Microservices? “Address coupling in our software design by building loosely coupled and highly encapsulated components” Udi Dahan
- 6. Coupling • Synchronous communication (Request Response) • Resource sharing (data, code) • Coupling Aspects (Temporal, Spatial, Platform )
- 7. Decomposition • Breaking down functionality into small autonomous components (vertical slicing) • CQS/CQRS • Inter components communication? • Messaging
- 8. Tools in .Net • Akka .net/ Orleans (actor frameworks) • MassTransit • Re-bus • NServiceBus (particular.net) • Build your own
- 9. Functionality • Submit Order • Wait for Buyer’s Remorse • Ability to Cancel Order (within buyer’s remorse) • Process Order (charge credit card) • Provision Download • Make Customer preferred • Send Welcome Email • Send Limited Time Offer Source code: https://docs.particular.net/samples/show-case/on-premise/?version=Core_6
- 11. Components Submit Order Notify: Order Placed Buyer’s Remorse Optional: Cancel Order Process Order Provision Download Make Customer preferred Send Limited Time Offer Send Welcome Email
- 12. Sample code walk through • Boundaries and responsibilities • Website • Code structure • Visualization
- 13. Debugging • Debugging Messaging • Sagas • Errors • http://particular.net/serviceinsight
- 14. Debugging Demo
- 15. Monitoring • System Monitoring • Business Monitoring • Messaging • http://particular.net/servicepulse
- 17. Build & Deploy • Build Nuget Packages • Octopus Deploy
- 18. Q&A Thank You! Sean Farmar twitter: @farmar Particular.net
Editor's Notes
- 2 min. The fallacies of distributed computing describe common assumptions that are made by developers and architects in distributed systems. In 1994 Peter Deutsch wrote down seven fallacies. In 1997 James Gosling added another fallacy. These fallacies are known as “The eight fallacies of distributed computing”. In the year 2006 Ted Neward added three more fallacies, which are not so widely known. The system is atomic/monolithic. (Ted Neward) The system is finished. (Ted Neward) Business logic can and should be centralized. (Ted Neward)
- 1 min.
- 1 min.
- 1 min.
- 1 min.
- 1 min.
- 1 min.