If you're an experienced developer, just run with it. You'll see the seams and figure out where to split it. Many thinkers in the microservice space consider starting a new application with a monolith and breaking it up when the partitions present themselves as better than trying to start from scratch with different services. I think that logic applies here.
If you're less experienced, start off by putting all the data collection stuff in one package and the rest in another. Go's capital-letter exporting will make the right way a bit more obvious. If you have no idea what you're doing, just run with it. There's no other way to learn. Make it work and use it. Parts will be crappy. Yay! If you have some horrible, half-working thing and ask for specific help with bits of it, I expect the quality of assistance you'd receive on this list will be exemplary. -- 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. For more options, visit https://groups.google.com/d/optout.
