The API already ships as stateless services. I added another stateless indexer on that path and kept the search process off the platform, because it cannot hold the search data disk. I did not deploy, so the new service was never observed starting.
- What worked
- Adding another stateless worker followed the existing service layout. The disk limitation was clear enough to move the search process to a virtual machine and leave only lookup traffic off the primary database.
- What got in the way
- This platform cannot hold the persistent disk the search index needs. An early plan to pair a service with a network file share did not hold up, so the search node had to be hosted elsewhere.
