Hi Everyone, I'm interested in improving my software engineering knowledge and experience with scalable software systems. I currently write software for an environment that's more resource-constrained (think embedded Linux device) where there is typically only one user connected to the device and interacting with the software API at a time. We optimize for efficient interaction with hardware (button events, transcoding, scanning filesystems, thumbnail generation, etc). This is the world in which I've grown as a professional software engineer and I'm looking to expand my knowledge to software applications outside of embedded Linux environments.
'm looking to learn more about designing and implementing larger systems that are designed to handle hundreds or thousands of concurrent users, and I would appreciate any insight on how they learned about this type of software engineering and what resources they found useful. Specifically, I've been asking myself the following questions: - What are some common design patterns used for scalable systems? - What technologies are commonly used for scalable systems? I'm familiar with protocol buffers and Twirp, an RPC library that leverages protobufs. I'd love to learn more about caching, transport mechanisms, and databases. - Are there any books, articles, or other reference material you've found helpful for expanding your knowledge of designing systems at scale? Currently I've started a couple of side projects to explore this space: - A library that monitors the number of open files given one or more PIDs. I would like to build upon this idea by creating a custom exporter/collector for node_exporter so that I could integrate this nicely in an existing monitoring setup. My goal with this project is to connect my knowledge of Linux and the constraints on processes with some common monitoring technologies that might be found in a large software ecosystem. - An AWS Lambda function that interacts with a couple of 3rd party APIs, namely Reddit and Spotify. My goal with this project is to learn a bit about 3rd party API consumption and serverless design. One caveat of which I'm aware is that these thoughts are not very specific to Go, and that often the programming language used to implement an application is part of the solution to a particular problem. I'm just particularly focusing on Go because I'm familiar with it as a systems-level language but would love to learn how Go is used to design larger-scale applications. I'm very open to suggestions with regards to the questions above, or anything else in this space that might be helpful as I start this journey. Thanks in advance for any insight you might be able to share! Cheers, Rob Weber -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/7f45b116-b9a8-44f7-b3d0-fdb4fe23d26c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
