iPrism Technologies is a global technology and process driven software, web and mobile app development company offering customer centric solutions with knowledge and experience of the entire IT lifecycle, we help enterprises streamline core IT processes and augment their competitive advantage.
Not sure I agree with most of this, but it's interesting to see another's approach to dealing with complexity.
The article correctly identifies complexity as the biggest problem with writing complex long-lived web applications, but then presents a series of ad-hoc solutions to specific problems (problems caused by the structure they have chosen) as the best answer. It would probably be better titled 'Things I learned writing go' or something similar, rather than attempting to frame different decisions trade/offs as anti-patterns.
To take one example, having one user model is good in that it is easier to maintain and less complex to think about, but the author advocates having a write model and an api model - in some circumstances that might be useful (where there are many private fields which must never leak to the view or require processing before presentation), but most of the time it's overkill and needless complexity.
Yes and written by some of the people involved in the original net package. Brad used to be one of the maintainers of net/http and net packages in go. I'm glad they are so conservative about changing the standard library though, even if it does mean warts like this persist.
Our crypto banking software development solution provides all the necessary banking functions that your customers expect from their core banking platform. It is designed to handle all your customers’ needs with secure API, intuitive front-end, and banking modules. To get complete information, visit our website today and get a free white label software demo.
Thanks for posting, this looks really interesting. The main problem I suppose would be deliverability, so you'd have to set up reverse DNS, SPF etc. use a rented server, and perhaps warm up the ip for a while.
Yes. I'm interested in this? Any links and research you want to share? Most localization is done with js and these guys localizejs.com even put it in their domain :) But if there is any Golang solution for this I wouldn't know.
The article does link to that blog post, and points out some problems with it.
I'm not a fan of this design either personally, in particular requiring a v2 suffix, I think it makes assumptions about versioning which don't withstand scrutiny, e.g. that major versions are always used for major breaking changes. In my experience they are more often used to indicate major feature releases.
I'd really rather go kept the culture of no breaking changes rather than explicitly encouraging them if you move past 1.x.
Looks like there's been a bit of work put in. I especially like how there's multiple sql drivers supported. Instructions on how to add slack were especially nice, I'd been somewhat stuck on the legacy keys (now deprecated).