Databases are at the heart of most business and web apps. If you’re considering using Go for your next project, one of the first things you’re going to look at is whether or not it has an integration for your current database (DB).
Software design is about representation: how do we represent the solution to a problem in code that can be executed on the machine of our choice? How do we represent the problem domain to the user? The software design problem is not inherently different from the problem of expression in any language, formal or informal.
Now that you have ActiveGo installed (and if you haven’t downloaded it yet - you can get it here www.activestate.com/activego) - let’s quickly go over some of the great features available out of the box to help you get started developing with Go:
Some of the world’s largest and most innovative companies have turned to Go to be the underlying technology to drive value for their customers. Netflix, BBC, Facebook, Docker, Atlassian, and the company that brought Go to life, Google. And why not? It is quick to learn, easy to master, and above all easy to maintain by individuals all the way up to large teams of engineers. On top of that, the Go community is welcoming with an inclusive and friendly culture--always wanting to continually innovate on the technology.
Last week I had the pleasure of attending the GolangVan Meetup, the Vancouver group devoted to all things Go. Hootsuite graciously hosted 44 gophers to celebrate the release of 1.8 - it was great to see the interest and growth of Go in the Vancouver tech community. This was one of over 70 release parties world-wide.
As a followup to yesterday’s announcement that we’ve selected Go as our first new distribution in 2017, I’d like to elaborate on why we chose to develop an ActiveGo™ distribution, and why we believe it’s such a good language for the enterprise.
It's been a little over a year since the sale of our Stackato business to HPE, and during this time we've been working hard on the next phase of ActiveState. As mentioned in one of my prior blog posts, we wanted to ensure that whatever we did would unify our company--we didn't want to end up with different business units as we had in the past with our language distributions and Stackato business units.