You all prolly dont give a shit but does any of you know of a tool to get back into an instagram account?? I somehow forgot the account password. I would love any assistance you can offer me.
@Ahmed Parker thanks for your reply. I found the site through google and I'm waiting for the hacking stuff now. Looks like it's gonna take a while so I will get back to you later when my account password hopefully is recovered.
there has to be an exception made for deletions: holding on to a request to delete a fact, and then perform the delete when we find the fact to be deleted; knowing the fact can't be recreated (because of unique ids). GDPR is a great example.
There are databases like cockroachdb and faunadb, diatributed databases which offer serializable isolation level and can scale to 100k+ tps. I don't think eventual consistency is something you want to deal with unless you need to scale to 3 continents on the same database shard or somehing.
In practice, with both of those DBs, in order to get serializable isolation *and* 100k+ tps you end up having to eliminate transaction contention and doing so is in practice very close to what you would do when designing an eventually consistent CQRS/ES system (Fauna's docs specifically recommend CQRS/ES and thus eventual consistency as the approach to take).
You dont - (between services). Your joined data is specific to an individual microservice - its not split across multiple services. Make your microservice return what its concerned with nothing more
We have to probably build 1 more database which is equivalent of a MATERIALIZED view and keep syncing it. There is adhoc where criteria but no adhoc join on the fly. We can only query this MATERIALIZED view or what they call CQRS. HUGE data duplication with latency.MATERIALIZED view is dinosaur. call it CQRS.
This talk has some glaring errors in trying to strictly define things. For example, a command does not always have a single receiver. You can send a command to n receivers and that's actually extremely useful, for the same reasons he likes events so much.
At th-cam.com/video/1hwuWmMNT4c/w-d-xo.html Jonas says that the DB table and the event bus both succeed or fail atomically. Can't that be eventually succeeds or fails instead of atomically? If I use google pub/sub and postgresql, can't I log that I'm inserting the event into the DB, and then when I'm done sending it over pub/sub, log that I'm done with the event?
I think he was trying to say something useful/valuable - but I really struggled to sift through the waffle.. Points were laboured FAR too much for my liking.. Good try though :-)
generally, Jonas is a good speaker, but this one he didn't seem to be well prepared... I believe he knows all of those stuff because I have seen him talking about those things before, but did he change a set of new slides the night before this talk?
Most experts (in any industry) actually have the same problem. They either oversimplify/overexplain the concepts OR they go full-on deep-dive, technical jargon. That's why there's only one Carl Sagan. I actually liked his explanation he didn't spoon-feed his own implementation. He gave a basic, albeit long, introduction to Events in MS Architecture since, as an architect, you can formulate your own implementation and then cross-reference it to how others implementing it.
Get put post delete are verbs. So we focus on nouns. Where did ver s come back again? Intent can only be insert update delete select. When events are produced there is no choice but consume event producer is obliged to produce and consumer is obliged yo consume if application has to work. Events are finally crud. What is crud less system. We need some code to look at. How event looks like , how message looks like how rdbms looked. How it looked after events. How much delay happened. How cars looks like how materialized view looks like. I would not present something without examples. This assumes that e eryone knows everything. Like taking to yourself not really for audience.
10:04 and and and try to understad the facts. i'll i'll i'll get the commands quite soon. but but but trying to find the co co cozal... between your your your components and the service. and and and and the service
@@GabrielGunderson it's not about manners. It's about right person for the right job. He may be arristotle or plato but he isn't suitable for delivering speeches and presentations. That's it.
Thank you for… broadcasting this event ;)
Really clear and concise talk. Thank you very much for the effort.
You all prolly dont give a shit but does any of you know of a tool to get back into an instagram account??
I somehow forgot the account password. I would love any assistance you can offer me.
@Karsyn Mack instablaster =)
@Ahmed Parker thanks for your reply. I found the site through google and I'm waiting for the hacking stuff now.
Looks like it's gonna take a while so I will get back to you later when my account password hopefully is recovered.
@Ahmed Parker it worked and I finally got access to my account again. Im so happy!
Thanks so much, you really help me out !
@Karsyn Mack No problem xD
The best talk about I have ever seen
This is a very nice talk, thank you for transmitting the experience!
Wow, great presentation
Great talk, good explanations, good references. Well done!
Managing events is a very powerful approach. Basically development converts into simple configuration.This is related to Actor model by Carl Hewitt.
Awesome talk!
great talk
Really good!
Seems to me that the future of microservices will use a lot of blockchain concepts
OK, whats the difference between event driven services and a multi agent system !?
Great talk
there has to be an exception made for deletions: holding on to a request to delete a fact, and then perform the delete when we find the fact to be deleted; knowing the fact can't be recreated (because of unique ids). GDPR is a great example.
Why would you need to delete a fact? You can always ignore it or not even receive it.
There are databases like cockroachdb and faunadb, diatributed databases which offer serializable isolation level and can scale to 100k+ tps. I don't think eventual consistency is something you want to deal with unless you need to scale to 3 continents on the same database shard or somehing.
In practice, with both of those DBs, in order to get serializable isolation *and* 100k+ tps you end up having to eliminate transaction contention and doing so is in practice very close to what you would do when designing an eventually consistent CQRS/ES system (Fauna's docs specifically recommend CQRS/ES and thus eventual consistency as the approach to take).
Brilliant.
25:14 how to get joined data in a CRUD microservice system? thanks in advance
You dont - (between services). Your joined data is specific to an individual microservice - its not split across multiple services. Make your microservice return what its concerned with nothing more
CQRS projections?
We have to probably build 1 more database which is equivalent of a MATERIALIZED view and keep syncing it. There is adhoc where criteria but no adhoc join on the fly. We can only query this MATERIALIZED view or what they call CQRS. HUGE data duplication with latency.MATERIALIZED view is dinosaur. call it CQRS.
37:35 event based persistence
This talk has some glaring errors in trying to strictly define things. For example, a command does not always have a single receiver. You can send a command to n receivers and that's actually extremely useful, for the same reasons he likes events so much.
At th-cam.com/video/1hwuWmMNT4c/w-d-xo.html Jonas says that the DB table and the event bus both succeed or fail atomically.
Can't that be eventually succeeds or fails instead of atomically? If I use google pub/sub and postgresql, can't I log that I'm inserting the event into the DB, and then when I'm done sending it over pub/sub, log that I'm done with the event?
I already gave up after "You know part" because I don't know
(y) manuel silva . best regards
Distribute for Availability not scalability if you are going to do this understanding this is basic
I think he was trying to say something useful/valuable - but I really struggled to sift through the waffle.. Points were laboured FAR too much for my liking.. Good try though :-)
Good content but the stuttering is tough to take.
Really tough to be you. Sorry you had to hear that while getting access to all of this great free content.
@@GabrielGunderson Content was OK, definitely not great.
generally, Jonas is a good speaker, but this one he didn't seem to be well prepared...
I believe he knows all of those stuff because I have seen him talking about those things before, but did he change a set of new slides the night before this talk?
Sounded like Jeff Goldblum. 😁 no disrespect. This is a great talk 🤘
I posit that there is only now.
How about an example project to go with the talk, all these buzz words are just marketing gimmicks.
Him explaining what he thinks events are is a marketing gimmick?
Most experts (in any industry) actually have the same problem. They either oversimplify/overexplain the concepts OR they go full-on deep-dive, technical jargon. That's why there's only one Carl Sagan. I actually liked his explanation he didn't spoon-feed his own implementation. He gave a basic, albeit long, introduction to Events in MS Architecture since, as an architect, you can formulate your own implementation and then cross-reference it to how others implementing it.
@@justintolentino9222 Most likely not everybody understands this enough to make their own implementations.
Don't focus on the nuns !
Get put post delete are verbs. So we focus on nouns. Where did ver s come back again? Intent can only be insert update delete select. When events are produced there is no choice but consume event producer is obliged to produce and consumer is obliged yo consume if application has to work. Events are finally crud. What is crud less system. We need some code to look at. How event looks like , how message looks like how rdbms looked. How it looked after events. How much delay happened. How cars looks like how materialized view looks like. I would not present something without examples. This assumes that e eryone knows everything. Like taking to yourself not really for audience.
What can we choose? Not consume message and get out of sync? You have to consume if the application hS to work. Where is the choice
10:04 and and and try to understad the facts. i'll i'll i'll get the commands quite soon. but but but trying to find the co co cozal... between your your your components and the service. and and and and the service
Are you a jerk in real life? Or just on TH-cam?
@@GabrielGunderson isn't that what you hear in video?
@@einfacherkerl3279 That's exactly what I hear. Would you say that to his face? Have some manners.
@@GabrielGunderson it's not about manners. It's about right person for the right job. He may be arristotle or plato but he isn't suitable for delivering speeches and presentations. That's it.
@@einfacherkerl3279 no he just needs to slow down a bit