4 ms·

The architecture sounds nicely choosen and well executed (according to your comment) but i miss some additional information on your website. Especially about h

by herbst 10y ago

The architecture sounds nicely choosen and well executed (according to your comment) but i miss some additional information on your website. Especially about how you plan to be always online. I see the same issue as with statuspages. Their value is actually more their stable platform than the code they produced, the most important feature the uptime.

richardknop 10y ago
It's a good question. Right now I have microservices running on AWS, in 3 availability zones so it should be resilient to an issue in single or even two zones. Services are also deployed in autoscaling groups so if one of the servers goes down, it will be replaced with a healthy instance. Right now everything is running in us-west-2 region but in the future, if it goes well, I'd like to spread servers across more regions in case there is some big AWS issue in one region. Microservices also cache remote config so if etcd cluster goes down they continue working. Plus I have a very high test coverage so the code should be robust enough. I will think of more things to do in the future. Good idea to add more information to the website. Thank you for the feedback.
- herbst 10y ago
  This sounds better than i even have imagined, clearly put something about that on your website. May also create a business related blog where you can add all these architectural choices in detail. Assuming other potential customers also look for transparency in this. About the databases, i would just make sure to have a plan when it comes so far. I dont think your website will explode in populary over night are you are not _that_ unique, so you most likely will notice it early enough if you watch closely when it is time to switch :)
  - richardknop 10y ago
    Thank you :)
richardknop 10y ago
Another potential issue could be scaling of the database. As I only use one RDS instance now. In case I would have lots of users using my service, which would be a nice thing, I would consider moving from RDS to my own Postgres database (which could be scaled more than RDS) plus moving metrics data to something like InfluxDB.
- markwakeford 10y ago
  Have you considered Aurora ?
  - richardknop 10y ago
    Not yet. I have heard a bit about it. What are the main advantages over Postgres?
    - markwakeford 10y ago
      I am not sure but I figured it would be the easiest to deploy from a scaling perspective.

by herbst 10y ago

richardknop 10y ago

It's a good question. Right now I have microservices running on AWS, in 3 availability zones so it should be resilient to an issue in single or even two zones. Services are also deployed in autoscaling groups so if one of the servers goes down, it will be replaced with a healthy instance. Right now everything is running in us-west-2 region but in the future, if it goes well, I'd like to spread servers across more regions in case there is some big AWS issue in one region. Microservices also cache remote config so if etcd cluster goes down they continue working. Plus I have a very high test coverage so the code should be robust enough. I will think of more things to do in the future. Good idea to add more information to the website. Thank you for the feedback.

herbst 10y ago
This sounds better than i even have imagined, clearly put something about that on your website. May also create a business related blog where you can add all these architectural choices in detail. Assuming other potential customers also look for transparency in this. About the databases, i would just make sure to have a plan when it comes so far. I dont think your website will explode in populary over night are you are not _that_ unique, so you most likely will notice it early enough if you watch closely when it is time to switch :)
- richardknop 10y ago
  Thank you :)

richardknop 10y ago

Another potential issue could be scaling of the database. As I only use one RDS instance now. In case I would have lots of users using my service, which would be a nice thing, I would consider moving from RDS to my own Postgres database (which could be scaled more than RDS) plus moving metrics data to something like InfluxDB.

markwakeford 10y ago
Have you considered Aurora ?
- richardknop 10y ago
  Not yet. I have heard a bit about it. What are the main advantages over Postgres?
  - markwakeford 10y ago
    I am not sure but I figured it would be the easiest to deploy from a scaling perspective.