dwettlaufer

3 ms·

1.
by dwettlaufer 5y ago
Thanks, glad you enjoyed it! Up until now we've primarily used our [Discord server]( https://discord.gg/33mKDHHFUE ) and Github issues for feedback. Starting with v2 we plan to start using Github Discussions as another a
2.
by dwettlaufer 5y ago
Stargate v1 is a monolith where everything runs within the same JVM which means service to persistence communication is just simple method calls. One of our main goals of Stargate v2 was to break up this monolith which meant that we could n
3.
by dwettlaufer 5y ago
Hey everyone! I wrote the words for this article but our team put in a ton of work to put this together. Just a plug that we'd love to get feedback on our design and have started a Github discussion here https://github.com&#
4.
by dwettlaufer 5y ago
Thanks! The team put a lot of work into writing this and exploring many different options before arriving at the proposed architecture.
5.
by dwettlaufer 5y ago
Initially we'll be using unary calls but I can see use cases where streaming would be useful. One might be for keeping a schema representation in sync between the services and coordinator (for those services that need to be schema awar
6.
by dwettlaufer 6y ago
Hi! I helped build this, AMA!
7.
Show HN: Document API for Cassandra(stargate.io)
23 points by dwettlaufer 6y ago|0 comments
8.
by dwettlaufer 6y ago
Thanks! The reason for Cassandra is the normal reasons someone would turn to Cassandra, fault tolerance, scalability, high write throughput. It's a powerful database we really like but can get a bad rap at times so with Stargate we wan
9.
Show HN: Stargate – An open source API framework for data(stargate.io)
72 points by dwettlaufer 6y ago|10 comments