Last week, we published a “move-and-improve” white paper about rearchitecting a monolithic .NET application using microservices. Today, we introduced the next installment in our series about migration entitled “Modernizing your .NET Application for Google Cloud.”
This paper dives into the details of the modernization roadmap. For example, in the previous white paper, we discussed using domain-driven design (DDD) to deconstruct a monolith into microservices. Now, we ramp up the fun with hands-on activities and real-world code samples. You’ll be working through the modernization of critical functions, including authentication, database and caching:
- Authentication – PetShop, our guinea pig application, currently uses the legacy ASP.NET Membership framework for authentication, which needs to be updated to support modern authentication protocols, such as OAuth and OIDC to better support mobile devices and applications.
- Database – PetShop uses Oracle for backend storage, but there are no technical reasons why we can’t use an open-source database like PostgreSQL instead. It may even be less expensive, and possess fewer licensing constraints for cloud computing.
- Caching – PetShop uses in-memory, on-server caching, but cloud-based systems can achieve better resiliency and performance by leveraging a distributed caching engine such as Redis.
By the time you finish with code samples in this white paper, you’ll have breathed new life into PetShop. By adopting technologies like Firebase, PostgreSQL and Redis, you’ll have offloaded a great deal of the maintenance and management to your service providers—in this case, GCP. For example, you’ll no longer have to maintain the ASP.NET Membership framework for authentication, as you’ll have outsourced it to Firebase. Get started today: download the white paper, and clone the GitHub repository.