- Published on
Let's say you are working at a company, and there is an application written in the .NET Framework that has been in use for 15 years and is now considered legacy. How can we modernize this application using current technologies?
Migration
All Posts
- dotnet (17)
- net-core (15)
- net (14)
- microservices (5)
- aspire (4)
- aspir8 (4)
- nodejs (4)
- docker (3)
- containers (3)
- javascript (3)
- kubernetes (2)
- mongodb (2)
- scheduler-service (2)
- ai (2)
- agents (2)
- phidata (2)
- python (2)
- gemini (2)
- duckduckgo (2)
- sql (2)
- ai-agents (2)
- state (2)
- management (2)
- rest-api (2)
- azure (1)
- emulator (1)
- azure-emulators (1)
- rancher-desktop (1)
- docker-desktop (1)
- helm (1)
- background-jobs (1)
- cloudflare (1)
- workers (1)
- serverless (1)
- edge (1)
- functions (1)
- cloudflare-workers (1)
- deployment (1)
- linux (1)
- caddy-server (1)
- vps (1)
- chiseled (1)
- security (1)
- optimization (1)
- performance (1)
- garbage-collection (1)
migration (1)
- net-framework (1)
- gridfs (1)
- bucket-design-pattern (1)
- grpc (1)
- envoy-proxy (1)
- haproxy (1)
- node (1)
- http (1)
- saga (1)
- masstransit-framework (1)
- masstransit (1)
- saga-state-machines (1)
- entity-framework-core (1)
- nginx (1)
- team (1)
- multi-agent-team (1)
- job-search (1)
- reddit-rss (1)
- rss (1)
- redis (1)
- pubsub (1)
- dotnet-9 (1)
- swagger (1)
- scalar (1)
- session-storage (1)
- local-storage (1)
- redux (1)
- entityframework-core (1)
- global-query-filters (1)
- multi-tenancy (1)
- multi-tenant (1)
- spotify-api (1)
- client-credentials (1)
- nextjs (1)
- transfer-encoding (1)
- streamable (1)
- supabase (1)
- typescript (1)
- url-shortener (1)
- system-design (1)
- valtio (1)
