search

eligosource / eventsourced

A library for building reliable, scalable and distributed event-sourced applications in Scala
Apache License 2.0
828 stars 98 forks source link

Add artifacts to Maven Central #42

Open krasserm opened 11 years ago

amitpa-nrift commented 10 years ago

Hi can you please add the eventsourced artifacts to Maven Central...we are usinng Maven with java..and SBT is out of scope for us..thanks for the great work.

krasserm commented 10 years ago

http://repo.eligotech.com/nexus/content/repositories/eligosource-releases/ is a Maven repository. Should be straightforward to fetch dependencies from there.

amitpa-nrift commented 10 years ago

Hi Martin,

Many thanks for the reply. I understand that this is a maven repo, and I can fetch the dependencies from there. For now we are doing just that. But it will be great if you can publish the repos in maven central, as we already fetch some of our dependencies from there, and which is likely to remain constant in case you move your repos.

Also it took me a while to find the link, which you posted, (had to browse the sbt build code). I think it will be helpful if you add a maven installation part in the installation guide.

Again thanks for the great work...its also nice to know that eventsourced will become akka persistence.

regards, Amit

On Tue, Oct 15, 2013 at 1:59 PM, Martin Krasser notifications@github.comwrote:

http://repo.eligotech.com/nexus/content/repositories/eligosource-releases/is a Maven repository. Should be straightforward to fetch dependencies from there.

— Reply to this email directly or view it on GitHubhttps://github.com/eligosource/eventsourced/issues/42#issuecomment-26317199 .

krasserm commented 10 years ago

... and which is likely to remain constant in case you move your repos.

expect the Eligotech Maven repo to be stable. Should it change, you'll find the artifacts in central before. I'm just too busy right now working on that.

Also it took me a while to find the link, which you posted, (had to browse the sbt build code). I think it will be helpful if you add a maven installation part in the installation guide.

Would you like to contribute that to the Wiki?

Again thanks for the great work...its also nice to know that eventsourced will become akka persistence.

You're welcome and yes, it's great to have a tighter integration into Akka. Btw, akka-persistence is a complete re-write. Not so many similarities with eventsourced any more (except the concepts of course)

amitpa-nrift commented 10 years ago

Hi Martin,

Thanks for your assurance, indeed if the repo remains stable it is not an issue. And infact if we do find it in central before it is moved it will be okay.

If you are okay, I will simply like to add the maven configuration for eventsourced in the installation guide.

Interesting to know that akka persistence is a complete rewrite, we are planning to use eventsourced for our app , will it be maintained further? (After Akka persistence) If not can we use akka persistence in production soon?

Do you mind letting us know what are salient features of each at this point and are the pros and cons for either.

Thanks for your time and patience.

Regards, Amit

On Tue, Oct 15, 2013 at 8:48 PM, Martin Krasser notifications@github.comwrote:

... and which is likely to remain constant in case you move your repos.

expect the Eligotech Maven repo to be stable. Should it change, you'll find the artifacts in central before. I'm just too busy right now working on that.

Also it took me a while to find the link, which you posted, (had to browse the sbt build code). I think it will be helpful if you add a maven installation part in the installation guide.

Would you like to contribute that to the Wiki?

Again thanks for the great work...its also nice to know that eventsourced will become akka persistence.

You're welcome and yes, it's great to have a tighter integration into Akka. Btw, akka-persistence is a complete re-write. Not so many similarities with eventsourced any more (except the concepts of course)

— Reply to this email directly or view it on GitHubhttps://github.com/eligosource/eventsourced/issues/42#issuecomment-26343544 .

krasserm commented 10 years ago

If you are okay, I will simply like to add the maven configuration for eventsourced in the installation guide.

Yes, please.

Interesting to know that akka persistence is a complete rewrite, we are planning to use eventsourced for our app , will it be maintained further? (After Akka persistence)

Yes, for bug fixes but no new feature development (except minor high-prio features for existing production deployments)

If not can we use akka persistence in production soon?

A first Akka 2.3-M1 milestone should be out in a couple of days. That's a good opportunity to use and give feedback. Expect a hardened version by the end of the year.

Do you mind letting us know what are salient features of each at this point and are the pros and cons for either.

I recommend to switch to akka-persistence, as it dramatically simplifies recovery even in a distributed setup. In it's current state, akka-persistence is still missing a production-ready journal and reliable channels but this should be available within the next few weeks. More at http://doc.akka.io/docs/akka/snapshot/scala/persistence.html. Special event sourcing support, in addition to command sourcing, should be in very soon (pull request currently in review).

amitpa-nrift commented 10 years ago

Okay,I will add the changes by tomorrow...

Its good to hear that eventsourced will be maintained. Isnt it a better idea to make Akka persistence a standard and eventsourced a place to try out new ideas, that way the best will eventually get moved to akka, and eventsourced work will also be used.

Now we want to to be in production by Novemeber max by December mid, so it will be difficult for us to switch to akka-persistence at this time front. We aim to use leveldb with eventsourced. The other alternative in our use case was Twitter Storm (we needed atleast once guarenteed delivery), but we found that for our use case eventsourced and akka fit nicely.

A tricky decision infact, hopefully once akka persistence is production ready we can replace eventsourced wih it.

On Wed, Oct 16, 2013 at 12:24 PM, Martin Krasser notifications@github.comwrote:

If you are okay, I will simply like to add the maven configuration for eventsourced in the installation guide.

Yes, please.

Interesting to know that akka persistence is a complete rewrite, we are planning to use eventsourced for our app , will it be maintained further? (After Akka persistence)

Yes, for bug fixes but no new feature development (except minor high-prio features for existing production deployments)

If not can we use akka persistence in production soon?

A first Akka 2.3-M1 milestone should be out in a couple of days. That's a good opportunity to use and give feedback. Expect a hardened version by the end of the year.

Do you mind letting us know what are salient features of each at this point and are the pros and cons for either.

I recommend to switch to akka-persistence, as it dramatically simplifies recovery even in a distributed setup. In it's current state, akka-persistence is still missing a production-ready journal and reliable channels but this should be available within the next few weeks. More at http://doc.akka.io/docs/akka/snapshot/scala/persistence.html. Special event sourcing support, in addition to command sourcing, should be in very soon (pull request currently in review).

— Reply to this email directly or view it on GitHubhttps://github.com/eligosource/eventsourced/issues/42#issuecomment-26396521 .

krasserm commented 10 years ago

Isnt it a better idea to make Akka persistence a standard and eventsourced a place to try out new ideas, that way the best will eventually get moved to akka, and eventsourced work will also be used.

That's what it actually is. With eventsourced we experimented with new ideas which have now been adopted by Akka/Typesafe. There will be add-on projects at Eligosource, that offer new features on top of akka-persistence. For example, we will migrate the journals to be compatible with akka-persistence. Other ideas and contributions are welcome, of course.

amitpa-nrift commented 10 years ago

Hi Martin,

I changed the doc some time back..I have posted a query in EventSourced user forum. Please do reply when you have time.

On Wed, Oct 16, 2013 at 3:49 PM, Martin Krasser notifications@github.comwrote:

Isnt it a better idea to make Akka persistence a standard and eventsourced a place to try out new ideas, that way the best will eventually get moved to akka, and eventsourced work will also be used.

That's what it actually is. With eventsourced we experimented with new ideas which have now been adopted by Akka/Typesafe. There will be add-on projects at Eligosource, that offer new features on top of akka-persistence. For example, we will migrate the journals to be compatible with akka-persistence. Other ideas and contributions are welcome, of course.

— Reply to this email directly or view it on GitHubhttps://github.com/eligosource/eventsourced/issues/42#issuecomment-26406735 .

krasserm commented 10 years ago

@amitpa-nrift thanks for adding to the Wiki. Made some minor edits ...

amitpa-nrift commented 10 years ago

Yep saw them....:)

On Thu, Oct 24, 2013 at 2:04 PM, Martin Krasser notifications@github.comwrote:

@amitpa-nrift https://github.com/amitpa-nrift thanks for adding to the Wiki. Made some minor edits ...

— Reply to this email directly or view it on GitHubhttps://github.com/eligosource/eventsourced/issues/42#issuecomment-26974865 .