![]() This design had numerous issues which affected the users: Then when a user does a search, the app will do a full text search over all the columns of all the tables in Elasticsearch. Some of the data was also joined with data from our data warehouse before writing to Elasticsearch. Then the app would copy the data to its own Elasticsearch database, one table per file, about dozen tables in total. In the original design, the data would arrive from the source systems as CSV files to S3. ![]() The data is collected from numerous other internal systems, and it's an essential tool for customer support and sales. I inherited an application whose main job is to show on one page all information which the company has about a customer. > Collect stories of software design as error reduction. A mistake there is now a mistake for everybody. The dictate comes down-no more exceptions! If you need functionality the central abstraction doesn’t offer, then add it to the central abstraction.Īdding functionality to the central abstraction requires donning robes, burning incense, sacrifices. Much of the savings, though, comes from errors not made.Ī few holdouts claim that their oh-so-special feature needs bespoke privacy code. Some cost saving from the new privacy lens comes because feature developers no longer have to code their own privacy code. The typical S curve ensues-a few usages of the new abstraction, then a flood as folks get comfortable with it & the abstraction grows in capability, then a long tail. Software design to the rescue-we’ll build a single abstraction that everyone can use for privacy. ![]() Privacy code tends to be fiddly with lots of corner cases. Each team cares about privacy but they code their own privacy code. A large software company develops many products.
0 Comments
Leave a Reply. |