4 ms·

I've found that when it doesn't make sense to keep everything in .Net, it's great to break things out into independent services. If there's something awesome yo

by kogir 15y ago

I've found that when it doesn't make sense to keep everything in .Net, it's great to break things out into independent services. If there's something awesome you want to use in Java, like Lucene, expose it as a service and consume it from .Net. In fact, if you do this right, you end up with a bunch of clearly separated re-usable services like in AWS. It also helps prevent the "giant ball of spaghetti" architecture by making it impossible.

chaostheory 15y ago
What if the stuff you want is too small to break out into separate service? e.g. some little util library or even a something like a driver Also if you use a lot of libraries / apps from a specific language, doesn't it make more sense just to transition to that language instead, or does what .NET buy your team worth it to stay?
- kogir 15y ago
  If you find yourself using primarily Java (nothing wrong with that, really), then just go all the way. I think the same is true for most any language. It's also valid to start doing everything new in a new language and gradually migrate away from where you started.
jbigelow76 15y ago
I know it was just a "for instance" but there is a .NET implementation of Lucene, open source and everything. http://incubator.apache.org/lucene.net/ http://incubator.apache.org/lucene.net/ The point being, "no open source community", "license costs" (see bizspark), the "MS is a desktop stack" are all popular myths that haven't been relevant for years. But your point of well defined, independent services is spot on.
- chaostheory 15y ago
  I didn't say "no open source community"; I said super small open source community compared to almost every major alternative. That isn't a myth. It's reality. Moreover Java has a lot more big projects that .NET just doesn't cover. Not to mention we're ignoring the tons of stuff you can find in Ruby, Python, and even PHP.

by kogir 15y ago

chaostheory 15y ago

What if the stuff you want is too small to break out into separate service? e.g. some little util library or even a something like a driver Also if you use a lot of libraries / apps from a specific language, doesn't it make more sense just to transition to that language instead, or does what .NET buy your team worth it to stay?

kogir 15y ago
If you find yourself using primarily Java (nothing wrong with that, really), then just go all the way. I think the same is true for most any language. It's also valid to start doing everything new in a new language and gradually migrate away from where you started.

jbigelow76 15y ago

I know it was just a "for instance" but there is a .NET implementation of Lucene, open source and everything. http://incubator.apache.org/lucene.net/ http://incubator.apache.org/lucene.net/ The point being, "no open source community", "license costs" (see bizspark), the "MS is a desktop stack" are all popular myths that haven't been relevant for years. But your point of well defined, independent services is spot on.

chaostheory 15y ago
I didn't say "no open source community"; I said super small open source community compared to almost every major alternative. That isn't a myth. It's reality. Moreover Java has a lot more big projects that .NET just doesn't cover. Not to mention we're ignoring the tons of stuff you can find in Ruby, Python, and even PHP.