{ "archive_path": "archive/1745641263.345312", "base_url": "udidahan.com/2009/09/01/dont-delete-just-dont", "basename": "", "bookmarked_date": "2025-04-26 04:21", "canonical": { "archive_org_path": "https://web.archive.org/web/udidahan.com/2009/09/01/dont-delete-just-dont", "dom_path": "output.html", "favicon_path": "favicon.ico", "git_path": "git/", "google_favicon_path": "https://www.google.com/s2/favicons?domain=udidahan.com", "headers_path": "headers.json", "htmltotext_path": "htmltotext.txt", "index_path": "index.html", "media_path": "media/", "mercury_path": "mercury/content.html", "pdf_path": "output.pdf", "readability_path": "readability/content.html", "screenshot_path": "screenshot.png", "singlefile_path": "singlefile.html", "warc_path": "warc/", "wget_path": null }, "domain": "udidahan.com", "downloaded_at": "2025-04-26T04:21:06.864530+00:00", "downloaded_datestr": "2025-04-26 04:21", "extension": "", "hash": "6CNQ763E30AGMRE6B1TT", "history": { "archive_org": [ { "cmd": [ "/usr/bin/curl", "--silent", "--location", "--compressed", "--proxy", "socks5://tor-socks-proxy:9150", "--head", "--max-time", "60", "--user-agent", "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36 ArchiveBox/{VERSION} (+https://github.com/ArchiveBox/ArchiveBox/)", "https://web.archive.org/save/https://udidahan.com/2009/09/01/dont-delete-just-dont/" ], "cmd_version": "8.10.1", "end_ts": "2025-04-26T04:22:20.386962+00:00", "index_texts": null, "output": "https://web.archive.org/web/20250426042205/https://udidahan.com/2009/09/01/dont-delete-just-dont/", "pwd": "/data/archive/1745641263.345312", "schema": "ArchiveResult", "start_ts": "2025-04-26T04:21:47.668555+00:00", "status": "succeeded" } ], "dom": [ { "cmd": [ "/usr/bin/chromium-browser", "--proxy-server=socks5://tor-socks-proxy:9150", "--disable-features=DarkMode", "--run-all-compositor-stages-before-draw", "--hide-scrollbars", "--autoplay-policy=no-user-gesture-required", "--no-first-run", "--use-fake-ui-for-media-stream", "--use-fake-device-for-media-stream", "--simulate-outdated-no-au='Tue, 31 Dec 2099 23:59:59 GMT'", "--headless=new", "--no-sandbox", "--no-zygote", "--disable-dev-shm-usage", "--disable-software-rasterizer", "--disable-sync", "--window-size=1440,2000", "--user-agent=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36 ArchiveBox/{VERSION} (+https://github.com/ArchiveBox/ArchiveBox/)", "--user-data-dir=/data/personas/Default/chrome_profile", "--profile-directory=Default", "--dump-dom", "https://udidahan.com/2009/09/01/dont-delete-just-dont/" ], "cmd_version": "131.0.6778", "end_ts": "2025-04-26T04:21:24.841932+00:00", "index_texts": null, "output": "output.html", "pwd": "/data/archive/1745641263.345312", "schema": "ArchiveResult", "start_ts": "2025-04-26T04:21:15.124322+00:00", "status": "succeeded" } ], "favicon": [ { "cmd": [ "/usr/bin/curl", "--silent", "--location", "--compressed", "--proxy", "socks5://tor-socks-proxy:9150", "--max-time", "60", "--output", "favicon.ico", "--user-agent", "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36 ArchiveBox/{VERSION} (+https://github.com/ArchiveBox/ArchiveBox/)", "https://www.google.com/s2/favicons?domain=udidahan.com" ], "cmd_version": "8.10.1", "end_ts": "2025-04-26T04:21:10.825549+00:00", "index_texts": null, "output": "favicon.ico", "pwd": "/data/archive/1745641263.345312", "schema": "ArchiveResult", "start_ts": "2025-04-26T04:21:07.312665+00:00", "status": "succeeded" } ], "git": [], "headers": [ { "cmd": [ "/usr/bin/curl", "--silent", "--location", "--compressed", "--proxy", "socks5://tor-socks-proxy:9150", "--head", "--max-time", "60", "--user-agent", "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36 ArchiveBox/{VERSION} (+https://github.com/ArchiveBox/ArchiveBox/)", "https://udidahan.com/2009/09/01/dont-delete-just-dont/" ], "cmd_version": "8.10.1", "end_ts": "2025-04-26T04:21:11.232621+00:00", "index_texts": null, "output": "headers.json", "pwd": "/data/archive/1745641263.345312", "schema": "ArchiveResult", "start_ts": "2025-04-26T04:21:10.857997+00:00", "status": "succeeded" } ], "htmltotext": [ { "cmd": [ "(internal) archivebox.extractors.htmltotext", "./{singlefile,dom}.html" ], "cmd_version": "0.8.5rc51", "end_ts": "2025-04-26T04:21:40.314618+00:00", "index_texts": [ "Don\u2019t Delete \u2013 Just Don\u2019t (https://udidahan.com/wp-content/themes/udidahan%20orginal%20templ/style.css) (/wp-content/uploads/csharp1.css) (Udi Dahan - The Software Simplist) (http://feeds.feedburner.com/UdiDahan-TheSoftwareSimplist) (https://udidahan.com/xmlrpc.php) (//s.w.org) (Udi Dahan - The Software Simplist \u00bb Don\u2019t Delete \u2013 Just Don\u2019t Comments Feed) (https://udidahan.com/2009/09/01/dont-delete-just-dont/feed/) (https://udidahan.com/wp-includes/css/dist/block-library/style.min.css?ver=5.8.1) (https://udidahan.com/wp-json/) (https://udidahan.com/wp-json/wp/v2/posts/1097) (RSD) (https://udidahan.com/xmlrpc.php?rsd) (https://udidahan.com/wp-includes/wlwmanifest.xml) (https://udidahan.com/2009/09/01/dont-delete-just-dont/) (https://udidahan.com/?p=1097) (https://udidahan.com/wp-json/oembed/1.0/embed?url=https%3A%2F%2Fudidahan.com%2F2009%2F09%2F01%2Fdont-delete-just-dont%2F) (https://udidahan.com/wp-json/oembed/1.0/embed?url=https%3A%2F%2Fudidahan.com%2F2009%2F09%2F01%2Fdont-delete-just-dont%2F&format=xml) (/) (Udi Dahan) (Udi Dahan) (/) Udi Dahan \u2013 The Software Simplist (/) Enterprise Development Expert & SOA Specialist (http://feeds.feedburner.com/UdiDahan-TheSoftwareSimplist) (Subscribe to my feed) (http://twitter.com/UdiDahan) (Follow me on Twitter) () (/?blog=true) Blog (/consulting/) Consulting (/training/) Training (/articles/) Articles (/speaking/) Speaking (/about/) About (Type and hit enter to search) (Search) (https://udidahan.com/2009/09/01/dont-delete-just-dont/) (Permanent Link: Don\u2019t Delete \u2013 Just Don\u2019t) Don\u2019t Delete \u2013 Just Don\u2019t Tuesday, September 1st, 2009. (no deletes) After reading Ayende\u2019s (http://ayende.com/Blog/archive/2009/08/30/avoid-soft-deletes.aspx) post advocating against \u201csoft deletes\u201d I felt that I should add a bit more to the topic as there were some important business semantics missing. As developers discuss the pertinence of using an IsDeleted column in the database to mark deletion, and the way this relates to reporting and auditing concerns is weighed, the core domain concepts rarely get a mention. Let\u2019s first understand the business scenarios we\u2019re modeling, the why behind them, before delving into the how of implementation. The real world doesn\u2019t cascade Let\u2019s say our marketing department decides to delete an item from the catalog. Should all previous orders containing that item just disappear? And cascading farther, should all invoices for those orders be deleted as well? Going on, would we have to redo the company\u2019s profit and loss statements? Heaven forbid. So, is Ayende wrong? Do we really need soft deletes after all? On the one hand, we don\u2019t want to leave our database in an inconsistent state with invoices pointing to non-existent orders, but on the other hand, our users did ask us to delete an entity. Or did they? When all you have is a hammer\u2026 We\u2019ve been exposing users to entity-based interfaces with \u201ccreate, read, update, delete\u201d semantics in them for so long that they have started presenting us requirements using that same language, even though it\u2019s an extremely poor fit. Instead of accepting \u201cdelete\u201d as a normal user action, let\u2019s go into why users \u201cdelete\u201d stuff, and what they actually intend to do. The guys in marketing can\u2019t actually make all physical instances of a product disappear \u2013 nor would they want to. In talking with these users, we might discover that their intent is quite different: \u201cWhat I mean by \u2018delete\u2019 is that the product should be discontinued. We don\u2019t want to sell this line of product anymore. We want to get rid of the inventory we have, but not order any more from our supplier. The product shouldn\u2019t appear any more when customers do a product search or category listing, but the guys in the warehouse will still need to manage these items in the interim. It\u2019s much shorter to just say \u2018delete\u2019 though.\u201d There seem to be quite a few interesting business rules and processes there, but nothing that looks like it could be solved by a single database column. Model the task, not the data Looking back at the story our friend from marketing told us, his intent is to discontinue the product \u2013 not to delete it in any technical sense of the word. As such, we probably should provide a more explicit representation of this task in the user interface than just selecting a row in some grid and clicking the \u2018delete\u2019 button (and \u201cAre you sure?\u201d isn\u2019t it). As we broaden our perspective to more parts of the system, we see this same pattern repeating: Orders aren\u2019t deleted \u2013 they\u2019re cancelled. There may also be fees incurred if the order is canceled too late. Employees aren\u2019t deleted \u2013 they\u2019re fired (or possibly retired). A compensation package often needs to be handled. Jobs aren\u2019t deleted \u2013 they\u2019re filled (or their requisition is revoked). In all cases, the thing we should focus on is the task the user wishes to perform, rather than on the technical action to be performed on one entity or another. In almost all cases, more than one entity needs to be considered. Statuses In all the examples above, what we see is a replacement of the technical action \u2018delete\u2019 with a relevant business action. At the entity level, instead of having a (hidden) technical WasDeleted status, we see an explicit business status that users need to be aware of. The manager of the warehouse needs to know that a product is discontinued so that they don\u2019t order any more stock from the supplier. In today\u2019s world of retail with Vendor Managed Inventory, this often happens together with a modification to an agreement with the vendor, or possibly a cancellation of that agreement. This isn\u2019t just a case of transactional or reporting boundaries \u2013 users in different contexts need to see different things at different times as the status changes to reflect the entity\u2019s place in the business lifecycle. Customers shouldn\u2019t see discontinued products at all. Warehouse workers should, that is, until the corresponding Stock Keeping Unit (SKU) has been revoked (another status) after we\u2019ve sold all the inventory we wanted (and maybe returned the rest back to the supplier). Rules and Validation When looking at the world through over-simplified-delete-glasses, we may consider the logic dictating when we can delete to be quite simple: do some role-based-security checks, check that the entity exists, delete. Piece of cake. The real world is a bigger, more complicated cake. Let\u2019s consider deleting an order, or rather, canceling it. On top of the regular security checks, we\u2019ve got some rules to consider: If the order has already been delivered, check if the customer isn\u2019t happy with what they got, and go about returning the order. If the order contained products \u201cmade to order\u201d, charge the customer for a portion (or all) of the order (based on other rules). And more\u2026 Deciding what the next status should be may very well depend on the current business status of the entity. Deciding if that change of state is allowed is context and time specific \u2013 at one point in time the task may have been allowed, but later not. The logic here is not necessarily entirely related to the entity being \u201cdeleted\u201d \u2013 there may be other entities which need to be checked, and whose status may also need to be changed as well. Summary I know that some of you are thinking, \u201cmy system isn\u2019t that complex \u2013 we can just delete and be done with it\u201d. My question to you would be, have you asked your users why they\u2019re deleting things? Have you asked them about additional statuses and rules dictating how entities move as groups between them? You don\u2019t want the success of your project to be undermined by that kind of unfounded assumption, do you? The reason we\u2019re given budgets to build business applications is because of the richness in business rules and statuses that ultimately provide value to users and a competitive advantage to the business. If that value wasn\u2019t there, wouldn\u2019t we be serving our users better by just giving them Microsoft Access? In closing, given that you\u2019re not giving your users MS Access, don\u2019t think about deleting entities. Look for the reason why. Understand the different statuses that entities move between. Ask which users need to care about which status. I know it doesn\u2019t show up as nicely on your resume as \u201c3 years WXF\u201d, but \u201csaved the company $4 million in wasted inventory\u201d does speak volumes. One last sentence: Don\u2019t delete. Just don\u2019t. If you liked this article, you might also like articles in these categories:(https://udidahan.com/category/architecture/) Architecture | (https://udidahan.com/category/business-rules/) Business Rules | (https://udidahan.com/category/data-access/) Data Access | (https://udidahan.com/category/databases/) Databases | (https://udidahan.com/category/ddd/) DDD | (https://udidahan.com/category/development/) Development | (https://udidahan.com/category/validation/) Validation (/first-time-here/) (Check out my Best Content) (Check out my Best Content) If you've got a minute, you might enjoy taking a look at some of my (/first-time-here/) best articles .I've gone through the hundreds of articles I've written over the past 6 years and put together a list of the best ones as ranked by my 5000+ readers.(http://www.UdiDahan.com/first-time-here/) You won't be disappointed. (http://feeds.feedburner.com/UdiDahan-TheSoftwareSimplist) (Subscribe to my feed) (Subscribe to my feed) If you'd like to get new articles sent to you when they're published, it's easy and free .(http://feeds.feedburner.com/UdiDahan-TheSoftwareSimplist) Subscribe right here . (http://twitter.com/UdiDahan) (Follow me on Twitter) (Follow me on Twitter) Follow me on Twitter (http://twitter.com/UdiDahan) @UdiDahan . Something on your mind? Got a question? I'd be thrilled to hear it.Leave a comment below or (mailto:questions@UdiDahan.com) email me , whatever works for you. 73 Comments (http://www.25hoursaday.com/weblog/2009/11/23/BuildingScalableDatabasesPerspectivesOnTheWarOnSoftDeletes.aspx) Dare Obasanjo aka Carnage4Life - Building Scalable Databases: Perspectives on the War on Soft Deletes Says: () November 23rd, 2009 at 7:32 am [\u2026] above that there are situations where one wants to hard delete data from the database in his post Don\u2019t Delete \u2013 Just Don\u2019t where he [\u2026] (http://asp-net-best-practices.blogspot.com/) Leo Says: () December 11th, 2009 at 1:35 pm Thanks pal!!! I was wondering if someone was concern about the domain model.. I\u2019m trying to apply some DDD and it makes sense to me that deletes have a reason behind it.. I will say no to deletes from now on!!! Saved my day!!!! Thanks,Leo! (http://christopherdeweese.com/blog2/post/service-oriented-event-driven-part-1-events) Service-Oriented, Event-Driven Part 1: Events \u00ab christopherDeweese.com Says: () December 24th, 2009 at 7:36 am [\u2026] Dahan posted an article titled \u201cDon\u2019t Delete \u2013 Just Don\u2019t\u201d a few weeks back.\u00a0 In that article Udi explores soft deletes versus hard deletes, but he [\u2026] GBruenetti Says: () February 9th, 2010 at 5:55 am Of course there is the need to delete things physically. Temporary data, old data, erroneous data. Before the computers took over we had paper baskets and shredders in our businesses. Since the basic business requirements are mainly unchanged we also need the digital equivalent of them today. I don\u2019t want to filter my valuable information out of a trash mountain. This observation does not mute your main point: Make sure you understand what your user wants/needs and *then* implement the correct logic for this. However, sometimes that can be a plain DELETE. SJB Says: () February 12th, 2010 at 1:49 pm How does this tie in with Data Protection laws, where data can only be held for x-amount of time? (http://www.UdiDahan.com) udidahan Says: () February 13th, 2010 at 10:39 am SJB, At that point, we create rollups of the data which can be stored for longer periods of time. ricky lively Says: () August 2nd, 2011 at 6:24 pm When I have had this kind of issue, I found that using a date range indicating when the record is active helpful. After the date range is over, the record still exists (for joins to records that used it), but is not used in anything going forward. (http://www.UdiDahan.com) udidahan Says: () August 3rd, 2011 at 8:09 am Ricky, What you\u2019re describing is a kind of soft-delete. (http://www.udidahan.com/2011/10/02/why-you-should-be-using-cqrs-almost-everywhere%e2%80%a6/) Why you should be using CQRS almost everywhere\u2026 Says: () October 2nd, 2011 at 2:45 pm [\u2026] means you don\u2019t ever delete data (see my previous blog post on the subject), and you definitely don\u2019t overwrite it with an update \u2013 even if you think [\u2026] Thomas (new one) Says: () January 30th, 2012 at 6:57 am Interesting ideas but they are based on data which is directly based on real life objects which basically exist forever. Do we really want to store everything from now to eternity? If we don\u2019t, we have to delete something. Like orders older than 10 years or customers who haven\u2019t bought anything in 2 years. Or stock data from 5 years ago. Storing personal data of ex-employees is probably illegal in many countries, they have to be deleted as soon as employment ends. So: As a blanket idea \u2018Do not delete\u2019 is very bad idea: It will cause massive problems sooner or later. (http://www.UdiDahan.com) udidahan Says: () February 1st, 2012 at 7:57 am Thomas, When it comes to personally identifying information, often we can comply with the privacy laws by just scrambling the data. (http://travisjhasnowebsite.com) Travis J Says: () March 26th, 2012 at 6:23 pm A nice article about not deleting. However, not really much attention is paid to what to do with the data that wasn\u2019t deleted. In fact, it is glossed over. In my opinion this is because you are focusing on the wrong issue. Not just \u201cwhat does deleting mean\u201d, but what IS being deleted. When a record is to be removed, what is really being removed is a node in a graph \u2013 not just a single record. That whole graph integriy is the reason for people to bandaid over the issue with \u201csoft deletes\u201d as advocated here. These bandaid solutions tend to hide the gangrene underneath \u2013 a festering problem which only gets worse with time. What\u2019s worse is that in order to accompany the soft delete logic must be included all over (many times breaking various conventions and implementing anti-patterns) to account for the possible breaks in the object graph. Moreover, what kind of business logic is \u201cisDeleted\u201d?! I believe a very strong solution to this problem, the problem of removing an object while retaining the referential integrity of the object graph, is to use an archival pattern. On delete of an object, the object is archived then deleted. The archive database, a mirror database with meta data (temporal database design can be used and is very relevant here), would then receive the object to be archived and restored if necessary. This makes it very direct to avoid listing or including a deleted object as the relevant database will no longer hold it. Now, the same logic which was applied looking for \u201cisDeleted\u201d \u201cisActive\u201d or \u201cDeletedDate\u201d can be applied in the correct place (Not all over the place) to foreign keys of retrieved objects. When a foreign key is present, but the object is not, then there is now a logical explanation and a logical set of options. Display that the containing object was deleted and some course of action: \u201cRestore, Delete Current Containing Object, View Deleted\u201d. These options can be either chosen by the user, or explicitly defined in code in a logical manner. Depending on how advanced the archival database is, perhaps more options exist such as who deleted it, when, why, etc. etc. (http://www.lelala.de) Lelala Says: () October 2nd, 2012 at 12:53 pm Wow,thanks for that impressive article (i came to you from Ayende\u2019s site). Your example with the marketing department is right, absolutely \u2013 while i can, absolutely, imagine a case in which it is not that relevant that you keep all stuff: You could save the final invoice, e.g., instead of storing all products that you have sold 10 years ago\u2026It depends completely on the use case, without considering this there is no true-vs-false. Luiyo Says: () June 29th, 2013 at 2:13 pm well, at some stages the DELETE is nothing but required. for instance in buffer tables, for some continuous flow processing in large scale systems as the ones I work with. trxs flow in a table through different async processes by changing status, and finally have a \u201clogical deleted\u201d status. But to keep +15 process in the flow with 120 trxs / second throughput, this table has also to be purged. there are different strategies for the purging activities, and the processes and table structure design some times makes it quite tricky. of course for usual business applications (even for large companies) the logical deletion is quite fine, but when dealing with massive data and near real time processing capacity things get a cool twist \ud83d\ude42 cheers, (https://www.lelala.de) Lelala Says: () April 13th, 2014 at 11:08 am The thing is, in smaller webprojects one could delete data, it depends on the context:If its not your bookkeeping or any critical stuff, i\u2019d say there is really no issue in deleting those rows from their tables. Sure -this should not be applied to your taxing-table \ud83d\ude09Hence it depends on the situation/problem one wants to solve.Regards (http://www.UdiDahan.com) udidahan Says: () April 16th, 2014 at 2:26 pm Lelala, I wouldn\u2019t say it\u2019s the issue of small vs big, but rather (as you said) the context. When the data is (what I call) private \u2013 meaning only seen/used by a single user, then that user can delete that data completely without any concern. However, when the data becomes \u201cpublic\u201d \u2013 meaning that there is data from other users that gets connected to it, one should avoid deleting and think of more meaningful lifecycle-type changes to it. Hope that clears things up. Thanks. Oscar Says: () September 19th, 2014 at 1:34 am Hi Udidahan, I have been facing this topic on several systems and I do believe in soft delete. But I have seen there is a problem when the data is highly connected. A very simple example: let\u2019s say that we are managing stores & employees. When we decide to deactivate a store, we can not think on deactivate the employees too (cause that will be thinking in the cascade way that we are trying to avoid), so, we can mark them as \u201cfree\u201d employees, without an assigned store. Seeing this from reporting side, what should we do when we decide to do a report of the stores existing on the months before delete?, should we show the store and the link with all its employees at that time?. And a second report after delete time, should the store not be shown? (of course thinking also on an employee report to show them as free after delete but show them linked to the store on a report before delete). The thing here is, should all be managed as really historic records? or once we decide to deactivate something the relations should be forgotten by the system?. In my example, would be to never show the store even in reports previous to its deactivation and show the employees as free persons since the start of the time. It could be confusing on making a difference when deactivation means something (like the closing of a store) or it is just deleting an input error (user wrongly enters a store that never existed). I know that this could make the topic more complicated, but I believe that in some systems could be need to take in consideration and could have an impact on deciding if we should use soft or physical delete. From my experience I support the idea soft delete but the final user needs to be part of the process on designing the logic behind it. We as analyst and designers can have a lot of good points and ideas, but the goal of a system is that it can make sense to our clients (even if it looks kind of gross to our logic) Thanks in advance, regards (http://www.UdiDahan.com) udidahan Says: () September 21st, 2014 at 7:03 pm Oscar, > the final user needs to be part of the process on designing the logic behind it (the delete) I definitely agree with that statement. dan Says: () July 10th, 2015 at 6:33 am In tables that I use as a queue system, I delete records after processing them.Otherwise I forbid deleting records in my systems. It\u2019s annoying to have to specify \u201cand deletedDate is null\u201d in your queries, but I usually end up making a view like \u201cselect * from FooHistory where deletedDate is null\u201d and use views in app logic.I suppose soft-deletes can be a pair for ORM users, though as a micro-ORM user, it\u2019s neither more nor less of a pain.What is less of a pain is determining the state of the system on date X. You can\u2019t do that if you destroy data. Why would a developer care about this\u2013isn\u2019t it a reporting issue? No, it\u2019s a development issue. Ever get a bug report that you can\u2019t reproduce? Maybe it\u2019s because the data you need to reproduce it has been destroyed. There are entire realms of questions that cannot be answered when you destroy data.I\u2019m sure it wouldn\u2019t be too hard to build a convention-based ORM plugin to deal with soft-delete tables, especially for the readers of this blog. Another thought is in regards to \u201cit doesn\u2019t make sense for a business object to have to check for isDeleted\u201d. I think, \u201cyes & no\u201d. An entity can be thought of as a series of changes over time. If you update the name of a product \u201cFooA\u201d to \u201cFooB\u201d, the people who bought it before the update still have a box that says \u201cFooA\u201d. Or if instead you delete the product and replace it with \u201cFooB\u201d, the old orders for \u201cFooA\u201d should still exist in your system. When the customer views his order history, it should definitely contain an entry for \u201cFooA\u201d, not the updated name. (http://www.UdiDahan.com) udidahan Says: () July 22nd, 2015 at 2:09 pm Dan, Those are great points \u2013 I\u2019m with you. Depending on the DB you\u2019re using, keeping the entire history in a single table can be problematic at large volumes of data. You\u2019d probably want at least a separate file partition for the deleted rows. Pepster Says: () October 21st, 2015 at 3:56 pm In our system we use domain event to insert/update and delete views required for querying. I guess when using ES, it doesn\u2019t matter whether you use Delete in your command as it will be stored in the EventStore as an event. What happened with the aggregate can be always be loaded from history by replaying the events, so no information is lost.When using a model for read/write, it becomes much harder to find out whether you have to do a real delete. Jooo Says: () June 1st, 2016 at 1:19 pm Inspiring post\u2026however, I do not think the example given actually support the point. Basically, The real world does cascade. The order example is a little bit misleading since that is not the real delete scenario. That is just scenarios for stateful entities. Delete is for truly useless data. For instance, if an employee resigns, the company would delete not only his email, but also other record related to him. (assume no ref of this employee is needed in future). Also, audit Trail would take care of the data recovery job. Just make sure the atomic is not broken in transction management. Regards (http://www.UdiDahan.com) udidahan Says: () June 4th, 2016 at 3:01 pm Jooo, Even if an employee resigns or is fired, the company shouldn\u2019t delete/expunge their records. Lawsuits can always happen later. Your comment... () Name (required) () Mail (will not be published) (required) () Website (Submit Comment) (1097) (978eb4ed0a) (158) If this is your first time commenting, it may take a while to show up.I'm working to make that better.(https://udidahan.com/comments/feed/) Subscribe here to receive updates on comments . (/first-time-here/) (Don't miss my best content) (Don't miss my best content) Recommendations (http://www.linkedin.com/profile/recommendations?id=1943218&authType=name&authToken=hSJ-#rec22295049) Bryan Wheeler, Director Platform Development at msnbc.com \u201cUdi Dahan is the real deal. We brought him on site to give our development staff the 5-day \u201cAdvanced Distributed System Design\u201d training. The course profoundly changed our understanding and approach to SOA and distributed systems. Consider some of the evidence: 1. Months later, developers still make allusions to concepts learned in the course nearly every day 2. One of our developers went home and made her husband (a developer at another company) sign up for the course at a subsequent date/venue 3. Based on what we learned, we\u2019ve made constant improvements to our architecture that have helped us to adapt to our ever changing business domain at scale and speed If you have the opportunity to receive the training, you will make a substantial paradigm shift. If I were to do the whole thing over again, I\u2019d start the week by playing the clip from the Matrix where Morpheus offers Neo the choice between the red and blue pills. Once you make the intellectual leap, you\u2019ll never look at distributed systems the same way. Beyond the training, we were able to spend some time with Udi discussing issues unique to our business domain. Because Udi is a rare combination of a big picture thinker and a low level doer, he can quickly hone in on various issues and quickly make good (if not startling) recommendations to help solve tough technical issues.\u201d November 11, 2010 (Sam Gentile) (Sam Gentile) (http://www.samgentile.com) Sam Gentile, Independent WCF & SOA Expert \u201cUdi, one of the great minds in this area.A man I respect immensely.\u201d (Ian Robinson) (Ian Robinson) (http://iansrobinson.com/about/) Ian Robinson, Principal Consultant at ThoughtWorks \"Your blog and articles have been enormously useful in shaping, testing and refining my own approach to delivering on SOA initiatives over the last few years. Over and against a certain 3-layer-application-architecture-blown-out-to- distributed-proportions school of SOA, your writing, steers a far more valuable course .\" (Shy Cohen) (Shy Cohen) (http://www.linkedin.com/in/shycohen) Shy Cohen, Senior Program Manager at Microsoft \u201cUdi is a world renowned software architect and speaker. I met Udi at a conference that we were both speaking at, and immediately recognized his keen insight and razor-sharp intellect. Our shared passion for SOA and the advancement of its practice launched a discussion that lasted into the small hours of the night.It was evident through that discussion that Udi is one of the most knowledgeable people in the SOA space. It was also clear why \u2013 Udi does not settle for mediocrity, and seeks to fully understand (or define) the logic and principles behind things.Humble yet uncompromising, Udi is a pleasure to interact with .\u201d (Glenn Block) (Glenn Block) (http://www.linkedin.com/in/gblock) Glenn Block, Senior Program Manager - WCF at Microsoft \u201cI have known Udi for many years having attended his workshops and having several personal interactions including working with him when we were building our Composite Application Guidance in patterns & practices. What impresses me about Udi is his deep insight into how to address business problems through sound architecture . Backed by many years of building mission critical real world distributed systems it is no wonder that Udi is the best at what he does. When customers have deep issues with their system design, I point them Udi's way.\u201d (Karl Wannenmacher) (Karl Wannenmacher) (https://www.xing.com/profile/Karl_Wannenmacher) Karl Wannenmacher, Senior Lead Expert at Frequentis AG \u201cI have been following Udi\u2019s blog and podcasts since 2007. I\u2019m convinced that he is one of the most knowledgeable and experienced people in the field of SOA, EDA and large scale systems.Udi helped Frequentis to design a major subsystem of a large mission critical system with a nationwide deployment based on NServiceBus . It was impressive to see how he took the initial architecture and turned it upside down leading to a very flexible and scalable yet simple system without knowing the details of the business domain.\nI highly recommend consulting with Udi when it comes to large scale mission critical systems in any domain.\u201d (Simon Segal) (Simon Segal) (http://www.linkedin.com/in/simonsegal) Simon Segal, Independent Consultant \u201cUdi is one of the outstanding software development minds in the world today, his vast insights into Service Oriented Architectures and Smart Clients in particular are indeed a rare commodity. Udi is also an exceptional teacher and can help lead teams to fall into the pit of success. I would recommend Udi to anyone considering some Architecural guidance and support in their next project.\u201d (Ohad Israeli) (Ohad Israeli) (http://www.linkedin.com/in/ohadisraeli) Ohad Israeli, Chief Architect at Hewlett-Packard, Indigo Division \u201cWhen you need a man to do the job Udi is your man! No matter if you are facing near deadline deadlock or at the early stages of your development, if you have a problem Udi is the one who will probably be able to solve it, with his large experience at the industry and his widely horizons of thinking , he is always full of just in place great architectural ideas . I am honored to have Udi as a colleague and a friend (plus having his cell phone on my speed dial).\u201d (Ward Bell) (Ward Bell) (http://www.linkedin.com/pub/0/b08/1a9) Ward Bell, VP Product Development at IdeaBlade \u201cEveryone will tell you how smart and knowledgable Udi is ... and they are oh-so-right. Let me add that Udi is a smart LISTENER. He's always calibrating what he has to offer with your needs and your experience ... looking for the fit. He has strongly held views ... and the ability to temper them with the nuances of the situation.I trust Udi to tell me what I need to hear, even if I don't want to hear it, ... in a way that I can hear it. That's a rare skill to go along with his command and intelligence.\u201d (http://www.linkedin.com/pub/8/314/674) Eli Brin, Program Manager at RISCO Group \u201cWe hired Udi as a SOA specialist for a large scale project. The development is outsourced to India. SOA is a buzzword used almost for anything today. We wanted to understand what SOA really is, and what is the meaning and practice to develop a SOA based system. We identified Udi as the one that can put some sense and order in our minds. We started with a private customized SOA training for the entire team in Israel. After that I had several focused sessions regarding our architecture and design. I will summarize it simply (as he is the software simplist): We are very happy to have Udi in our project. It has a great benefit. We feel good and assured with the knowledge and practice he brings. He doesn\u2019t talk over our heads . We assimilated nServicebus as the ESB of the project. I highly recommend you to bring Udi into your project.\u201d (Catherine Hole) (Catherine Hole) (http://www.linkedin.com/pub/cathrine-hole/0/6a3/666) Catherine Hole, Senior Project Manager at the Norwegian Health Network \u201cMy colleagues and I have spent five interesting days with Udi - diving into the many aspects of SOA. Udi has shown impressive abilities of understanding organizational challenges, and has brought the business perspective into our way of looking at services. He has an excellent understanding of the many layers from business at the top to the technical infrstructure at the bottom. He is a great listener, and manages to simplify challenges in a way that is understandable both for developers and CEOs, and all the specialists in between .\u201d (Yoel Arnon) (Yoel Arnon) (http://www.linkedin.com/in/yoelarnon) Yoel Arnon, MSMQ Expert \u201cUdi has a unique, in depth understanding of service oriented architecture and how it should be used in the real world , combined with excellent presentation skills. I think Udi should be a premier choice for a consultant or architect of distributed systems.\u201d (http://www.linkedin.com/pub/1/a1/607) Vadim Mesonzhnik, Development Project Lead at Polycom \u201cWhen we were faced with a task of creating a high performance server for a video-tele conferencing domain we decided to opt for a stateless cluster with SQL server approach. In order to confirm our decision we invited Udi. After carefully listening for 2 hours he said: \"With your kind of high availability and performance requirements you don\u2019t want to go with stateless architecture.\" One simple sentence saved us from implementing a wrong product and finding that out after years of development. No matter whether our former decisions were confirmed or altered, it gave us great confidence to move forward relying on the experience, industry best-practices and time-proven techniques that Udi shared with us. It was a distinct pleasure and a unique opportunity to learn from someone who is among the best at what he does.\u201d (Jack Van Hoof) (Jack Van Hoof) (http://www.linkedin.com/in/jackvanhoof) Jack Van Hoof, Enterprise Integration Architect at Dutch Railways \u201cUdi is a respected visionary on SOA and EDA, whose opinion I most of the time (if not always) highly agree with. The nice thing about Udi is that he is able to explain architectural concepts in terms of practical code-level examples .\u201d (Neil Robbins) (Neil Robbins) (http://neildoesdotnet.blogspot.com/) Neil Robbins, Applications Architect at Brit Insurance \u201cHaving followed Udi's blog and other writings for a number of years I attended Udi's two day course on 'Loosely Coupled Messaging with NServiceBus' at SkillsMatter, London. I would strongly recommend this course to anyone with an interest in how to develop IT systems which provide immediate and future fitness for purpose. An influential and innovative thought leader and practitioner in his field, Udi demonstrates and shares a phenomenally in depth knowledge that proves his position as one of the premier experts in his field globally. The course has enhanced my knowledge and skills in ways that I am able to immediately apply to provide benefits to my employer. Additionally though I will be able to build upon what I learned in my 2 days with Udi and have no doubt that it will only enhance my future career. I cannot recommend Udi, and his courses, highly enough .\u201d (Nick Malik) (Nick Malik) (http://www.linkedin.com/pub/1/763/999) Nick Malik, Enterprise Architect at Microsoft Corporation \u201cYou are an excellent speaker and trainer, Udi , and I've had the fortunate experience of having attended one of your presentations. I believe that you are a knowledgable and intelligent man.\u201d (Sean Farmar) (Sean Farmar) (http://www.linkedin.com/pub/6/668/107) Sean Farmar, Chief Technical Architect at Candidate Manager Ltd \u201cUdi has provided us with guidance in system architecture and supports our implementation of NServiceBus in our core business application. He accompanied us in all stages of our development cycle and helped us put vision into real life distributed scalable software. He brought fresh thinking, great in depth of understanding software, and ongoing support that proved as valuable and cost effective. Udi has the unique ability to analyze the business problem and come up with a simple and elegant solution for the code and the business alike.With Udi's attention to details, and knowledge we avoided pit falls that would cost us dearly .\u201d (B\u00f8rge Hansen) (B\u00f8rge Hansen) (http://www.linkedin.com/in/borge3000) B\u00f8rge Hansen, Architect Advisor at Microsoft \u201cUdi delivered a 5 hour long workshop on SOA for aspiring architects in Norway. While keeping everyone awake and excited Udi gave us some great insights and really delivered on making complex software challenges simple. Truly the software simplist.\u201d (http://www.linkedin.com/pub/7/678/b2b) Motty Cohen, SW Manager at KorenTec Technologies \u201cI know Udi very well from our mutual work at KorenTec. During the analysis and design of a complex, distributed C4I system - where the basic concepts of NServiceBus start to emerge - I gained a lot of \"Udi's hours\" so I can surely say that he is a professional, skilled architect with fresh ideas and unique perspective for solving complex architecture challenges. His ideas, concepts and parts of the artifacts are the basis of several state-of-the-art C4I systems that I was involved in their architecture design.\u201d (Aaron Jensen) (Aaron Jensen) (http://www.linkedin.com/in/aaronjensen) Aaron Jensen, VP of Engineering at Eleutian Technology \u201cAwesome. Just awesome. We\u2019d been meaning to delve into messaging at Eleutian after multiple discussions with and blog posts from Greg Young and Udi Dahan in the past. We weren\u2019t entirely sure where to start, how to start, what tools to use, how to use them, etc. Being able to sit in a room with Udi for an entire week while he described exactly how, why and what he does to tackle a massive enterprise system was invaluable to say the least. We now have a much better direction and, more importantly, have the confidence we need to start introducing these powerful concepts into production at Eleutian.\u201d (Gad Rosenthal) (Gad Rosenthal) (http://www.linkedin.com/pub/7/601/542) Gad Rosenthal, Department Manager at Retalix \u201cA thinking person. Brought fresh and valuable ideas that helped us in architecting our product. When recommending a solution he supports it with evidence and detail so you can successfully act based on it . Udi's support \"comes on all levels\" - As the solution architect through to the detailed class design. Trustworthy!\u201d (Chris Bilson) (Chris Bilson) (http://www.linkedin.com/pub/0/15/338) Chris Bilson, Developer at Russell Investment Group \u201cI had the pleasure of attending a workshop Udi led at the Seattle ALT.NET conference in February 2009. I have been reading Udi's articles and listening to his podcasts for a long time and have always looked to him as a source of advice on software architecture.When I actually met him and talked to him I was even more impressed. Not only is Udi an extremely likable person, he's got that rare gift of being able to explain complex concepts and ideas in a way that is easy to understand .All the attendees of the workshop greatly appreciate the time he spent with us and the amazing insights into service oriented architecture he shared with us.\u201d (Alexey Shestialtynov) (Alexey Shestialtynov) (http://www.linkedin.com/pub/1/266/a3) Alexey Shestialtynov, Senior .Net Developer at Candidate Manager \u201cI met Udi at Candidate Manager where he was brought in part-time as a consultant to help the company make its flagship product more scalable. For me, even after 30 years in software development, working with Udi was a great learning experience . I simply love his fresh ideas and architecture insights.As we all know it is not enough to be armed with best tools and technologies to be successful in software - there is still human factor involved. When, as it happens, the project got in trouble, management asked Udi to step into a leadership role and bring it back on track. This he did in the span of a month. I can only wish that things had been done this way from the very beginning.I look forward to working with Udi again in the future.\u201d (Christopher Bennage) (Christopher Bennage) (http://www.linkedin.com/pub/1/266/a3) Christopher Bennage, President at Blue Spire Consulting, Inc. \u201cMy company was hired to be the primary development team for a large scale and highly distributed application. Since these are not necessarily everyday requirements, we wanted to bring in some additional expertise. We chose Udi because of his blogging, podcasting, and speaking. We asked him to to review our architectural strategy as well as the overall viability of project.I was very impressed, as Udi demonstrated a broad understanding of the sorts of problems we would face. His advice was honest and unbiased and very pragmatic. Whenever I questioned him on particular points, he was able to backup his opinion with real life examples.\nI was also impressed with his clarity and precision. He was very careful to untangle the meaning of words that might be overloaded or otherwise confusing. While Udi's hourly rate may not be the cheapest, the ROI is undoubtedly a deal .\nI would highly recommend consulting with Udi.\u201d (http://www.linkedin.com/pub/1/3b2/26a) Robert Lewkovich, Product / Development Manager at Eggs Overnight \u201cUdi's advice and consulting were a huge time saver for the project I'm responsible for. The $ spent were well worth it and provided me with a more complete understanding of nServiceBus and most importantly in helping make the correct architectural decisions earlier thereby reducing later, and more expensive, rework.\u201d (Ray Houston) (Ray Houston) (http://www.linkedin.com/pub/1/469/885) Ray Houston, Director of Development at TOPAZ Technologies \u201cUdi's SOA class made me smart - it was awesome. The class was very well put together . The materials were clear and concise and Udi did a fantastic job presenting it. It was a good mixture of lecture, coding, and question and answer. I fully expected that I would be taking notes like crazy, but it was so well laid out that the only thing I wrote down the entire course was what I wanted for lunch. Udi provided us with all the lecture materials and everyone has access to all of the samples which are in the nServiceBus trunk. Now I know why Udi is the \"Software Simplist.\" I was amazed to find that all the code and solutions were indeed very simple. The patterns that Udi presented keep things simple by isolating complexity so that it doesn't creep into your day to day code. The domain code looks the same if it's running in a single process or if it's running in 100 processes.\u201d (Ian Cooper) (Ian Cooper) (http://www.linkedin.com/pub/1/469/885) Ian Cooper, Team Lead at Beazley \u201cUdi is one of the leaders in the .Net development community, one of the truly smart guys who do not just get best architectural practice well enough to educate others but drives innovation. Udi consistently challenges my thinking in ways that make me better at what I do .\u201d (http://www.linkedin.com/pub/1/578/ab5) Liron Levy, Team Leader at Rafael \u201cI've met Udi when I worked as a team leader in Rafael. One of the most senior managers there knew Udi because he was doing superb architecture job in another Rafael project and he recommended bringing him on board to help the project I was leading.Udi brought with him fresh solutions and invaluable deep architecture insights. He is an authority on SOA (service oriented architecture) and this was a tremendous help in our project.On the personal level - Udi is a great communicator and can persuade even the most difficult audiences (I was part of such an audience myself..) by bringing sound explanations that draw on his extensive knowledge in the software business. Working with Udi was a great learning experience for me, and I'll be happy to work with him again in the future.\u201d (Adam Dymitruk) (Adam Dymitruk) (http://www.linkedin.com/in/adymitruk) Adam Dymitruk, Director of IT at Apara Systems \u201cI met Udi for the first time at DevTeach in Montreal back in early 2007. While Udi is usually involved in SOA subjects, his knowledge spans all of a software development company's concerns . I would not hesitate to recommend Udi for any company that needs excellent leadership, mentoring, problem solving, application of patterns, implementation of methodologies and straight out solution development.There are very few people in the world that are as dedicated to their craft as Udi is to his. At ALT.NET Seattle, Udi explained many core ideas about SOA. The team that I brought with me found his workshop and other talks the highlight of the event and provided the most value to us and our organization. I am thrilled to have the opportunity to recommend him.\u201d (Eytan Michaeli) (Eytan Michaeli) (http://www.linkedin.com/in/eytanm) Eytan Michaeli, CTO Korentec \u201cUdi was responsible for a major project in the company, and as a chief architect designed a complex multi server C4I system with many innovations and excellent performance.\u201d (Carl Kenne) (Carl Kenne) (http://www.linkedin.com/pub/carl-kenne/2/982/aa2) Carl Kenne, .Net Consultant at Dotway AB \u201cUdi's session \"DDD in Enterprise apps\" was truly an eye opener. Udi has a great ability to explain complex enterprise designs in a very comprehensive and inspiring way. I've seen several sessions on both DDD and SOA in the past, but Udi puts it in a completly new perspective and makes us understand what it's all really about . If you ever have a chance to see any of Udi's sessions in the future, take it!\u201d (http://www.linkedin.com/pub/7/b15/407) Avi Nehama, R&D Project Manager at Retalix \u201cNot only that Udi is a briliant software architecture consultant, he also has remarkable abilities to present complex ideas in a simple and concise manner, and... always with a smile . Udi is indeed a top-league professional!\u201d (Ben Scheirman) (Ben Scheirman) (http://www.linkedin.com/in/benscheirman) Ben Scheirman, Lead Developer at CenterPoint Energy \u201cUdi is one of those rare people who not only deeply understands SOA and domain driven design, but also eloquently conveys that in an easy to grasp way. He is patient, polite, and easy to talk to . I'm extremely glad I came to his workshop on SOA.\u201d (Scott C. Reynolds) (Scott C. Reynolds) (http://www.linkedin.com/in/scottcreynolds) Scott C. Reynolds, Director of Software Engineering at CBLPath \u201cUdi is consistently advancing the state of thought in software architecture, service orientation, and domain modeling.His mastery of the technologies and techniques is second to none, but he pairs that with a singular ability to listen and communicate effectively with all parties, technical and non, to help people arrive at context-appropriate solutions .\nEvery time I have worked with Udi, or attended a talk of his, or just had a conversation with him I have come away from it enriched with new understanding about the ideas discussed.\u201d (http://www.linkedin.com/in/obender) Evgeny-Hen Osipow, Head of R&D at PCLine \u201cUdi has helped PCLine on projects by implementing architectural blueprints demonstrating the value of simple design and code.\u201d (Rhys Campbell) (Rhys Campbell) (http://www.linkedin.com/in/rhysc) Rhys Campbell, Owner at Artemis West \u201cFor many years I have been following the works of Udi. His explanation of often complex design and architectural concepts are so cleanly broken down that even the most junior of architects can begin to understand these concepts. These concepts however tend to typify the \"real world\" problems we face daily so even the most experienced software expert will find himself in an \"Aha!\" moment when following Udi teachings.It was a pleasure to finally meet Udi in Seattle Alt.Net OpenSpaces 2008, where I was pleasantly surprised at how down-to-earth and approachable he was. His depth and breadth of software knowledge also became apparent when discussion with his peers quickly dove deep in to the problems we current face. If given the opportunity to work with or recommend Udi I would quickly take that chance. When I think .Net Architecture, I think Udi.\u201d (Sverre Hundeide) (Sverre Hundeide) (http://www.linkedin.com/in/rhysc) Sverre Hundeide, Senior Consultant at Objectware \u201cUdi had been hired to present the third LEAP master class in Oslo. He is an well known international expert on enterprise software architecture and design, and is the author of the open source messaging framework nServiceBus.\nThe entire class was based on discussion and interaction with the audience, and the only Power Point slide used was the one showing the agenda.He started out with sketching a naive traditional n-tier application (big ball of mud), and based on suggestions from the audience we explored different solutions which might improve the solution. Whatever suggestions we threw at him, he always had a thoroughly considered answer describing pros and cons with the suggested solution. He obviously has a lot of experience with real world enterprise SOA applications .\u201d (Rapha\u00ebl Wouters) (Rapha\u00ebl Wouters) (http://www.linkedin.com/in/raphaelwouters) Rapha\u00ebl Wouters, Owner/Managing Partner at Medinternals \u201cI attended Udi's excellent course 'Advanced Distributed System Design with SOA and DDD' at Skillsmatter. Few people can truly claim such a high skill and expertise level, present it using a pragmatic, concrete no-nonsense approach and still stay reachable.\u201d (Nimrod Peleg) (Nimrod Peleg) (http://www.linkedin.com/pub/0/674/708) Nimrod Peleg, Lab Engineer at Technion IIT \u201cOne of the best programmers and software engineer I've ever met, creative, knows how to design and implemet, very collaborative and finally - the applications he designed implemeted work for many years without any problems! \u201d (http://www.linkedin.com/in/jmbeas) Jose Manuel Beas \u201cWhen I attended Udi's SOA Workshop, then it suddenly changed my view of what Service Oriented Architectures were all about. Udi explained complex concepts very clearly and created a very productive discussion environment where all the attendees could learn a lot . I strongly recommend hiring Udi.\u201d (Daniel Jin) (Daniel Jin) (http://www.linkedin.com/pub/0/674/708) Daniel Jin, Senior Lead Developer at PJM Interconnection \u201cUdi is one of the top SOA guru in the .NET space. He is always eager to help others by sharing his knowledge and experiences. His blog articles often offer deep insights and is a invaluable resource. I highly recommend him.\u201d (Pasi Taive) (Pasi Taive) (http://www.linkedin.com/pub/pasi-taive/0/a93/3b5) Pasi Taive, Chief Architect at Tieto \u201cI attended both of Udi's \"UI Composition Key to SOA Success\" and \"DDD in Enterprise Apps\" sessions and they were exceptionally good. I will definitely participate in his sessions again. Udi is a great presenter and has the ability to explain complex issues in a manner that everyone understands.\u201d (http://il.linkedin.com/pub/eran-sagi/0/b55/999) Eran Sagi, Software Architect at HP \u201cSo far, I heard about Service Oriented architecture all over. \nEveryone mentions it \u2013 the big buzz word. \nBut, when I actually asked someone for what does it really mean, no one managed to give me a complete satisfied answer.\nFinally in his excellent course \u201cAdvanced Distributed Systems\u201d, I got the answers I was looking for .\nUdi went over the different motivations (principles) of Services Oriented, explained them well one by one, and showed how each one could be technically addressed using NService bus.\nIn his course, Udi also explain the way of thinking when coming to design a Service Oriented system. \nWhat are the questions you need to ask yourself in order to shape your system, place the logic in the right places for best Service Oriented system. I would recommend this course for any architect or developer who deals with distributed system, but not only. \nIn my work we do not have a real distributed system, but one PC which host both the UI application and the different services inside, all communicating via WCF. \nI found that many of the architecture principles and motivations of SOA apply for our system as well. Enough that you have SW partitioned into components and most of the principles becomes relevant to you as well.\nBottom line \u2013 an excellent course recommended to any SW Architect, or any developer dealing with distributed system.\u201d (/consulting/) Consult with Udi Guest Authored Books (http://www.jnsk.se/weblog/posts/GuestAuthors.htm) (Chapter: Introduction to SOA) (Chapter: Introduction to SOA) (http://www.soa-expertenwissen.de/) (Article: The Enterprise Service Bus and Your SOA) (Article: The Enterprise Service Bus and Your SOA) (http://www.amazon.com/dp/059652269X) (97 Things Every Software Architect Should Know) (https://mastodon.social/@Udidahan) Follow me on Mastodon (http://creativecommons.org/licenses/by/3.0/) (Creative Commons License) (Creative Commons License) \u00a9 Copyright 2005-2011, Udi Dahan. (mailto:email@UdiDahan.com) email@UdiDahan.com " ], "output": "htmltotext.txt", "pwd": "/data/archive/1745641263.345312", "schema": "ArchiveResult", "start_ts": "2025-04-26T04:21:40.248969+00:00", "status": "succeeded" } ], "media": [ { "cmd": [ "/usr/local/bin/yt-dlp", "--restrict-filenames", "--trim-filenames", "128", "--write-description", "--write-info-json", "--write-annotations", "--write-thumbnail", "--no-call-home", "--write-sub", "--write-auto-subs", "--convert-subs=srt", "--yes-playlist", "--continue", "--no-abort-on-error", "--ignore-errors", "--geo-bypass", "--add-metadata", "--format=(bv*+ba/b)[filesize<=750m][filesize_approx<=?750m]/(bv*+ba/b)", "--skip-download", "--cache-dir=/data/yt-dlp-cache/", "--cookies=/data/yt-dlp-cache/cookies.txt", "--proxy=socks5://tor-socks-proxy:9150", "--no-playlist", "https://udidahan.com/2009/09/01/dont-delete-just-dont/" ], "cmd_version": "2024.10.7", "end_ts": "2025-04-26T04:21:47.566737+00:00", "index_texts": [], "output": "media/", "pwd": "/data/archive/1745641263.345312", "schema": "ArchiveResult", "start_ts": "2025-04-26T04:21:41.696287+00:00", "status": "succeeded" } ], "mercury": [ { "cmd": [ "/home/archivebox/.npm/bin/postlight-parser", "https://udidahan.com/2009/09/01/dont-delete-just-dont/" ], "cmd_version": "2.2.3", "end_ts": "2025-04-26T04:21:40.220093+00:00", "index_texts": null, "output": "mercury/", "pwd": "/data/archive/1745641263.345312", "schema": "ArchiveResult", "start_ts": "2025-04-26T04:21:36.515788+00:00", "status": "succeeded" } ], "pdf": [], "readability": [ { "cmd": [ "/home/archivebox/.npm/bin/readability-extractor", "/tmp/tmp3n5meevx", "https://udidahan.com/2009/09/01/dont-delete-just-dont/" ], "cmd_version": "0.0.11", "end_ts": "2025-04-26T04:21:29.694011+00:00", "index_texts": [ "Don\u2019t Delete \u2013 Just Don\u2019t\n\n\n\nTuesday, September 1st, 2009.\n\n\n\t\t\t\n\n\t\t\t\t\nAfter reading Ayende\u2019s post advocating against \u201csoft deletes\u201d I felt that I should add a bit more to the topic as there were some important business semantics missing. As developers discuss the pertinence of using an IsDeleted column in the database to mark deletion, and the way this relates to reporting and auditing concerns is weighed, the core domain concepts rarely get a mention. Let\u2019s first understand the business scenarios we\u2019re modeling, the why behind them, before delving into the how of implementation.\nThe real world doesn\u2019t cascade\nLet\u2019s say our marketing department decides to delete an item from the catalog. Should all previous orders containing that item just disappear? And cascading farther, should all invoices for those orders be deleted as well? Going on, would we have to redo the company\u2019s profit and loss statements?\nHeaven forbid.\nSo, is Ayende wrong? Do we really need soft deletes after all?\nOn the one hand, we don\u2019t want to leave our database in an inconsistent state with invoices pointing to non-existent orders, but on the other hand, our users did ask us to delete an entity.\nOr did they?\nWhen all you have is a hammer\u2026\nWe\u2019ve been exposing users to entity-based interfaces with \u201ccreate, read, update, delete\u201d semantics in them for so long that they have started presenting us requirements using that same language, even though it\u2019s an extremely poor fit.\nInstead of accepting \u201cdelete\u201d as a normal user action, let\u2019s go into why users \u201cdelete\u201d stuff, and what they actually intend to do.\nThe guys in marketing can\u2019t actually make all physical instances of a product disappear \u2013 nor would they want to. In talking with these users, we might discover that their intent is quite different:\n\u201cWhat I mean by \u2018delete\u2019 is that the product should be discontinued. We don\u2019t want to sell this line of product anymore. We want to get rid of the inventory we have, but not order any more from our supplier. The product shouldn\u2019t appear any more when customers do a product search or category listing, but the guys in the warehouse will still need to manage these items in the interim. It\u2019s much shorter to just say \u2018delete\u2019 though.\u201d\nThere seem to be quite a few interesting business rules and processes there, but nothing that looks like it could be solved by a single database column.\nModel the task, not the data\nLooking back at the story our friend from marketing told us, his intent is to discontinue the product \u2013 not to delete it in any technical sense of the word. As such, we probably should provide a more explicit representation of this task in the user interface than just selecting a row in some grid and clicking the \u2018delete\u2019 button (and \u201cAre you sure?\u201d isn\u2019t it).\nAs we broaden our perspective to more parts of the system, we see this same pattern repeating:\n\nOrders aren\u2019t deleted \u2013 they\u2019re cancelled. There may also be fees incurred if the order is canceled too late.\nEmployees aren\u2019t deleted \u2013 they\u2019re fired (or possibly retired). A compensation package often needs to be handled.\nJobs aren\u2019t deleted \u2013 they\u2019re filled (or their requisition is revoked).\n\nIn all cases, the thing we should focus on is the task the user wishes to perform, rather than on the technical action to be performed on one entity or another. In almost all cases, more than one entity needs to be considered.\nStatuses\nIn all the examples above, what we see is a replacement of the technical action \u2018delete\u2019 with a relevant business action. At the entity level, instead of having a (hidden) technical WasDeleted status, we see an explicit business status that users need to be aware of.\nThe manager of the warehouse needs to know that a product is discontinued so that they don\u2019t order any more stock from the supplier. In today\u2019s world of retail with Vendor Managed Inventory, this often happens together with a modification to an agreement with the vendor, or possibly a cancellation of that agreement. \nThis isn\u2019t just a case of transactional or reporting boundaries \u2013 users in different contexts need to see different things at different times as the status changes to reflect the entity\u2019s place in the business lifecycle. Customers shouldn\u2019t see discontinued products at all. Warehouse workers should, that is, until the corresponding Stock Keeping Unit (SKU) has been revoked (another status) after we\u2019ve sold all the inventory we wanted (and maybe returned the rest back to the supplier).\nRules and Validation\nWhen looking at the world through over-simplified-delete-glasses, we may consider the logic dictating when we can delete to be quite simple: do some role-based-security checks, check that the entity exists, delete. Piece of cake.\nThe real world is a bigger, more complicated cake.\nLet\u2019s consider deleting an order, or rather, canceling it. On top of the regular security checks, we\u2019ve got some rules to consider:\n\nIf the order has already been delivered, check if the customer isn\u2019t happy with what they got, and go about returning the order. \nIf the order contained products \u201cmade to order\u201d, charge the customer for a portion (or all) of the order (based on other rules).\nAnd more\u2026\n\nDeciding what the next status should be may very well depend on the current business status of the entity. Deciding if that change of state is allowed is context and time specific \u2013 at one point in time the task may have been allowed, but later not. The logic here is not necessarily entirely related to the entity being \u201cdeleted\u201d \u2013 there may be other entities which need to be checked, and whose status may also need to be changed as well.\nSummary\nI know that some of you are thinking, \u201cmy system isn\u2019t that complex \u2013 we can just delete and be done with it\u201d.\nMy question to you would be, have you asked your users why they\u2019re deleting things? Have you asked them about additional statuses and rules dictating how entities move as groups between them? You don\u2019t want the success of your project to be undermined by that kind of unfounded assumption, do you?\nThe reason we\u2019re given budgets to build business applications is because of the richness in business rules and statuses that ultimately provide value to users and a competitive advantage to the business. If that value wasn\u2019t there, wouldn\u2019t we be serving our users better by just giving them Microsoft Access?\nIn closing, given that you\u2019re not giving your users MS Access, don\u2019t think about deleting entities. Look for the reason why. Understand the different statuses that entities move between. Ask which users need to care about which status. I know it doesn\u2019t show up as nicely on your resume as \u201c3 years WXF\u201d, but \u201csaved the company $4 million in wasted inventory\u201d does speak volumes.\nOne last sentence: Don\u2019t delete. Just don\u2019t.\n\n\n\n\n\n\n\n\n\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\t\t\n\n\t\t\t\t\n\n\t\t\t\n\t\t\n\n\n\u00a0\n\n\u00a0\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\u00a0\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nRecommendations\n\n\n\n\n\n\nBryan Wheeler, Director Platform Development at msnbc.com\n\n\n\n\u201cUdi Dahan is the real deal.We brought him on site to give our development staff the 5-day \u201cAdvanced Distributed System Design\u201d training. The course profoundly changed our understanding and approach to SOA and distributed systems. Consider some of the evidence: 1. Months later, developers still make allusions to concepts learned in the course nearly every day 2. One of our developers went home and made her husband (a developer at another company) sign up for the course at a subsequent date/venue 3. Based on what we learned, we\u2019ve made constant improvements to our architecture that have helped us to adapt to our ever changing business domain at scale and speed If you have the opportunity to receive the training, you will make a substantial paradigm shift. If I were to do the whole thing over again, I\u2019d start the week by playing the clip from the Matrix where Morpheus offers Neo the choice between the red and blue pills. Once you make the intellectual leap, you\u2019ll never look at distributed systems the same way. Beyond the training, we were able to spend some time with Udi discussing issues unique to our business domain. Because Udi is a rare combination of a big picture thinker and a low level doer, he can quickly hone in on various issues and quickly make good (if not startling) recommendations to help solve tough technical issues.\u201d November 11, 2010\n\n\n\n\nSam Gentile, Independent WCF & SOA Expert\n\n\u201cUdi, one of the great minds in this area.A man I respect immensely.\u201d\n\n\n\n\nIan Robinson, Principal Consultant at ThoughtWorks\n\n\"Your blog and articles have been enormously useful in shaping, testing and refining my own approach to delivering on SOA initiatives over the last few years. Over and against a certain 3-layer-application-architecture-blown-out-to- distributed-proportions school of SOA, your writing, steers a far more valuable course.\"\n\n\n\n\nShy Cohen, Senior Program Manager at Microsoft\n\n\u201cUdi is a world renowned software architect and speaker. I met Udi at a conference that we were both speaking at, and immediately recognized his keen insight and razor-sharp intellect. Our shared passion for SOA and the advancement of its practice launched a discussion that lasted into the small hours of the night.It was evident through that discussion that Udi is one of the most knowledgeable people in the SOA space. It was also clear why \u2013 Udi does not settle for mediocrity, and seeks to fully understand (or define) the logic and principles behind things.Humble yet uncompromising, Udi is a pleasure to interact with.\u201d\n\n\n\n\nGlenn Block, Senior Program Manager - WCF at Microsoft\n\n\u201cI have known Udi for many years having attended his workshops and having several personal interactions including working with him when we were building our Composite Application Guidance in patterns & practices. What impresses me about Udi is his deep insight into how to address business problems through sound architecture. Backed by many years of building mission critical real world distributed systems it is no wonder that Udi is the best at what he does. When customers have deep issues with their system design, I point them Udi's way.\u201d\n\n\n\n\nKarl Wannenmacher, Senior Lead Expert at Frequentis AG\n\n\u201cI have been following Udi\u2019s blog and podcasts since 2007. I\u2019m convinced that he is one of the most knowledgeable and experienced people in the field of SOA, EDA and large scale systems.\nUdi helped Frequentis to design a major subsystem of a large mission critical system with a nationwide deployment based on NServiceBus. It was impressive to see how he took the initial architecture and turned it upside down leading to a very flexible and scalable yet simple system without knowing the details of the business domain.\nI highly recommend consulting with Udi when it comes to large scale mission critical systems in any domain.\u201d\n\n\n\n\nSimon Segal, Independent Consultant\n\n\u201cUdi is one of the outstanding software development minds in the world today, his vast insights into Service Oriented Architectures and Smart Clients in particular are indeed a rare commodity. Udi is also an exceptional teacher and can help lead teams to fall into the pit of success. I would recommend Udi to anyone considering some Architecural guidance and support in their next project.\u201d\n\n\n\n\n\nOhad Israeli, Chief Architect at Hewlett-Packard, Indigo Division\n\n\u201cWhen you need a man to do the job Udi is your man! No matter if you are facing near deadline deadlock or at the early stages of your development, if you have a problem Udi is the one who will probably be able to solve it, with his large experience at the industry and his widely horizons of thinking , he is always full of just in place great architectural ideas. \n\nI am honored to have Udi as a colleague and a friend (plus having his cell phone on my speed dial).\u201d\n\n\n\n\nWard Bell, VP Product Development at IdeaBlade\n\n\u201cEveryone will tell you how smart and knowledgable Udi is ... and they are oh-so-right. Let me add that Udi is a smart LISTENER. He's always calibrating what he has to offer with your needs and your experience ... looking for the fit. He has strongly held views ... and the ability to temper them with the nuances of the situation.I trust Udi to tell me what I need to hear, even if I don't want to hear it, ... in a way that I can hear it. That's a rare skill to go along with his command and intelligence.\u201d\n\n\n\nEli Brin, Program Manager at RISCO Group\n\n\u201cWe hired Udi as a SOA specialist for a large scale project. The development is outsourced to India. SOA is a buzzword used almost for anything today. We wanted to understand what SOA really is, and what is the meaning and practice to develop a SOA based system.\n\nWe identified Udi as the one that can put some sense and order in our minds. We started with a private customized SOA training for the entire team in Israel. After that I had several focused sessions regarding our architecture and design.\n\nI will summarize it simply (as he is the software simplist): We are very happy to have Udi in our project. It has a great benefit. We feel good and assured with the knowledge and practice he brings. He doesn\u2019t talk over our heads. We assimilated nServicebus as the ESB of the project. I highly recommend you to bring Udi into your project.\u201d\n\n\n\n\nCatherine Hole, Senior Project Manager at the Norwegian Health Network\n\n\u201cMy colleagues and I have spent five interesting days with Udi - diving into the many aspects of SOA. Udi has shown impressive abilities of understanding organizational challenges, and has brought the business perspective into our way of looking at services. He has an excellent understanding of the many layers from business at the top to the technical infrstructure at the bottom. He is a great listener, and manages to simplify challenges in a way that is understandable both for developers and CEOs, and all the specialists in between.\u201d\n\n\n\n\nYoel Arnon, MSMQ Expert\n\n\u201cUdi has a unique, in depth understanding of service oriented architecture and how it should be used in the real world, combined with excellent presentation skills. I think Udi should be a premier choice for a consultant or architect of distributed systems.\u201d\n\n\n\nVadim Mesonzhnik, Development Project Lead at Polycom\n\u201cWhen we were faced with a task of creating a high performance server for a video-tele conferencing domain we decided to opt for a stateless cluster with SQL server approach. In order to confirm our decision we invited Udi.\n\nAfter carefully listening for 2 hours he said: \"With your kind of high availability and performance requirements you don\u2019t want to go with stateless architecture.\"One simple sentence saved us from implementing a wrong product and finding that out after years of development. No matter whether our former decisions were confirmed or altered, it gave us great confidence to move forward relying on the experience, industry best-practices and time-proven techniques that Udi shared with us.\n\nIt was a distinct pleasure and a unique opportunity to learn from someone who is among the best at what he does.\u201d\n\n\n\n\nJack Van Hoof, Enterprise Integration Architect at Dutch Railways\n\n\u201cUdi is a respected visionary on SOA and EDA, whose opinion I most of the time (if not always) highly agree with. The nice thing about Udi is that he is able to explain architectural concepts in terms of practical code-level examples.\u201d\n\n\n\n\nNeil Robbins, Applications Architect at Brit Insurance\n\n\u201cHaving followed Udi's blog and other writings for a number of years I attended Udi's two day course on 'Loosely Coupled Messaging with NServiceBus' at SkillsMatter, London.\n\nI would strongly recommend this course to anyone with an interest in how to develop IT systems which provide immediate and future fitness for purpose. An influential and innovative thought leader and practitioner in his field, Udi demonstrates and shares a phenomenally in depth knowledge that proves his position as one of the premier experts in his field globally.\n\nThe course has enhanced my knowledge and skills in ways that I am able to immediately apply to provide benefits to my employer. Additionally though I will be able to build upon what I learned in my 2 days with Udi and have no doubt that it will only enhance my future career.\n\nI cannot recommend Udi, and his courses, highly enough.\u201d\n\n\n\n\nNick Malik, Enterprise Architect at Microsoft Corporation\n\n\u201cYou are an excellent speaker and trainer, Udi, and I've had the fortunate experience of having attended one of your presentations. I believe that you are a knowledgable and intelligent man.\u201d\n\n\n\n\nSean Farmar, Chief Technical Architect at Candidate Manager Ltd\n\n\u201cUdi has provided us with guidance in system architecture and supports our implementation of NServiceBus in our core business application.\nHe accompanied us in all stages of our development cycle and helped us put vision into real life distributed scalable software. He brought fresh thinking, great in depth of understanding software, and ongoing support that proved as valuable and cost effective.\nUdi has the unique ability to analyze the business problem and come up with a simple and elegant solution for the code and the business alike.With Udi's attention to details, and knowledge we avoided pit falls that would cost us dearly.\u201d\n\n\n\n\nB\u00f8rge Hansen, Architect Advisor at Microsoft\n\n\u201cUdi delivered a 5 hour long workshop on SOA for aspiring architects in Norway. While keeping everyone awake and excited Udi gave us some great insights and really delivered on making complex software challenges simple. Truly the software simplist.\u201d\n\n\n\nMotty Cohen, SW Manager at KorenTec Technologies\n\n\u201cI know Udi very well from our mutual work at KorenTec. During the analysis and design of a complex, distributed C4I system - where the basic concepts of NServiceBus start to emerge - I gained a lot of \"Udi's hours\" so I can surely say that he is a professional, skilled architect with fresh ideas and unique perspective for solving complex architecture challenges. His ideas, concepts and parts of the artifacts are the basis of several state-of-the-art C4I systems that I was involved in their architecture design.\u201d\n\n\n\n\n\nAaron Jensen, VP of Engineering at Eleutian Technology\n\n\u201cAwesome. Just awesome.\nWe\u2019d been meaning to delve into messaging at Eleutian after multiple discussions with and blog posts from Greg Young and Udi Dahan in the past. We weren\u2019t entirely sure where to start, how to start, what tools to use, how to use them, etc. Being able to sit in a room with Udi for an entire week while he described exactly how, why and what he does to tackle a massive enterprise system was invaluable to say the least.\n\nWe now have a much better direction and, more importantly, have the confidence we need to start introducing these powerful concepts into production at Eleutian.\u201d\n \n\n\n\n\nGad Rosenthal, Department Manager at Retalix\n\n\u201cA thinking person. Brought fresh and valuable ideas that helped us in architecting our product. When recommending a solution he supports it with evidence and detail so you can successfully act based on it. Udi's support \"comes on all levels\" - As the solution architect through to the detailed class design. Trustworthy!\u201d \n\n\n\n\nChris Bilson, Developer at Russell Investment Group\n\n\u201cI had the pleasure of attending a workshop Udi led at the Seattle ALT.NET conference in February 2009. I have been reading Udi's articles and listening to his podcasts for a long time and have always looked to him as a source of advice on software architecture.When I actually met him and talked to him I was even more impressed. Not only is Udi an extremely likable person, he's got that rare gift of being able to explain complex concepts and ideas in a way that is easy to understand.All the attendees of the workshop greatly appreciate the time he spent with us and the amazing insights into service oriented architecture he shared with us.\u201d \n\n\n\n\nAlexey Shestialtynov, Senior .Net Developer at Candidate Manager\n\n\u201cI met Udi at Candidate Manager where he was brought in part-time as a consultant to help the company make its flagship product more scalable. For me, even after 30 years in software development, working with Udi was a great learning experience. I simply love his fresh ideas and architecture insights.As we all know it is not enough to be armed with best tools and technologies to be successful in software - there is still human factor involved. When, as it happens, the project got in trouble, management asked Udi to step into a leadership role and bring it back on track. This he did in the span of a month. I can only wish that things had been done this way from the very beginning.I look forward to working with Udi again in the future.\u201d \n\n\n\n\nChristopher Bennage, President at Blue Spire Consulting, Inc.\n\n\u201cMy company was hired to be the primary development team for a large scale and highly distributed application. Since these are not necessarily everyday requirements, we wanted to bring in some additional expertise. We chose Udi because of his blogging, podcasting, and speaking. We asked him to to review our architectural strategy as well as the overall viability of project.\nI was very impressed, as Udi demonstrated a broad understanding of the sorts of problems we would face. His advice was honest and unbiased and very pragmatic. Whenever I questioned him on particular points, he was able to backup his opinion with real life examples.\nI was also impressed with his clarity and precision. He was very careful to untangle the meaning of words that might be overloaded or otherwise confusing. While Udi's hourly rate may not be the cheapest, the ROI is undoubtedly a deal.\nI would highly recommend consulting with Udi.\u201d \n\n\n\n\nRobert Lewkovich, Product / Development Manager at Eggs Overnight\n\n\u201cUdi's advice and consulting were a huge time saver for the project I'm responsible for. The $ spent were well worth it and provided me with a more complete understanding of nServiceBus and most importantly in helping make the correct architectural decisions earlier thereby reducing later, and more expensive, rework.\u201d \n\n\n\n\nRay Houston, Director of Development at TOPAZ Technologies\n\n\u201cUdi's SOA class made me smart - it was awesome.\n\nThe class was very well put together. The materials were clear and concise and Udi did a fantastic job presenting it. It was a good mixture of lecture, coding, and question and answer. I fully expected that I would be taking notes like crazy, but it was so well laid out that the only thing I wrote down the entire course was what I wanted for lunch. Udi provided us with all the lecture materials and everyone has access to all of the samples which are in the nServiceBus trunk.\n\nNow I know why Udi is the \"Software Simplist.\" I was amazed to find that all the code and solutions were indeed very simple. The patterns that Udi presented keep things simple by isolating complexity so that it doesn't creep into your day to day code. The domain code looks the same if it's running in a single process or if it's running in 100 processes.\u201d \n\n\n\n\nIan Cooper, Team Lead at Beazley\n\n\u201cUdi is one of the leaders in the .Net development community, one of the truly smart guys who do not just get best architectural practice well enough to educate others but drives innovation. Udi consistently challenges my thinking in ways that make me better at what I do.\u201d \n\n\n\nLiron Levy, Team Leader at Rafael\n\n\u201cI've met Udi when I worked as a team leader in Rafael. One of the most senior managers there knew Udi because he was doing superb architecture job in another Rafael project and he recommended bringing him on board to help the project I was leading.Udi brought with him fresh solutions and invaluable deep architecture insights. He is an authority on SOA (service oriented architecture) and this was a tremendous help in our project.On the personal level - Udi is a great communicator and can persuade even the most difficult audiences (I was part of such an audience myself..) by bringing sound explanations that draw on his extensive knowledge in the software business. Working with Udi was a great learning experience for me, and I'll be happy to work with him again in the future.\u201d\n\n\n\n\nAdam Dymitruk, Director of IT at Apara Systems\n\n\u201cI met Udi for the first time at DevTeach in Montreal back in early 2007. While Udi is usually involved in SOA subjects, his knowledge spans all of a software development company's concerns. I would not hesitate to recommend Udi for any company that needs excellent leadership, mentoring, problem solving, application of patterns, implementation of methodologies and straight out solution development.There are very few people in the world that are as dedicated to their craft as Udi is to his. At ALT.NET Seattle, Udi explained many core ideas about SOA. The team that I brought with me found his workshop and other talks the highlight of the event and provided the most value to us and our organization. I am thrilled to have the opportunity to recommend him.\u201d\n\n\n\n\nEytan Michaeli, CTO Korentec\n\n\u201cUdi was responsible for a major project in the company, and as a chief architect designed a complex multi server C4I system with many innovations and excellent performance.\u201d\n\n\n\n\n\nCarl Kenne, .Net Consultant at Dotway AB\n\n\u201cUdi's session \"DDD in Enterprise apps\" was truly an eye opener. Udi has a great ability to explain complex enterprise designs in a very comprehensive and inspiring way. I've seen several sessions on both DDD and SOA in the past, but Udi puts it in a completly new perspective and makes us understand what it's all really about. If you ever have a chance to see any of Udi's sessions in the future, take it!\u201d\n\n\n\nAvi Nehama, R&D Project Manager at Retalix\n\u201cNot only that Udi is a briliant software architecture consultant, he also has remarkable abilities to present complex ideas in a simple and concise manner, and... \nalways with a smile. Udi is indeed a top-league professional!\u201d\n\n\n\n\nBen Scheirman, Lead Developer at CenterPoint Energy\n\n\u201cUdi is one of those rare people who not only deeply understands SOA and domain driven design, but also eloquently conveys that in an easy to grasp way. He is patient, polite, and easy to talk to. I'm extremely glad I came to his workshop on SOA.\u201d\n\n\n\n\nScott C. Reynolds, Director of Software Engineering at CBLPath \n\n\u201cUdi is consistently advancing the state of thought in software architecture, service orientation, and domain modeling.\nHis mastery of the technologies and techniques is second to none, but he pairs that with a singular ability to listen and communicate effectively with all parties, technical and non, to help people arrive at context-appropriate solutions.\nEvery time I have worked with Udi, or attended a talk of his, or just had a conversation with him I have come away from it enriched with new understanding about the ideas discussed.\u201d\n\n\n\nEvgeny-Hen Osipow, Head of R&D at PCLine\n\u201cUdi has helped PCLine on projects by implementing architectural blueprints demonstrating the value of simple design and code.\u201d\n\n\n\n\nRhys Campbell, Owner at Artemis West\n\n\u201cFor many years I have been following the works of Udi. His explanation of often complex design and architectural concepts are so cleanly broken down that even the most junior of architects can begin to understand these concepts. These concepts however tend to typify the \"real world\" problems we face daily so even the most experienced software expert will find himself in an \"Aha!\" moment when following Udi teachings.\nIt was a pleasure to finally meet Udi in Seattle Alt.Net OpenSpaces 2008, where I was pleasantly surprised at how down-to-earth and approachable he was. His depth and breadth of software knowledge also became apparent when discussion with his peers quickly dove deep in to the problems we current face. If given the opportunity to work with or recommend Udi I would quickly take that chance. When I think .Net Architecture, I think Udi.\u201d \n\n\n\n\nSverre Hundeide, Senior Consultant at Objectware \n\n\u201cUdi had been hired to present the third LEAP master class in Oslo. He is an well known international expert on enterprise software architecture and design, and is the author of the open source messaging framework nServiceBus.\nThe entire class was based on discussion and interaction with the audience, and the only Power Point slide used was the one showing the agenda.\nHe started out with sketching a naive traditional n-tier application (big ball of mud), and based on suggestions from the audience we explored different solutions which might improve the solution. Whatever suggestions we threw at him, he always had a thoroughly considered answer describing pros and cons with the suggested solution. He obviously has a lot of experience with real world enterprise SOA applications.\u201d \n\n\n\n\nRapha\u00ebl Wouters, Owner/Managing Partner at Medinternals\n\n\u201cI attended Udi's excellent course 'Advanced Distributed System Design with SOA and DDD' at Skillsmatter. Few people can truly claim such a high skill and expertise level, present it using a pragmatic, concrete no-nonsense approach and still stay reachable.\u201d\n\n\n\n\nNimrod Peleg, Lab Engineer at Technion IIT\n\n\u201cOne of the best programmers and software engineer I've ever met, creative, knows how to design and implemet, very collaborative and finally - the applications he designed implemeted work for many years without any problems!\u201d\n\n\n\nJose Manuel Beas\n\u201cWhen I attended Udi's SOA Workshop, then it suddenly changed my view of what Service Oriented Architectures were all about. Udi explained complex concepts very clearly and created a very productive discussion environment where all the attendees could learn a lot. I strongly recommend hiring Udi.\u201d \n\n\n\n\nDaniel Jin, Senior Lead Developer at PJM Interconnection\n\n\u201cUdi is one of the top SOA guru in the .NET space. He is always eager to help others by sharing his knowledge and experiences. His blog articles often offer deep insights and is a invaluable resource. I highly recommend him.\u201d \n\n\n\n\nPasi Taive, Chief Architect at Tieto\n\n\u201cI attended both of Udi's \"UI Composition Key to SOA Success\" and \"DDD in Enterprise Apps\" sessions and they were exceptionally good. I will definitely participate in his sessions again. Udi is a great presenter and has the ability to explain complex issues in a manner that everyone understands.\u201d \n\n\n\nEran Sagi, Software Architect at HP\n\n\u201cSo far, I heard about Service Oriented architecture all over. \nEveryone mentions it \u2013 the big buzz word. \nBut, when I actually asked someone for what does it really mean, no one managed to give me a complete satisfied answer.\nFinally in his excellent course \u201cAdvanced Distributed Systems\u201d, I got the answers I was looking for.\nUdi went over the different motivations (principles) of Services Oriented, explained them well one by one, and showed how each one could be technically addressed using NService bus.\nIn his course, Udi also explain the way of thinking when coming to design a Service Oriented system. \nWhat are the questions you need to ask yourself in order to shape your system, place the logic in the right places for best Service Oriented system.\n\nI would recommend this course for any architect or developer who deals with distributed system, but not only. \nIn my work we do not have a real distributed system, but one PC which host both the UI application and the different services inside, all communicating via WCF. \nI found that many of the architecture principles and motivations of SOA apply for our system as well. Enough that you have SW partitioned into components and most of the principles becomes relevant to you as well.\nBottom line \u2013 an excellent course recommended to any SW Architect, or any developer dealing with distributed system.\u201d \n\n\n\n\n\nConsult with Udi\n\n\n\n\nGuest Authored Books" ], "output": "readability/", "pwd": "/data/archive/1745641263.345312", "schema": "ArchiveResult", "start_ts": "2025-04-26T04:21:26.329141+00:00", "status": "succeeded" } ], "screenshot": [], "singlefile": [], "title": [ { "cmd": [ "/usr/bin/curl", "--silent", "--location", "--compressed", "--proxy", "socks5://tor-socks-proxy:9150", "--max-time", "60", "--user-agent", "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36 ArchiveBox/{VERSION} (+https://github.com/ArchiveBox/ArchiveBox/)", "https://udidahan.com/2009/09/01/dont-delete-just-dont/" ], "cmd_version": "8.10.1", "end_ts": "2025-04-26T04:21:24.952569+00:00", "index_texts": null, "output": "Don\u2019t Delete \u2013 Just Don\u2019t", "pwd": "/data/archive/1745641263.345312", "schema": "ArchiveResult", "start_ts": "2025-04-26T04:21:24.894417+00:00", "status": "succeeded" } ], "wget": [] }, "icons": null, "is_archived": true, "is_static": false, "latest": { "archive_org": "https://web.archive.org/web/20250426042205/https://udidahan.com/2009/09/01/dont-delete-just-dont/", "dom": "output.html", "favicon": "favicon.ico", "git": null, "media": "media/", "pdf": null, "screenshot": null, "singlefile": null, "title": "Don\u2019t Delete \u2013 Just Don\u2019t", "warc": null, "wget": null }, "link_dir": "/data/archive/1745641263.345312", "newest_archive_date": "2025-04-26T04:21:47.668555+00:00", "num_failures": 0, "num_outputs": 9, "oldest_archive_date": "2025-04-26T04:21:07.312665+00:00", "path": "/2009/09/01/dont-delete-just-dont/", "schema": "Link", "scheme": "https", "snapshot_abid": "snp_01JSR57M9E4AFB54260158K1MZ", "snapshot_id": "dc7f6f10-ae4d-4a7a-88e2-b39b4a89869f", "sources": [ "/data/sources/1745641261-import.txt" ], "tags": null, "tags_str": "", "timestamp": "1745641263.345312", "title": "Don\u2019t Delete \u2013 Just Don\u2019t", "url": "https://udidahan.com/2009/09/01/dont-delete-just-dont/" }