Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #12661

G

Glenn Engstrand

Personal blog · glennengstrand.info · on HN as gengstrandprogrammingsystems

Glenn Engstrand's personal blog at glennengstrand.info covers programming and systems. Since 2014, 6 different Hacker News readers have linked it 39 times, most often “Micro-Services: Scala vs. Clojure”. No feed was found, so read it on the site itself.

No feed foundVisit the blog
39mentions?
6HN people?
2014–2025first – last linked?
Links on Hacker News per year · peak 6 in 2018

personal blog site

The author on HN?

gengstrand · 157 karma · member since 2008

Advising 12 factor cloud native architectures with less complexity and more scalability for improved performance, lower cloud bills, lower maintenance costs, faster time to market, and more secure. Current interests include AI (both predictive and generative), distributed consensus, and open source. Currently exploring how LLMs can enhance and augment the developer experience. You can contact me at media at glennengstrand.info

From their public HN profile, which links to this site.

Most-linked posts?

  1. Micro-Services: Scala vs. Clojure
    3 people · 3 mentions · first linked 2016-01-04

What Hacker News says?

  1. Whenever I evaluate a technology stack for microservice architecture viability, I implement the same feature identical polyglot persistent microservice then run it through the same load test as all the others. In that way, I can compare and contrast these various technology stacks. I blog about the results here. http://glennengstrand.info So far, I have covered clojure on ring, scala on finatra, java on dropwizard,…

    Comment linking /

    on “Ask HN: What are good solo developer blogs that you enjoy reading?”
  2. Submitted Revisiting Scala as a story · 4 points

    HN discussion
  3. > BTW, the author claims Go is faster than Java. Is this true, because it didn't used to be? I very recently ran an evaluation that included load testing feature identical business focused microservices written in both Java and Go. These are IO bound processes. The results are that, in this context, Go is on par with Java when it comes to performance (i.e. throughput and latency). http://glennengstrand.info/software…

    Comment linking /software/architecture/microservice/golang

    on “Why Go and Not Rust?”
  4. Submitted Micro-Services: Scala vs. Clojure as a story · 4 points

    HN discussion
  5. I really appreciate the overall gist of this blog and find value in the mech suit vs human replacement analogy. The "near zero time" observation is not consistent with my own findings which I have blogged about at https://glennengstrand.info/software/llm/migration/java/type... and covers a more specific use case of service migration. Using LLMs did cut the heads down coding time by two thirds but certainly not to ze…

    Comment linking /software/llm/migration/java/typescript

    on “LLM-powered tools amplify developer capabilities rather than replacing them”
  6. Submitted Micro-Services: Scala vs. Clojure as a story · 4 points

    HN discussion
  7. In this blog https://glennengstrand.info/blog/ I implement feature identical rudimentary polyglot persistent news feed microservices in various programming languages and tech stacks then compare them with previous implementations in terms of architecture, design, coding, and performance under load. I currently have 13 implementations of that same back end service in a freely available public github repo.

    Comment linking /blog/

    on “Ask HN: Great Blogs by Programmers”
  8. Submitted Building Better Microservices with Machine Learning as a story · 3 points

    HN discussion
  9. I also wanted to understand why GQL was getting so much attention in a REST vs GraphQL way so I implemented a GQL microservice that had the same features as a service that I had implemented previously as REST. Both services ran on node.js and connected to the same data stores, etc. I ran both services on the same load test lab and documented my findings at https://glennengstrand.info/software/architecture/microservi…

    Comment linking /software/architecture/microservice/graphql

    on “Best practices for REST API design (2020)”
  10. Submitted Micro-Services: Scala vs. Clojure as a story · 3 points

    HN discussion
  11. I recently blogged about a comparative evaluation of the three technologies you identified as cross platform (Flutter, React Native, Ionic) over at https://glennengstrand.info/software/architecture/ionic/reac... by implementing a feature identical PoC app in each tech stack. The value of cross platform toolkits is all about cost reduction. It is cheaper to staff up on a single skill set rather than to staff up on th…

    Comment linking /software/architecture/ionic/react/flutter

    on “Flutter is the most popular cross-platform mobile SDK”
  12. Submitted Writing Reactive Microservices for the JVM as a story · 2 points

    HN discussion
  13. I maintain a github repo where I implement a feature identical polyglot persistent microservice in various programming languages and tech stacks then I put each implementation through the same load test lab where I collect then analyze the performance results and draw comparatives. I blog about my findings here. https://glennengstrand.info/blog/

    Comment linking /blog/

    on “Ask HN: What are some great engineering blogs?”
  14. Submitted EKS vs. GKE as a story · 2 points

    HN discussion
  15. I started playing around with Clojure back in 2014 by implementing a rudimentary polyglot persistent news feed microservice. That microservice used Ring which sits on top of Jetty. I blogged about that implementation at https://glennengstrand.info/software/architecture/oss/clojur... which is my personal blog. Last year, I re-evaluated Clojure with a feature identical microservice. This time, I integrated with Donkey…

    Comment linking /software/architecture/microservice/clojure/vertx

    on “Try Clojure – An interactive tutorial in the browser”
  16. Submitted Micro-Services: Scala vs. Clojure as a story · 2 points

    HN discussion
  17. Go did rise to prominence by being the programming language behind such high profile software as Kubernetes, Docker, and Prometheus. None of those are business applications and Rob Pike (ex Bell Labs guru and co-inventor of Go) gave a presentation about Go in 2015 where he explicitly identified that Go was invented for infrastructure and not business applications. I have encountered many engineers who are excited ab…

    Comment linking /software/architecture/microservice/golang

    on “Show HN: We wrote a book about building business applications in Go”
  18. Submitted Micro-Services: Clojure vs. Scala as a story · 2 points

    HN discussion
  19. I am surprised that no one here has yet mentioned Clojure in connection with Big Data. At OSCON 2014 ( see http://glennengstrand.info/analytics/fp ), I was first introduced to Cascalog which allows you to write Hadoop map reduce jobs in Clojure. Both Cloudera and Hortonworks support it.

    Comment linking /analytics/fp

    on “Clojure 2014 Year in Review”
  20. Submitted Functional Programming and Big Data as a story · 2 points

    HN discussion
  21. While there are some language features in Scala that are a bit of a buzz kill (see https://glennengstrand.info/software/coding/java/scala for more on that), the OP is mostly complaining about https://en.wikipedia.org/wiki/Dependency_hell The Akka BSL is a big disappointment to me as well but a better name for that would be LightBend isn't fun anymore.

    Comment linking /software/coding/java/scala

    on “Scala isn't fun anymore”
  22. Submitted Scala vs. Java as a story · 1 points

    HN discussion
  23. When comparing programming languages / tech stacks, I am also more interested in the full picture (libraries, complexity, performance) than just differences in syntactic sugar. I use https://github.com/gengstrand/clojure-news-feed as a test bed for such evaluations. There, you will find almost feature identical microservices in clojure using ring with the jetty adaptor and python 3 on flask. The clojure service was…

    Comment linking /software/performance/eks/gke

    on “Why I Switched from Python to Clojure (2016)”
  24. Submitted GraphQL vs. REST as a story · 1 points

    HN discussion
  25. Kotlin does not lock you in and has not locked you in to IntelliJ. About a year ago, I coded up a Kotlin service using VS Code. See https://glennengstrand.info/software/coding/csharp/kotlin for my description of that including how nice the developer experience was under VS Code. The plugin I used was https://github.com/mathiasfrohlich/vscode-kotlin which works like a charm.

    Comment linking /software/coding/csharp/kotlin

    on “Kotlin-Lsp: Kotlin Language Server and Plugin for Visual Studio Code”
  26. Submitted Revisiting Scala as a story · 1 points

    HN discussion
  27. It would not be incorporating ML into your app's code base directly but one way that I incorporate ML is to use it to analyze application performance data in hopes of learning how to improve it. http://glennengstrand.info/software/architecture/msa/ml

    Comment linking /software/architecture/msa/ml

    on “Ask HN: How to incorporate machine learning into day job?”
  28. Submitted DropWizard vs. Ring as a story · 1 points

    HN discussion
  29. > Use Spring for frameworks. Or Dropwizard if you want microservices that are more light weight and performant than Spring. https://glennengstrand.info/software/performance/springboot/... Or Vert.x or Play if you want to code reactive microservices. https://glennengstrand.info/software/architecture/microservi... > No one does inheritance anymore composition's all the rage. Hmmm, that is oversimplification IMHO. When…

    Comment linking /software/architecture/microservice/vertx/play

    on “Java Turns 25 – Whats Next? [pdf]”
  30. Having written https://glennengstrand.info/software/architecture/microservi... which is a blog entitled "GraphQL vs REST" I must admit that I was initially on guard with this blog. In then end, they did compare and contrast GraphQL with REST. I don't wish to go over this article point-by-point but their main arguments against REST seems to me to be this... 1. too many endpoints 2. too much data retrieval 3. too much…

    Comment linking /software/architecture/microservice/graphql

    on “A REST View of GraphQL”

Search all of HN for glennengstrand.info