http://golangnews.com Jobs, Code, Videos and News for Go hackers - everything about the go programming language Tue, 10 Oct 2017 22:08:00 +0000 Today we’re excited to announce the 1.0 release of the open source time series database, InfluxDB and our commercial offering, InfluxEnterprise, which supports high availability deployments and scale out clustering for increased throughput. This makes today the biggest day in our company’s history. This release has been almost 3 years in the making and on this occasion I’d like to take a look back at the project’s history, let users know what compatibility guarantees the 1.x line of releases will have and talk about what’s next for InfluxDB. 12 points posted by kenny https://www.influxdata.com/influxdb-1-0-ga-released-a-retrospective-and-whats-next 1052 Thu, 08 Sep 2016 15:14:00 +0000 This is an idea I’ve been kicking around for a little while, and I’m curious what others think about it. Everyone seems to be talking about microservices these days, but in most projects there is a transition point from monolith to service-based designs. I contend that for new projects you should almost always start with a monolith. I said it seven years ago when I wrote about <a href="https://www.amazon.com/Service-Oriented-Design-Rails-Addison-Wesley-Professional-ebook/dp/B00413PHZU" style="box-sizing: border-box; margin: 0px; padding: 0px; border: 0px; outline: 0px; background: 0px 0px rgb(255, 255, 255); font-size: 16px; vertical-align: baseline; text-size-adjust: 100%; color: rgb(50, 176, 140); font-family: &quot;Open Sans&quot;, Helvetica, Arial, Lucida, sans-serif;">Service Oriented Design with Ruby</a>: if there’s any way you can avoid services, build a monolith. However, making the shift to services later can be quite tricky, so in this post I’ll explore the advantages of a monolith while proposing a way to structure a new project that lends itself to being broken out into services later. I call this design/architecture pattern The Decomposable Monolith. To help illustrate the idea, we’ll work through an example using Go as the implementation language and a next-generation data platform (say for time series data) as the application. 7 points posted by kenny https://www.influxdata.com/blog/decomposable-monolith-long-live-monolith-long-live-services 3036 Thu, 21 Dec 2017 16:19:00 +0000 6 points posted by drogo https://www.influxdata.com/influxdb-1-1-released-with-up-to-60-performance-increase-and-new-query-functionality 1302 Sat, 03 Dec 2016 04:45:00 +0000 4 points posted by kenny https://www.influxdata.com/blog/java-is-the-cobol-of-my-generation-and-go-is-its-successor-and-other-reflections-after-gophercon 3956 Thu, 02 May 2019 15:14:00 +0000 4 points posted by gopher https://www.influxdata.com/modern-time-series-database-in-the-age-of-instrumentation 2197 Thu, 11 May 2017 11:42:00 +0000