How-To: MicroServices and Service-Oriented Everything

Start Time: Friday, May 15, 2020 8:00 AM
I'll start with a short talk about the business benefits to Service-Oriented. Second I'll move into the reasons why OO should be fired. Then I'll talk about the basic concepts of Service-Oriented. Lastly, I'll show code, charts, and actual application of Service-Oriented in a Micro Ecosystem.

MicroServices should compose every LOB system. MicroServices are the natural result of following all best practices and principles. Object-Oriented programming is the natural enemy of MicroServices, because MicroServices are stateless, whereas OO is a stateful paradigm. For MicroServices, you require a Service-Oriented Architecture. For an SOA, you require Service-Oriented Programming. SOP is the culmination of principles, mixed with some aspects of OO and Functional Programming.

Steven Fletcher, Owner and Architect, WebFletch, INC

StevenFletcher, Steven Fletcher

Steven (Fletch) has been developing web and desktop applications mainly in C++, C#, and .NET since the mid 90's.  PvP Networking and Level Design for DooM, Duke Nukem, and Wolfenstein almost 30 years ago is what sparked an interest in IT. Since then, Fletch has contributed or built systems in many industries including Military, Local Government, Healthcare, Oil and Gas, Finance, and more. It began with DooM and Zelda fan sites, evolved into organizational applications for the US Navy, local government websites, local business websites, and then culminated into the establishment of WebFletch in 2007. Since 2007, Fletch has worked toward expertise in, what he calls; SOLID, Test-Driven, Service-Oriented Architectures with MicroServices. Businesses can hire Fletch for Service-Oriented training, or you can sometimes see him speak at local User Meetups or Conferences.