{"action":"created","issue":{"url":"https://api.github.com/repos/akka/akka/issues/23564","repository_url":"https://api.github.com/repos/akka/akka","labels_url":"https://api.github.com/repos/akka/akka/issues/23564/labels{/name}","comments_url":"https://api.github.com/repos/akka/akka/issues/23564/comments","events_url":"https://api.github.com/repos/akka/akka/issues/23564/events","html_url":"https://github.com/akka/akka/issues/23564","id":252236184,"number":23564,"title":"Docs - Nice to have reference to `AtLeastOnceDeliverySnapshot` on the Persistence - Snapshots section","user":{"login":"joantune","id":1016580,"avatar_url":"https://avatars1.githubusercontent.com/u/1016580?v=4","gravatar_id":"","url":"https://api.github.com/users/joantune","html_url":"https://github.com/joantune","followers_url":"https://api.github.com/users/joantune/followers","following_url":"https://api.github.com/users/joantune/following{/other_user}","gists_url":"https://api.github.com/users/joantune/gists{/gist_id}","starred_url":"https://api.github.com/users/joantune/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joantune/subscriptions","organizations_url":"https://api.github.com/users/joantune/orgs","repos_url":"https://api.github.com/users/joantune/repos","events_url":"https://api.github.com/users/joantune/events{/privacy}","received_events_url":"https://api.github.com/users/joantune/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2017-08-23T10:35:51Z","updated_at":"2017-08-24T10:39:03Z","closed_at":null,"body":"Hi!\r\n\r\nThis would be nice to have a reference to the `AtLeastOnceDeliverySnapshot` in the Persistence -> Snapshots section in the documentation.  \r\nI almost repeated the `AtLeastOnceDeliverySnapshot` 'manually' until I found out via the methods that such a Snapshot already exists.\r\n\r\n\r\nPS:\r\nIn general the documentation of Akka is a bit discouraging, it isn't as concise as Play's (it's more of a Reference one) and one has to wonder if that happens because LightBend sells support to Akka - although I would argue that encouraging a better documentation would actually help to use Akka more and of course the enterprises will have a budget for the support and for the enterprise products.\r\n\r\nI would actually open up the Lagom quite like Play is opened, and then simply have an offer to SMBs for access to services and products, instead of locking Lagom to a useless 3 nodes (!) if you want microservices and actors, you're expected to use more than 3, I understand the need to make money out of this, but I think that somehow there's a better way forward. \r\nAlso, you don't know what is the pricing for unlocking Lagom i.e. what's the lightbend subscription and if that value will uphold itself in the future - whenever I see a sales form I guess it's going to be way expensive (and it probably shouldn't for projects that don't make that much money yet, and for the others I'm sure they will be happy to pay more).\r\nThis way you guys are setting yourselves up to becoming irrelevant once easier to use and better documented solutions like Microsoft Orleans are ported to Java"},"comment":{"url":"https://api.github.com/repos/akka/akka/issues/comments/324599555","html_url":"https://github.com/akka/akka/issues/23564#issuecomment-324599555","issue_url":"https://api.github.com/repos/akka/akka/issues/23564","id":324599555,"user":{"login":"joantune","id":1016580,"avatar_url":"https://avatars1.githubusercontent.com/u/1016580?v=4","gravatar_id":"","url":"https://api.github.com/users/joantune","html_url":"https://github.com/joantune","followers_url":"https://api.github.com/users/joantune/followers","following_url":"https://api.github.com/users/joantune/following{/other_user}","gists_url":"https://api.github.com/users/joantune/gists{/gist_id}","starred_url":"https://api.github.com/users/joantune/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joantune/subscriptions","organizations_url":"https://api.github.com/users/joantune/orgs","repos_url":"https://api.github.com/users/joantune/repos","events_url":"https://api.github.com/users/joantune/events{/privacy}","received_events_url":"https://api.github.com/users/joantune/received_events","type":"User","site_admin":false},"created_at":"2017-08-24T10:39:03Z","updated_at":"2017-08-24T10:39:03Z","body":"@raboof: I will try to get some time after I hit the milestone that I wanted with a system that I have, but I cannot promise anything as it's basically a one man show ATM. \r\n\r\nIt's good to know that Akka's trying to better the documentation.\r\nMaybe what is needed is some sprinkling of general use cases - like using actors for batch long running jobs, using actors for <insert typical example - REST API (?)> etc, documented, and then the docs as is as reference documentation.\r\n\r\nI didn't know that detail about Lagom. Maybe the glue between Play and Lagom and Akka might be that documentation of Typical use cases and a reference to them from the Play's documentation. Akka is very barebones and has a steep learning curve, which is quite the opposite of Play. Akka can be great but you need to point out the typical use cases and let people figure out the rest.\r\n One of the reasons why I moved away from Spring and into Play was that the docs that I found were of older versions or very 'reference' like. I remember configuring Spring security, and some months later wanted to change something and struggle again to find out how to do that.  "}}
{"actor":{"display_login":"joantune"}}