Relational databases distribute their data across many tables by normalization or according to business entities. This makes maintaining a growing database schema easier. Real-world queries often span across multiple tables, and hence joining these tables is inevitable.
PostgreSQL uses many algorithms to join tables. In this article, we will see how joins work behind the scenes from a planner perspective and understand how to optimize them.
It’s finally here, the end of season 1 of the podcast is upon us! To celebrate, Santa is bringing something special – entrepreneurship advice for all the would-be founders of the world, ages 1 to 92.
Brian Singer, co-founder & CPO of Nobl9, sits down with Dev Interrupted to help us close out season 1 with a conversation on what it takes to found your own company. Having founded a pair of companies, one of which he sold to Google, Brian has a deep understanding of what it takes to successfully found and scale a startup. More than that, he knows what VCs are looking for.
I mentioned previously that I had submitted some content to DevConf.CZ 2022 with a focus on the architecture work I’ve been doing lately.
What’s DevConf.cz?
Life was normal until 2020’s monstrously bad news – Covid – came around. Developers got out of bed, then marched to the office to crunch code as they always do. While inside of the office, they reviewed their goals, played with Git, interacted with their colleagues over a cup (or two) of coffee, and built products relevant to the functionality of the company. Many developers also had side-projects that they would go home and work on during their free time as their hobby.
While in the office, developers would be busy regurgitating code – web developers, for example, would work with PHP, SQL, CSS, Javascript, and its libraries (say, jQuery). Meanwhile, database administrators would think deeply about the performance of their database instances (they would take care of indexing and normalizing their data, or work with big data sets, etc.). Once the code was complete, they’d document it and push it over to GitHub.
Threat modeling is the ultimate shift left approach. It can be used to identify and eliminate potential vulnerabilities before a single line of code is written. Employing threat modeling methodologies should be your first step toward building networks, systems, and applications that will be secure by design. STRIDE is a model of threats that can be used as a framework in ensuring secure application design.
In our previous article from this series we talked about the example predictive analysis architecture found in an edge medical diagnosis solution for the healthcare industry.
The process was laid out how we approached the use case and how portfolio solutions are the base for researching a generic architecture. It continued by discussion how we approached the use case by researching successful customer portfolio solutions as the basis for a generic architecture.
As the author of GCeasy – Garbage collection logs analysis tool, I get to see a few interesting Garbage Collection Patterns again and again. Based on the Garbage collection pattern, you can detect the health and performance characteristics of the application instantly. In this post, let me share a few interesting Garbage collection patterns that have intrigued me.
You will see a beautiful saw-tooth GC pattern when an application is healthy, as shown in the above graph. Heap usage will keep rising; once a ‘Full GC’ event is triggered, heap usage will drop all the way to the bottom.
In the previous article in this series, we introduced the world of Codeanywhere, a cloud IDE and container development experience all available in just your browser.
Are you ready for some more amazing, easy to use, developer tooling that requires not a single tooling installation and no configuration?
Nowadays, with the rise of social media, fast internet, etc., the tendency to use applications is getting more and more. As a result of these behavior changes, monolithic applications need to deal with a tremendous majority of changes.
The testing that is done to verify the interface functionality is called Interface testing. It is also defined as a software testing type that verifies whether the communication between two different software systems is done correctly.
