aleixmorgadas’s avataraleixmorgadas’s Twitter Archive—№ 2,297

      1. I found a problem with this architecture. Long Running Tasks. I'm thinking of extending the architecture to Heroku to deploy those Long Running Tasks. They can be seen as Process Managers. By doing this, I still didn't solve that they are sharing the same DB 😓 Ideas? 🤔 @aleixmorgadas/1543588956788473857
        Permalink On twitter.com Twitter logo aleixmorgadas’s avatar ❤️ 3 Favorites Mood -2 🙁
    1. …in reply to @aleixmorgadas
      The connection between Vercel and Heroku can be secured by Auth0 with a Machine-to-Machine communication. Thinking also on: - Moving the full API logic to Heroku. - Vercel/Next API acts as a secure proxy to Heroku. - It can REST or GraphQL based That would solve the shared DB
      Permalink On twitter.com Twitter logo aleixmorgadas’s avatar Mood +6 🙂
  1. …in reply to @aleixmorgadas
    This still can be $0 MVP fully serverless. It's very nice to have property ☺️💸
    On twitter.com Twitter logo aleixmorgadas’s avatar Mood +3 🙂
    1. …in reply to @aleixmorgadas
      This is due to a limitation of Vercel Platform. They don't support Long Running Tasks nor Cron Jobs. There's a small hack of using GitHub Actions by doing a Cron Workflow that calls a Vercel endpoint to trigger that behavior if the duration is less than 5min in the paid plan 🤣
      Permalink On twitter.com Twitter logo aleixmorgadas’s avatar Mood -3 🙁