OCTO Technology Blog
blog.octo.com · Company blog · on HN since 2015
The OCTO Technology blog is written by engineers at a French consultancy, covering software architecture, APIs, databases, and web technologies.
What HN saysHN commenters cite it for its hexagonal architecture write-up and a Protocol Buffers benchmark, in discussions of layering and efficient data formats.
15HN people shared it
3linked it in comments
12stories submitted
150story points
5 years agolast shared
2015people per year2026
Most-shared posts
- 1Hexagonal Architecture3 people · 4 points · first shared 2018 · discussion on HN
- 2WebAssembly, an executable format for the web1 people · 128 points · first shared 2017 · 93 comments on HN
- 3How to design a REST API1 people · 7 points · first shared 2015 · discussion on HN
- 4What Redis deployment do you need?1 people · 2 points · first shared 2017 · discussion on HN
- 5Clean Code and Node.js1 people · 2 points · first shared 2018 · discussion on HN
- 6How to Deal with an Inverse Conway Maneuver?1 people · 2 points · first shared 2022 · discussion on HN
- 7KotlinConf 2018 – Our recap1 people · 1 points · first shared 2018 · discussion on HN
- 8OpenShift 3: private PaaS with Docker1 people · 1 points · first shared 2015 · discussion on HN
- 9Strengths and Weaknesses of a Cloud-Hosted Android CI Server1 people · 1 points · first shared 2015 · discussion on HN
- 10POV: A streaming/communication platform for the data mesh1 people · 1 points · first shared 2021 · 1 comments on HN
- 11ScyllaDB vs. Cassandra: towards a new myth?1 people · 1 points · first shared 2015 · discussion on HN
- 12My reading of percolator architecture a google search engine component1 people · first shared 2018
- 13Protocol buffers benchmark and mobile1 people · first shared 2018
What HN people wrote when they linked it
evanweaver · 2018-12-04
For further reading, Dan Abadi's post at http://dbmsmusings.blogspot.com/2018/09/newsql-database-systems-are-fa… addresses the Spanner issues more directly.
I don't think there's a great reference for the Percolator transaction architecture specifically, but there is a brief description here: https://blog.octo.com/en/my-reading-of-percolator-architecture-a-googl…
One thing I learned recently is that FoundationDB is essentially the Percolator model (timestamp oracle), even though FoundationDB predated the Percolator paper.
dangets · 2020-02-01
I am currently a big fan of the hexagonal architecture which is pretty close to what you describe as far as layering.
https://blog.octo.com/en/hexagonal-architecture-three-principles-and-a…
https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architectur…
I also advocate for packaging by feature rather than layer (each feature defines its layers)
https://hackernoon.com/package-by-features-not-layers-2d076df1964d
imtringued · 2018-05-16
Then use compression. gzipped json is highly efficient over the wire.
https://blog.octo.com/en/protocol-buffers-benchmark-and-mobile/
The primary purpose of binary data formats is that they can be parsed quickly and some even allow direct access without a parsing step.