Join
3
2 Comments

Does this architecture look right for updating a static website in real-time?

by Lesley Chang

Here's my previous post regarding this question: https://www.indiehackers.com/post/anyone-know-how-to-go-about-programmatically-publishing-web-pages-3b620e5960?utm_campaign=digest-daily&utm_medium=email&utm_source=indie-hackers-emails

I recently started back on this project and I've taken into consideration everyone's recommendations, but I can't help but feel like something might still be missing...

I've attached an image of the architecture I came up with for this project. (apologies if it's hard to read - let me know if there's anything I need to clarify!)

A TLDR of what the implementation needs to accomplish:

There will be a mobile app for a user who wants to publish a static single web page under our company domain at URL www.company.com/userpage, and the user does this by submitting some data through the mobile app (including a 60 second video) to display on the web page.

As soon as they press "Submit" this web page should be immediately available at the URL www.company.com/userpage for them to view.

Hoping my approach in the diagram is correct, as I'll be implementing this starting tomorrow, but I'm worried it's not the best way to go about this...

This should be a read-heavy service, since many more people will be viewing the URL www.company.com/userpage than there will be users creating new pages via our mobile app.

Thanks so much!!! I'd really really appreciate your input. :)

Lesley Chang's avatarLesley Chang
on November 9, 2020
Say something nice to rasreee…
Post Comment
  1. 1

    Feel free to ignore this comment if I've made some incorrect assumptions! 😅

    It sounds like you might be building a web app for the first time?

    If that's the case, I wouldn't worry about public/production architecture for the time being. Just get your app working locally. When you are ready to deploy it to production there are many "zero config" options available to you and you won't have to worry about specific pieces of architecture.

    The reason I made this assumption is because your questions are mostly around application logic. They aren't really anything to do with architecture - you could deploy the logic you're describing onto any architecture really.

    So if you need a push in the right direction regarding application logic, here's how I would build what you're describing (LinkTree-like service), in Ruby on Rails:

    rails new

    1. create a User model with an auth library e.g. Devise
    2. create a Links model
    3. User has_many Links
    4. allow current_user to create Links
    5. when someone visits route /users/:id display that User's link list

    Then I would run git push heroku master and my app would be live and usable by anyone. I didn't have to worry about architecture :)

    YMMV when using a different framework but the principles are all the same. Good luck!

    yongfook's avatar yongfook
    ·
    6 years ago
    ·
    Reply
  2. 1

    This looks like it's going in the right direction, but there are a few important details that are not clear from this sketch:

    • How is the user interacting with the CMS? The sketch only shows it interacting with the CDN.
    • I don't understand the "routes the rendered content to whatever we want" part.

    Again, this looks like the right approach, but it's hard to say for sure without some more details.

    zanderle's avatar zanderle
    ·
    6 years ago
    ·
    Reply