Technical Lead. Passionate about cloud computing & web security | Blogger at @Medium | Freelance Mobile Developer | CKAD | AWS Community Builder ๐ฑ๐ฐ
1 Nobel Laureate
1 Central banker w/ Phd
2 Former military
1 Law professor
4 Human rights/student activists
2 Senior Legal professionals
2 Diplomats
1 Agriculture researcher
1 Psychology professor
1 Religious scholar
...
1 Friend of the President
Bangladesh did what we couldn't.
This is beyond horrific. I'm disgusted to be a human being.
Israel delivered a truck full of bodies to be buried in mass graves without any explanation.
Every single one of these videos is AI-generated, and if this doesn't concern you at least a little bit, nothing will
The newest model: https://t.co/zkDWU8Be9S
(Remember Will Smith eating spaghetti? I have so many questions)
Need low latency & high performance? Accelerate workloads with #AWS. โ๏ธ๐๏ธ
Amazon #S3 Express One Zone delivers the fastest data access in the cloud with the lowest-latency cloud #Storage. Speed up data processing & cross the finish with time to spare.
๐ https://t.co/tVrtKvWVpB
I love @SpringBoot 3.2!!
- reactive cache/scheduled abstraction
- virtual threads
- CRaC
- Spring for @apache_pulsar
- RestClient / JdbcClient
- reloadable SSL
- @GraalVM
- @java 21
- observability
- spring.main.keep-alive=true
- @Docker for @neo4j, activemq, etc
- new dependencies
- TransactionalExecutionListener
Try it out: https://t.co/1zelhVJx8l
For the full details see release notes for @springboot (1) and @springframework (2)
1. https://t.co/qyNpFRpspA
2. https://t.co/F6CuXdbGol
@AkhilaSene97 They are cricket board-paid journalists. they will receive free tours and other benefits so they just ask silly questions not the real issues
๐ง๐ผ๐ฝ ๐ฎ๐ฌ ๐ฆ๐ค๐ ๐พ๐๐ฒ๐ฟ๐ ๐ผ๐ฝ๐๐ถ๐บ๐ถ๐๐ฎ๐๐ถ๐ผ๐ป ๐๐ฒ๐ฐ๐ต๐ป๐ถ๐พ๐๐ฒ๐
Here is the list of the top 20 SQL query optimization techniques I found noteworthy:
1. Create an index on huge tables (>1.000.000) rows
2. Use EXIST() instead of COUNT() to find an element in the table
3. SELECT fields instead of using SELECT *
4. Avoid Subqueries in WHERE Clause
5. Avoid SELECT DISTINCT where possible
6. Use WHERE Clause instead of HAVING
7. Create joins with INNER JOIN (not WHERE)
8. Use LIMIT to sample query results
9. Use UNION ALL instead of UNION wherever possible
10. Use UNION where instead of WHERE ... or ... query.
11. Run your query during off-peak hours
12. Avoid using OR in join queries
14. Choose GROUP BY over window functions
15. Use derived and temporary tables
16. Drop the index before loading bulk data
16. Use materialized views instead of views
17. Avoid != or <> (not equal) operator
18. Minimize the number of subqueries
19. Use INNER join as little as possible when you can get the same output using LEFT/RIGHT join.
20. For retrieving the same dataset, frequently try to use temporary sources.
Do you know what is ๐ค๐๐ฒ๐ฟ๐ ๐ข๐ฝ๐๐ถ๐บ๐ถ๐๐ฒ๐ฟ? Its primary function is to determine ๐๐ต๐ฒ ๐บ๐ผ๐๐ ๐ฒ๐ณ๐ณ๐ถ๐ฐ๐ถ๐ฒ๐ป๐ ๐๐ฎ๐ to execute a given SQL query by finding the best execution plan. The query optimizer works by taking the SQL query as input and analyzing it to determine how best to execute it. The first step is to parse the SQL query and create a syntax tree. The optimizer then analyzes the syntax tree to determine how to run the query.
Next, the optimizer generates ๐ฎ๐น๐๐ฒ๐ฟ๐ป๐ฎ๐๐ถ๐๐ฒ ๐ฒ๐ ๐ฒ๐ฐ๐๐๐ถ๐ผ๐ป ๐ฝ๐น๐ฎ๐ป๐, which are different ways of executing the same query. Each execution plan specifies the order in which the tables should be accessed, the join methods, and any filtering or sorting operations. The optimizer then assigns a ๐ฐ๐ผ๐๐ to each execution plan based on the number of disk reads and the CPU time required to execute the query.
Finally, the optimizer ๐ฐ๐ต๐ผ๐ผ๐๐ฒ๐ ๐๐ต๐ฒ ๐ฒ๐ ๐ฒ๐ฐ๐๐๐ถ๐ผ๐ป ๐ฝ๐น๐ฎ๐ป with the lowest cost as the optimal execution plan for the query. This plan is then used to execute the query.
Check in the image the ๐ผ๐ฟ๐ฑ๐ฒ๐ฟ ๐ถ๐ป ๐๐ต๐ถ๐ฐ๐ต ๐ฆ๐ค๐ ๐พ๐๐ฒ๐ฟ๐ถ๐ฒ๐ ๐ฟ๐๐ป.
#technology #softwareengineering #programming #techworldwithmilan #sql
So many new things in @java 21 vs @java 17. A few of my favorites, in addition to Loomโs virtual ๐งตs:
- SequencedCollections and new factory methods
- Math.div* methods
- auto-close HttpClient
- BigInteger#parallelMultiply
- enhanced switch pattern matching
- record component extraction in pattern matching
- exhaustive checks in sealed types in enhanced switch
- Future#getState()
- String#indexOf(String, int start, int stop)