|
is “the de facto standard searching algorithm for P2P (peer-to-peer) networks on the Internet.” Kademlia is a protocol specification for decentralizing peer-to-peer network operations, efficiently storing and retrieving data across the network.
Okay Marc, I'd like a bit of context, if you don't mind. How did you wander into this subject matter such that a book popped out?
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
charlieg wrote: How did you wander into this subject matter such that a book popped out?
I've been interested in the tech behind things like cryptocurrency (blockchain, proof of work, Merkle trees, etc.) and P2P was one of the puzzle pieces. Also, supposedly "distributed data" is one of the emerging newfangled waves and I wanted to learn more about how that all works, pros and cons, etc.
I poked around looking at various P2P implementations and the Kademlia Protocol kept popping up as the defacto standard for distributing data across a P2P network. I thought, cool, how hard can this be. Riiight.
What I found was the typical morass of contradictory protocols (there was an earlier version of Kademlia that seems to have been removed from the web at this point but that a variety of people appear to have implemented), contradictory/confusing statements within the protocol definition itself, and a LOT of really bad (buggy or just plain unfinished) open source implementations.
The standard implementation in the *nix world appears to be libp2p with various language ports (who knows how well implemented) but none in C#. Ah ha! Opportunity!
So what I thought would be a simple and short article for CodeProject turned out to be a large investigation to resolve all the conflicts and confusion and understanding the "why" behind various seemingly simple sounding algorithms became a 100 page tome (first cut), so I decided to see if SyncFusion would be interested in it. And they were!
Latest Article - Contextual Data Explorer
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
Thanks, neat story. 
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
Downloaded.
Reading...
Read the About the Author:
About The Author "Marc enjoys playing the lyre and going on adventures with his fiancee."
As soon as I completed that sentence I thought, "He's a Magic Bard. He's actually a traveling Magic Bard." Then my mind went back to the old Commodore 64 game...
The Bard's Tale (1985 video game) - Wikipedia[^]
Is that you by the fire with the lyre?
Does that sentence rhyme? 
The Bard's Tale (1985 video game) - cover pic[^] 
|
|
|
|
|
raddevus wrote: Then my mind went back to the old Commodore 64 game...
I remember that game! But no, that's not me. I was a lot younger then! 
Latest Article - Contextual Data Explorer
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
When I read the name of the book.." The Kademlia Protocol " ...could this be the next Frederick Forsyth....
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
abmv wrote: could this be the next Frederick Forsyth
Hah! That would be a good title!
Latest Article - Contextual Data Explorer
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
The context is being used in Code First mode with code that was generated from an EDMX file for either Database First or Model First development. This will not work correctly. To fix this problem do not remove the line of code that throws this exception. If you wish to use Database First or Model First, then make sure that the Entity Framework connection string is included in the app.config or web.config of the start-up project. If you are creating your own DbConnection, then make sure that it is an EntityConnection and not some other type of DbConnection, and that you pass it to one of the base DbContext constructors that take a DbConnection. To learn more about Code First, Database First, and Model First see the Entity Framework documentation here: Entity Framework (EF) Documentation
So glad I don't use EF!
Latest Article - Contextual Data Explorer
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
Marc Clifton wrote: So glad I don't use EF!
Why? Is it because it's wise to wait a while to see if Mickeysoft ditches it again in favor of something else? Or is it because some frameworks tend to hide a problem's complexity while introducing its own new complexity?
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
CodeWraith wrote: Is it because it's wise to wait a while to see if Mickeysoft ditches it again in favor of something else? Or is it because some frameworks tend to hide a problem's complexity while introducing its own new complexity?
I see you've experienced EF as well.
Latest Article - Contextual Data Explorer
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
Doing so right at this moment.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
I find the opposite is true, when a little complexity is required one spends too much time fighting the frameworks simplistic / single dimensional approach to get the task done.
Signature ready for installation. Please Reboot now.
|
|
|
|
|
Sacrilege! Mickeysoft never falls short of any expectations!
Again, before the fanbois recover from their shock, let's get their outcry out of the way: You must be a hater who always hates and is easily confused by facts. You are also a troll who enjoys stomping on their tender feelings. 
Also, this has become #3 on my checklist when to avoid putting too much time in Mickeysoft's grand new thingie.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
As long as you realise the language you use means no-one is going to take you seriously, it's all good.
|
|
|
|
|
What gave you the impression that I'm still around here for anything serious?
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
I was just checking that you knew no-one is going to take you seriously, I'd hate to see you wasting your time.
|
|
|
|
|
How nice of you. And now try your trolling luck somewhere else. It's your time you are wasting right now.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
Marc Clifton wrote: So glad I don't use EF!
Yeah, EF seems to be created for devs who don't want to actually think about the database as being a separate thing. However, at this point, the db is still a separate thing.
And if you attempt to blithely roll on as if the db is not a separate thing then you will either:
1) pay the price for it
2) cause someone else down the road (after you are gone) to pay the price for it
Wouldn't It Be Nice?
It would be nice if our code just serialized to a structured format without ever having to think about it.
It would also be nice if my car powered itself from all the electrons in the atoms that surround it.
Free energy!
|
|
|
|
|
raddevus wrote: EF seems to be created for devs who don't want to actually think about the database as being a separate thing
It's an ORM, so its purpose is to abstract the domain knowledge in the db into object orientated code without the developer needing to concern themselves with the technicalities of the data access methods. "Code first" is only used by proptypers and school students, it isn't used in the "real world" so it's fairly hard to completely forget you're using a separate database, and any decent developer will be well aware and they'll also ensure the code they're writing isn't going anything daft at the database end. Any technology can be used badly, criticising something because it *can* be used badly does nothing but make me question the motives of the person doing the critisiing.
|
|
|
|
|
|
raddevus wrote: I've just seen it get people down a road in the past where they hit a dead end with no way out.
Then they're bad developers, I have no issues with EF.
raddevus wrote: I'd like to see your rebuttal to OP because he is the one who said he is glad he doesn't use it.
He's just an old man who is scared of anything new
|
|
|
|
|
I successfully avoided using EF up until last year for some MVC stuff I'm doing.
I don't like it. I was happy with my home-spun ADO db class, although my home-spun class really does need to be bolstered with transaction handling. Even so, it's never really failed me yet. I'd also much rather handle my upserting and data retrieval via stored procs (I'm a strong advocate for putting db crap in the db).
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
John Simmons / outlaw programmer wrote: successfully avoided using EF up until last year for some MVC stuff I'm doing.
I've avoided it because it seems like it's overly engineered. Way too much code and technology for something that just wraps ADO anyhow.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Most of the time, the use of EF (or any ORM for that matter) is driven by management's desire to get something out "fast", and efficiency is NOT a consideration in those decisions. Many times, using EF is like using a hammer to kill a flea.
I'm actually torn with regards to using or not using EF. On the one hand, it doesn't require you to write BOTH ends of the database access. On the other hand, if you change the model, you have to do gyrations to update the database to match the model using the package manager console. In my case, the package manager console refuses to work because of some stupid-ass security policy override regarding powershell script execution, so I'm stuck with having to manually change the database ANYWAY. How stupid is that?!
I think I'm going to seriously explore moving over to my ADO class. My only concern is the OWIN stuff that MVC uses. There's a LOT of code that's deeply reliant on the use of EF. I wish they would change the template to allow us to select the ORM (or no-ORM code) of our choice. These frameworks are supposed to make our lives easier, but they actually don't when it comes to getting closer to the metal.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
John Simmons / outlaw programmer wrote: My only concern is the OWIN stuff that MVC uses. There's a LOT of code that's deeply reliant on the use of EF. I wish they would change the template to allow us to select the ORM (or no-ORM code) of our choice. These frameworks are supposed to make our lives easier, but they actually don't when it comes to getting closer to the metal.
How can that be?
As I understand them, the MVC/MVP patterns strictly separate presentation, logic and data access. They have different takes on where to draw the separating lines, but data access is always abstracted away into the model.
How can then the 'front end' depend on the EF, unless it's actually MVC in name only?
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
#/media/File:Bard%27s_Tale_Box_Cover.jpg){kind=link}