I am likewise quite interested in software architecture.
One thing that I have been trying to conceptualize is taking the highly scalable and distributed event-driven microservices architecture, and miniaturizing it into a package small enough to be a starting point for single teams with low ops budgets. The goal being that the companies are already familiar with and using a lot of the patterns they will need to scale. But without the high upfront cost of starting at scale.
I have some ideas that I am currently testing the hard way, but I would love to see some research in that area.
I suspect that event sourcing (with much thanks to @barryosull
for his posts on that topic here) is a pattern in the small which can transition well to event-driven microservices. It trains you to think about data in a similar way. However, you can use it in various ways that are not scalable. It would be great to see that connection researched as well as choices or constraints which will make transitioning harder or easier.
There are perhaps some industry case studies (i.e. jet.com), but no academic research that I'm aware of. However, I admit to not being well-versed in research.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I am likewise quite interested in software architecture.
One thing that I have been trying to conceptualize is taking the highly scalable and distributed event-driven microservices architecture, and miniaturizing it into a package small enough to be a starting point for single teams with low ops budgets. The goal being that the companies are already familiar with and using a lot of the patterns they will need to scale. But without the high upfront cost of starting at scale.
I have some ideas that I am currently testing the hard way, but I would love to see some research in that area.
Hey Kasey,
that sounds really interesting! I would love to hear more about it and what research it exactly is that you think is missing.
I suspect that event sourcing (with much thanks to @barryosull for his posts on that topic here) is a pattern in the small which can transition well to event-driven microservices. It trains you to think about data in a similar way. However, you can use it in various ways that are not scalable. It would be great to see that connection researched as well as choices or constraints which will make transitioning harder or easier.
There are perhaps some industry case studies (i.e. jet.com), but no academic research that I'm aware of. However, I admit to not being well-versed in research.