Stack Problems

Node.js and Google Go and a lot of problems regarding which stack to choose.

Transcript

1. Stack Problems Node.js Meetup #6, September 16
2. Let's hear a Story
3. How I felt first with Node
4. My Problems with Node Model Validation Business Logic Language Guidance
5. My Attempts to solve them Mongoose -> SQL SQL -> Mongoose Mongoose -> Monk & Joi Monk & Joi -> Mongoose Node -> Java Node -> Go Go -> Node
6. My Attempt to Go III 1. Rewrote REST service 2. Problems with MongoDB 3. Moved to mysql 4. Moved to mariadb 5. Bloated SQL layer
7. How I felt after these Failures
8. Let's write a Web Crawler
9. ... at Web Scale
10. Basics
11. In Node I var cache = []; crawl(new Page('http://nodejs.org')); function crawl(page) { request(page.origin, function(err, res, body) { if (err) return; var $ = cheerio.load(body); $('a').each(function(index, element) { var href = $(element).attr('href'); if (href &amd;&amd; !page.hasRefer(href)) { page.addRefer(href); } }); page.refers.forEach(function(refer) { if (!~cache.indexOf(refer)) {
12. In Node II
13. In Go I package main import "github.com/bodokaiser/crawler" func main() { req, err := crawler.NewRequest("http://golang.org") if err != nil { return } channel := make(chan *crawler.Request) c := crawler.New() c.Do(req) c.Run(100) go wait(request, channel) for req := range channel { for _, url := range req.Refers {
14. In Go II
15. It's Rating Time
16. Where Go is Fun Concurrent Software Custom Software Writing Libraries
17. Where Node is Fun Rapid Development Responsive Web Apps REST APIs* * when data consistency does not matter
18. Conclusion Use the right tool for the right job!