I don't prefer to do that through the client-side, it's okay to add a button to that run it, just imagine these cases:

• You have 3 users, so this task will run about 3 times every hour, what about more?
• You have no users, so the task will never run.

I prefer to do that from the server-side, and you can update the time through an API to get the latest time or you can add a WebSocket to make it always updated.

A database cleanup task should indeed be run on the server side periodically. In Java projects where I have participated, we have done similar tasks with Tomcat or Jetty using ServletContextListener. Other servers, e.g. node, have their own mechanisms of course.

You create a class implementing this interface, whose methods get called when your servlet is started or destroyed. In the startup method you create a thread that cleans the db up in a loop every hour, until the servlet is destroyed:

import java.util.concurrent.ExecutorService;
import java.util.concurrent.Executors;

import javax.servlet.ServletContextEvent;
import javax.servlet.ServletContextListener;
import javax.servlet.annotation.WebListener;

@WebListener
public class DBCleanupContextListener implements ServletContextListener
{
    private ExecutorService threadPool;
    private DBCleanupTask dbCleanupTask;

    public DBCleanupContextListener()
    {
        threadPool = Executors.newFixedThreadPool(Runtime.getRuntime().availableProcessors());
        dbCleanupTask = new DBCleanupTask();
    }

    @Override
    public void contextInitialized(ServletContextEvent arg0)
    {
        threadPool.execute(dbCleanupTask);

        // submit additional tasks here if needed...
        
    }

    @Override
    public void contextDestroyed(ServletContextEvent arg0)
    {
        dbCleanupTask.shutdown();
        threadPool.shutdown();
    }

    class DBCleanupTask implements Runnable
    {
        boolean finished = false;
        
        @Override
        public void run()
        {
            while (!finished)
            {
                
                System.out.println("db cleanup code goes here ....");
                
                try
                {
                    Thread.sleep(60 * 60 * 1000); // sleeps 1 hour = 60min*60sec*1000ms
                }
                catch (InterruptedException e)
                {
                    finished = true;
                }
            }
        }
    
        public void shutdown()
        {
            finished = true;
        }
        
    }
}

I have run this code with Tomcat, Jetty and Spring Boot. Theoretically it should run on any JavaEE server, but you need to research how to configure the servlet. On Tomcat for example it needs to be added to the web.xml, as described here:

<web-app ...>
<listener>
    <listener-class>
            com.example.DBCleanupContextListener 
        </listener-class>
</listener>
</web-app>

1 Yes, Component data get erased when you navigated from one component to another. if you want to do something before the component getting destroy you can use the ngOnDestroy Lifecycle method of the component.

2 you can use the service to store data while navigating between components.