Very nice project! Curiousity question: since you are taking data dumps once-twice a year, and let's say you also copy the photos as well, do you do any updates incrementally or just replace the old one with new dump?
What is your target market? Is it database companies, cloud providers etc. that implements a proper distributed architecture? If it is not limited to that, what would be the value Antithesis can provide to a company that utilizes a small-scale service oriented architecture that has its own share of distributed complexity?
Database vendors are very natural customers, because they're distributed systems for whom correctness and uptime are paramount. But they're far from our only customers! We have tons of people who are doing exactly what you describe -- running a client-server architecture or a collection of microservices that need to be fault-tolerant.
One of our theses is that the vast majority of real world "distributed systems developers" would never describe themselves that way and don't read the same blogs that all the database people do. Nonetheless, these people are writing distributed systems, and share the pain that we've all experienced. One of the most important tasks ahead of us is precisely to reach this vast "distributed systems dark matter" and explain to them how it is that we can help their day-to-day jobs.
It's good that the author provided use cases, why they needed the project etc.
Frankly, I didn't get the difference from basic Go templating looking at the quickstart examples. If it has any advantage over, they should state it clearly.
Thank you for feedback!
Right, Quick Start does not represent any advantages. To show that advantages, example needs to be more complex.
We are working now on providing better quick start experience + demo project, that can be used as starter.
Main reason of posting library in media: share our idea and motivation :)
Sorry, if you're confused with our docs, we are working hard on it now.
I've just checked the Cloud Infrastructure section and couldn't see your point there. There are readings for fundamentals, then basic practices, then online courses in udacity and kube-bootcamp, then step-by-step guides to deepen the knowledge.
I think they have accomplished a good thing here: a curated list of sources to get into the cloud computing/infrastructure world.
I don't think they can talk about every step in the development lifecycle, it would be very very opinionated. It leaves the reader/developer no space for elasticity and freedom of choice to what to learn/practice. After acquiring the fundamentals, we should all choose our own path by discovering.
