My Weekly Journal - 06
My weekly journal is series of blog posts where I share stories about my professional and personal work. This is my weekly Journal 065, Feb 21, 2021, and in this post, I am going to share with you about:
- ASMX to REST (Web API) and WCF to REST (Web API) migrations
- Loss aversion
- Slow living
ASMX to REST (Web API) and WCF to REST (Web API) migrations
ASMX Services used to be the only way to build web services in Microsoft .net development. Developer used to write code in c# to support various business operations in the service. GetWorkCenterList or GetWorkOrderList etc. are simplest examples of such operations supported by asmx service. The asmx services were published in IIS, and was discovered through WSDL. In order to consume the service, you either generate a proxy through WSDL.exe if you are consuming it in Microsoft .net development or use language specific proxy generation tools in other programming.
I have been doing Microsoft SharePoint Development and used asmx services supported by Microsoft SharePoint 2010 in order to read some lists or libraries in the Microsoft SharePoint Development.
In a nutshell, ASMX Services supported implementation of service oriented architecture in Microsoft .net development.
Due to tightly coupled SOAP dependency, XML serialization, data transformation and protocol specific complexities to implement security etc., Microsoft introduced WCF which was new way to implement service oriented architecture in Microsoft .net development.
WCF provided many advantages over ASMX Services like interoperability, security and reliability, supported plain XML, REST and SOAP and much more. Now you can write programs in Microsoft .net development that supported both tcp based communication, http protocol based communication, REST communication, and SOAP all of it but you can still write code only once. Based on your needs you can enable any type of communication/transport securely.
With rise of .NET Core, Microsoft’s Unclear Plans for Server-Side WCF Continues to Frustrate .NET Developers.
While there is no clear guidelines or help available on this topic, being a Microsoft technology export company, we already started helping our clients in migrating from ASMX and WCF to asp.net web api.
Loss aversion
I came across loss aversion while reading Thinking fast, and slow. In this week, I have been speaking to a friend about this and way to think clearly because due to loss aversion, we feel almost double pain than the amount of happiness we receive when gaining something.
Later during the week, I also find another useful article on loss aversion which may help better understand it.
Applying game theory is another helpful technique in many life situations if you can define your wins and loses clearly.
Slow Living
Ever since I’ve read Ikigai: The Japanese Secret to a Long and Happy Life, The Little Book of Lykke, Lagom: The Swedish Art of Balanced Living, I’m interested more into Slow living and discovering more about the same.
I’m taking regular morning walk since a month now (with some exception days ;)), trying to take small breaks and stay focused through weekly OKRs and trying to avoid parallel work and too much work as much as I can.
See you next week!