<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Durgadevi Subramanian on Medium]]></title>
        <description><![CDATA[Stories by Durgadevi Subramanian on Medium]]></description>
        <link>https://medium.com/@psdurgadevi?source=rss-fc52b35d91fb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*cG1a562GPey7IG27.jpg</url>
            <title>Stories by Durgadevi Subramanian on Medium</title>
            <link>https://medium.com/@psdurgadevi?source=rss-fc52b35d91fb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:28:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@psdurgadevi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Pune-Shiridi-Nashik Trip 5–7 Jun 2026]]></title>
            <link>https://medium.com/@psdurgadevi/pune-shiridi-nashik-trip-5-7-jun-2026-25b0b2c9ce01?source=rss-fc52b35d91fb------2</link>
            <guid isPermaLink="false">https://medium.com/p/25b0b2c9ce01</guid>
            <dc:creator><![CDATA[Durgadevi Subramanian]]></dc:creator>
            <pubDate>Sun, 14 Jun 2026 05:06:32 GMT</pubDate>
            <atom:updated>2026-06-14T05:09:35.621Z</atom:updated>
            <content:encoded><![CDATA[<p>5-Jun-2026 — Day 1: These three days will always hold a special place in my heart. It was pure joy to witness the love, care, and companionship around us — strangers becoming friends, and memories being created that none of us will ever forget.</p><p>We started early at 4:00 AM from Bangalore to Pune by Indigo Airbus — my first flight experience. Got a window seat and it was wonderful. Landed in Pune around 5:30 AM, collected our bags, and headed to the bus arranged by the travel group.</p><p>Around 7:30 AM, we stopped for breakfast — hot idlis with vada, chitranna, and tea served fresh.</p><p>Post breakfast, we headed towards Ranjangaon Ganapathi Temple, one of the Ashta Vinayaka temples, about 50 km from Pune airport. Due to poor road quality it took us 1.5 hours, and we reached around 9:30 AM.</p><p>The temple was closed for renovation work, so we worshipped from outside where they had arranged an LED TV for devotees to take darshan.</p><p>After darshan, we started towards Shiridi. Stopped at 11:00 AM for a tea break on the way.</p><p>Reached Shiridi at 2:00 PM, collected our room keys, kept our luggage, and had lunch — Anna, sambar, and vegetables.</p><p>Took some rest. At 4:30 PM we had tea with snacks, then started towards darshan. Kept our slippers and entered the temple through Gate №7 for free darshan. We entered the hall around 5:45 PM.</p><p>From 6:15 PM to 7:15 PM, public darshan was paused for Aarthi. After Aarthi, paid darshan was released first. Around 8:15 PM they opened our hall. It took about 40 minutes to reach the sanctum, but we had a peaceful darshan of Shiridi Sai Baba. Came out of the temple by 9:15 PM.</p><p>Did some shopping near the temple, reached our room by 10:00 PM.</p><p>Dinner was at the dining hall — roti, hakka noodles, rasa anna, and papad. After dinner, we took rest for the next day.</p><p>6-Jun-2026 — Day 2: Started early at 5:30 AM with coffee. By 6:30 AM we freshened up and headed to the temple again — captured a few photos around the premises, finished the remaining shopping, and were back at the hotel by 7:30 AM.</p><p>Breakfast was semiya upma and avalakki with tea. At 8:30 AM we started towards Trimbakeshwar Jyotirlinga Temple, Nashik.</p><p>On the way we stopped at a roadside restaurant for a tea break, then continued. Reached Trimbakeshwar Jyotirlinga, around 12:30 PM and finished lunch first.</p><p>Post lunch we went to the ticket counter for special darshan. It took about 30 minutes to get tickets, and by 2:00 PM we joined the queue.</p><p>The weather didn’t support us at all — harsh sun, slow-moving queue, and zero crowd management. People were pushing, elderly devotees struggled in the heat and thirst, and even babies were uncomfortable. It was genuinely tough for everyone.</p><p>But we held on. With the slow movement, we finally entered the temple at 5:45 PM and had a peaceful darshan of Lord Trimbakeshwar Jyotirlinga by 6:00 PM. Came out and caught our bus straight to Panchavati. Reached Panchavati at 8:15 PM.</p><p>What a place. Memories of Ram, Lakshman, and Sita’s Dandakaranya days from the Ramayana came alive. Standing before the vanavasa site of Ram, Lakshman, and Sita, every scene played out in my mind. Filled with those memories, we left Panchavati at 10:00 PM and reached our hotel by 12:00 AM.</p><p>Dinner was delicious — fried rice, gobi manchurian, puri sagu, sambar anna, papad, and custard fruit salad. Then we rested for the next day.</p><p>7-Jun-2026 — Day 3: Started early at 5:30 AM, checked out of our rooms in Shiridi, and headed towards Grishneshwar Jyotirlinga at Verul.</p><p>On the way we stopped for breakfast — had hot pongal and kesari bath. Post breakfast, we started again at 8:00 AM and reached Grishneshwar Temple by 8:30 AM.</p><p>We joined the queue. Since it was early morning, the sun was bearable and the crowd was lighter. There was still no crowd management, but the queue kept moving unlike Trimbakeshwar Jyotirlinga. Within 1 hour we entered the temple premises. The movement slowed inside, but finally we had a peaceful darshan of Mahadev at 10:15 AM.</p><p>After darshan we did some shopping and boarded the bus to Ellora, northwest of Aurangabad, Maharashtra. Ellora features 34 open-to-public rock-cut monuments carved into a basalt cliff. This ancient complex spans the 6th to 10th century CE and beautifully represents the religious harmony of Buddhism, Hinduism, and Jainism.</p><p>We spent about 2 hours there. The architecture left us stunned.</p><p>The Kailasa Temple (Cave 16): The crown jewel of Ellora and the largest single monolithic excavation in the world. A massive, free-standing temple carved top-down from a single rock face, with intricate sculptural detailing.</p><p>Buddhist Caves (1–12): Early caves with large monasteries/viharas and prayer halls/chaityas built between 600–730 CE.</p><p>Hindu Caves (13–29): Carved in early and late periods, featuring magnificent depictions of Hindu mythology, including the sprawling, cross-shaped Dumar Lena (Cave 29).</p><p>Jain Caves (30–34): From the 8th to 10th century, reflecting Jain philosophy with elaborate pillars and a massive monolithic elephant in Cave 32.</p><p>Around 2:30 PM we had lunch, then started towards Shani Shingnapur. Reached there around 4:30 PM.</p><p>It was less crowded, and within an hour we had darshan. Post darshan we had tea, boarded the bus, and started towards Pune Airport.</p><p>Reached Pune Airport at 10:15 PM, checked in, and boarded our flight at 11:30 PM. Took off at 12:20 AM and landed in Bangalore at 1:40 AM. Collected our bags, left the airport by 2:30 AM, and reached home early morning at 3:30 AM.</p><p>The Jyotirlingas along with Shiridi made goosebumps rise through my soul and body — it truly took me to heaven.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25b0b2c9ce01" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[7 days sweet memories of Dec-2025]]></title>
            <link>https://medium.com/@psdurgadevi/7-days-memories-of-2025-9d67a3bcb376?source=rss-fc52b35d91fb------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d67a3bcb376</guid>
            <dc:creator><![CDATA[Durgadevi Subramanian]]></dc:creator>
            <pubDate>Sun, 14 Jun 2026 04:05:18 GMT</pubDate>
            <atom:updated>2026-06-16T01:55:42.519Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Dec 22, 2025 — Day 1</strong>:</p><p>Began the day with a delicious lunch at Gowri Krishna Veg Restaurant. Post lunch, we visited Thiruparankundaram Temple for Lord Karthikeya’s darshan.</p><p>We ended with Jigarthanda from West Masi Street, and then headed to Madurai Food Street at Teppakulam — one place packed with authentic, tasty Madurai snacks.</p><p><strong>Dec 23, 2025 Day 2:</strong></p><p>Started early at 5:30 AM for Rameswaram via the Outer Ring Road. Clear roads and FM radio songs made the drive pleasant. Had breakfast at Vasantham Restaurant and reached Rameswaram by 9:30 AM. At 10:00 AM, we reached Agni Theertham and enjoyed boating, followed by tender coconut. By 11:30 AM, we had a peaceful darshan of Lord Shiva at Ramanathaswamy Temple through the free darshan queue.</p><p>Post darshan, we headed to Dhanushkodi and spent nearly 2 hours at the beach. As you drive, it feels surreal — <strong>like floating in the middle of the sea</strong>, with water on both sides and the sky above. The journey itself becomes a darshan, a pilgrimage of nature, leading you to <strong>Arichal Munai</strong>, the very tip of India where the land dissolves into the ocean. Standing there, you feel the vastness of creation — the roar of the waves, the silence of the horizon, and the humbling truth that you are at the <strong>end of the Indian subcontinent</strong>. <br> We then relished an amazing fish lunch at a roadside shop. A rustic fish lunch added flavor.<br> <br> Around 6:00 PM, we visited the house of Dr. A.P.J. Abdul Kalam in Rameswaram — our former President, ISRO scientist, and the ‘<strong>Missile Man of India’</strong>. Standing in the place he called home was deeply humbling. Every corner reflected his simplicity, curiosity, and love for the nation.</p><p>Around 10:00 PM, we reached Madurai Teppakulam and enjoyed ghee puttu.</p><p>On the way back home, we picked up yummy idlis from a roadside shop.</p><p><strong>Dec 24, 2025 — Day 3:</strong> <br> Started at 5:30 AM from Madurai to Kanyakumari with an extra cab for comfort. Stopped at Hotel Balaji on the highway around 7:30 AM for ghee roast dosa, soft pongal, and filter coffee — absolutely delicious! <br> By 10:00 AM, we reached Kanyakumari and began with darshan at the TTD Balaji Temple, with the cool sea breeze adding to the calm.</p><p>After Balaji darshan, we visited Bhagavathi Amman Temple and took the boat to Vivekananda Rock Memorial. The 20-minute ride and standing on the rock in the middle of the sea was magical. We had Bhagavathi Amman’s Pada darshan and visited the Vivekananda Ashram. <strong>Walking across the glass bridge to the 133-ft Thiruvalluvar Statue was thrilling</strong>. <br> From there, we captured beautiful views of the memorial rock and temple. Returned by 3:45 PM, witnessed the sangam of three seas behind Bhagavathi Amman Temple, and had her blessings after a 45-minute wait.</p><p>Lunch was at a nearby restaurant, then we drove to Suchindram for the Thanumalayan Temple. This 17th-century shrine, where Shiva, Vishnu, and Brahma are worshipped together, left us awestruck — the monolithic Hanuman statue, musical pillars, 1,035 carved pillars, and towering gopuram were highlights. We reached Nagercoil in the evening, checked into our room, and had dinner nearby.</p><p>At night, we stepped out for a walk and experienced Nagercoil lit up with full Christmas vibes. The church was beautifully illuminated, and the whole-night prayers created such a peaceful, positive energy. It made for a perfect end to the day, and we slept like a baby.</p><p><strong>Dec 25, 2025 — Day 4:<br> </strong>As usual, we started early at 5:45 AM towards Thiruvananthapuram for Anantha Padmanabha Swamy Temple. The NH66 route is known to be congested and slow — just 75 km but it can take 2 to 4 hours with bus traffic and bottlenecks at Marthandam and Kaliyakkavilai.</p><p>Hugging the coast made the drive pleasant though — sea breezes, coconut groves, rocky coastlines, and calm estuaries kept us company.<br> <br> Around 8:45 AM, we reached Thiruvananthapuram and had breakfast at Indian Coffee House. Then we joined the darshan queue without mobiles. It was a long wait of about 3.5 to 4 hours, but the peaceful darshan of Anantha Padmanabha Swamy made every minute worth it.<br> <br> Post darshan We reached our parking area by 1:30 PM ,we went to Kovalam beach, the sea water was clear and we played around 2 hours.<br> <br> Then started back towards Kanyakumari for lunch. Around 5:00 PM, we stopped on the Kanyakumari–Madurai highway for a Madurai-style (tiffin) — yummy and satisfying.<br> <br> Post lunch, we headed straight to Madurai. By 8:30 PM we reached, dropped our cab, and stepped out for dinner. Tried checking Krishna Restaurant for non-veg, but it was packed. Ended up at Sree Sabrees Veg Restaurant instead — great call! So many options and the food was delicious.<br> <br> After a nice dinner, we came home and crashed with happy, tired hearts.<br> <br> <strong>Dec 26, 2025 — Day 5:</strong> As usual, we started early at 6:30 AM towards Meenakshi Temple and reached by 7:00 AM. After depositing our mobiles and slippers, we joined the darshan queue.<br> <br> I can’t put the crowd into words — the temple was flooded with devotees. Somehow we managed to get special darshan tickets, but still waited nearly 5 hours. The temple is massive with an estimated 33,000 sculptures capturing dizzying detail from floor to ceiling. Carved from granite, wood, and stucco, they bring Hindu epics and South Indian folklore to life. With the heavy crowd, we couldn’t enjoy all of it properly.<br> <br> Adding to that, renovation work for the grand Kumbhabhishekam meant many areas were closed, so we couldn’t cover everything.<br> <br> We did get to see the sacred Golden Lotus Tank — Porthamarai Kulam — believed to have been created by Lord Shiva himself. Legend says it tests the quality of literary works.<br> <br> The temple’s outer facades are defined by its 14 towering gopurams, pyramids of color layered with multi-colored stucco figures of gods, demons, animals, and celestial dancers.</p><p>While in the queue, special puja screenings happened twice and caused another 1.5-hour delay. Finally, by 12:30 PM we had a peaceful darshan and stepped out.<br> <br> We collected our things and headed to Kumar Mess for lunch. This time we went all-in on Madurai special non-veg — so yummy! We spent about 2 hours there, savoring every bite.<br> <br> Post lunch, we explored the buzzing Masi Street Bazaar near the temple. Countless shops, endless lanes — it truly shows why Madurai is called a sleepless city. After shopping, we had coffee at A2B near Vilakuthoon, then walked to the famous Jigarthanda shop on Manjanakara Street. Locals swear by it as one of the most authentic spots for Madurai’s iconic cold dessert, and they were right.<br> <br> We returned home for a short rest. At 7:30 PM we stepped out for dinner — no confusion this time. Straight to Sree Sabrees Veg Restaurant. What variety, what hospitality! 2 days still aren’t enough to try everything. We enjoyed each dish to the fullest.<br> <br> Successfully completed 5 days and returned home for rest for next day travel.<br> <br> <strong>Dec 27, 2025 — Day 6:</strong> <br> As usual, we started early morning towards Thanjavur. The Brihadeeswara Temple, or Thanjai Periya Kovil, is a magnificent UNESCO World Heritage Site. Built entirely out of granite by Chola Emperor Rajaraja I around 1010 AD, this 1000-year-old architectural marvel is celebrated globally for its baffling engineering and massive proportions.<br> <br> On the way, we stopped at Sree Sabrees on the highway for breakfast.<br> <br> Tamil Nadu’s highways are a road tripper’s dream — bypass ring roads and flyovers let you drive from Madurai straight to Thanjavur Big Temple without urban delays.<br> <br> Around 11:00 AM, we reached the Big Temple. No words — we just stood there awestruck. The 19.5 ft, 25-ton Nandi carved from a single rock guards the entrance. The 80-ton capstone sits without cement. The 66m vimana is one of the tallest in the world. “Standing before 1000 years of history, where every stone tells a story.”<br> <br> After 60 mins we entered. The 9-ft Shiva Linga in the inner sanctum was powerful. Post darshan, we had Thanjavur’s famous full meals — absolutely yum.<br> <br> Then we drove to Gangaikonda Cholapuram. Again, empty roads — felt like they were made for us. By 3:30 PM we reached. It’s a miniature of Thanjavur Big Temple, built by Rajendra Chola. Wow architecture, once again.<br> <br> After darshan, we started towards Chidambaram for Thillai Natarajar Temple.<br> <br> <strong>Evening:</strong> Around 6:15 PM we reached Chidambaram Temple. After parking, we entered by 7:15 PM. The temple was flooded with devotees again. A special puja was going on and ended around 8:15 PM.<br> <br> We bought special darshan tickets, adjusted through the push, and had a peaceful darshan of Lord Nataraja.<br> <br> Post darshan, we reached our room by 9:00 PM, dropped bags, and went out for dinner. No big restaurant there, so we tried a small tiffin center cooking the old-school way. With a little hesitation we walked in — and wow, the dosas were amazing! Sometimes the simplest places surprise you the most.<br> <br> Then we returned to our room and rested.<br> <br> <strong>Dec 28, 2025 — Day 7:</strong> <br> As usual, we started early at 5:00 AM towards Thillai Natarajar Temple for darshan a second time. This time we explored the temple fully without rushing. After darshan, we returned to the room by 7:30 AM, packed our stuff, and started the long drive back to Bangalore.<br> <br> We stopped near Kallakurichi bus stand for breakfast — food was just average, nothing memorable.<br> <br> For lunch, we headed to Salem and had a meal at Selvi Mess. It was overcrowded, but taste-wise it was good. Can’t match Madurai flavor though!<br> <br> Post lunch, we pushed towards Bangalore. On the way we sang songs, shared trip memories, and finally reached Bangalore at 8:00 PM in the night.<br> <br> Dec 22–28, 2025–7 days, 2,341 km+ km, countless temples, 3 seas,Pongal, Ghee roast to Jigarthanda to dosa. Started as a plan, ended as a lifetime memory</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d67a3bcb376" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Springboot Annoations]]></title>
            <link>https://medium.com/@psdurgadevi/springboot-annoations-3dad8c936ea7?source=rss-fc52b35d91fb------2</link>
            <guid isPermaLink="false">https://medium.com/p/3dad8c936ea7</guid>
            <dc:creator><![CDATA[Durgadevi Subramanian]]></dc:creator>
            <pubDate>Tue, 07 Apr 2026 03:10:44 GMT</pubDate>
            <atom:updated>2026-04-07T03:11:49.025Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Core Spring</strong></p><ul><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Bean.html">@Bean</a> — Annotated method produces a bean managed by the Spring IoC container</li><li>Stereotype annotations</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/stereotype/Component.html">@Component</a> — Marks annotated class as a bean found by the component-scanning and loaded into the application context</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/stereotype/Controller.html">@Controller</a> — Marks annotated class as a bean for Spring MVC containing request handler</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/web/bind/annotation/RestController.html">@RestController</a> — Marks annotated class as a @Controller bean and adds @ResponseBody to serialize returned results as messages</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Configuration.html">@Configuration</a> — Marks annotated class as a Java configuration defining beans</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/stereotype/Service.html">@Service</a> — Marks annotated class as a bean (as convention usually containing business logic)</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/stereotype/Repository.html">@Repository</a> — Marks annotated class as a bean (as convention usually providing data access) and adds auto-translation from SQLException to DataAccessExceptions</li></ul><h4>Bean state</h4><ul><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/annotation/PostConstruct.html">@PostConstruct</a> — Annotated method is executed after dependency injection is done to perform initialization</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/annotation/PreDestroy.html">@PreDestroy</a> — Annotated method is executed before the bean is destroyed, e.g. on the shutdown</li></ul><h4>Configuration</h4><ul><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Import.html">@Import</a> — Imports one or more Java configuration classes @Configuration</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/PropertySource.html">@PropertySource</a> — Indicates the location of applicaiton.properties file to add key-value pairs to Spring Environment</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/beans/factory/annotation/Value.html">@Value</a> — Annotated fields and parameters values will be injected</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/ComponentScan.html">@ComponentScan</a> — Configures component scanning @Compenent, @Service, etc.</li></ul><h4>Bean properties</h4><ul><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Lazy.html">@Lazy</a> — Annotated bean will be lazily initialized on the first usage</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Profile.html">@Profile</a> — Indicates that beans will be only initialized if the defined profiles are active</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Scope.html">@Scope</a> — Defines bean creation scope, e.g. prototype, singleton, etc.</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/DependsOn.html">@DependsOn</a> — Explicitly defines a dependency to other beans in terms of creation order</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/core/annotation/Order.html">@Order</a> — Defines sorting order if injecting a list of beans, but it does not resolve the priority if only a single bean is expected</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Primary.html">@Primary</a> — Annotated bean will be picked if multiple beans can be autowired</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Conditional.html">@Conditional</a> — Annotated bean is created only if conditions are satisfied</li><li>Additionally available in Spring Boot:</li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/autoconfigure/condition/ConditionalOnBean.html">@ConditionalOnBean</a></li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/autoconfigure/condition/ConditionalOnMissingBean.html">@ConditionalOnMissingBean</a></li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/autoconfigure/condition/ConditionalOnClass.html">@ConditionalOnClass</a></li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/autoconfigure/condition/ConditionalOnMissingClass.html">@ConditionalOnMissingClass</a></li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/autoconfigure/condition/ConditionalOnProperty.html">@ConditionalOnProperty</a></li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/autoconfigure/condition/ConditionalOnProperty.html">@ConditionalOnMissingProperty</a></li></ul><h4>Bean injection</h4><ul><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/beans/factory/annotation/Autowired.html">@Autowired</a> — Beans are injected into annotated setters, fields, or constructor params.</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/beans/factory/annotation/Qualifier.html">@Qualifier</a> — Specifies the name of a bean as an additional condition to identify a unique candidate for autowiring</li></ul><h4>Validation</h4><ul><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/validation/Valid.html">@Valid</a> — Mark a property, method parameters or return type for validation</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/validation/annotation/Validated.html">@Validated</a> — Variant of @Valid that allows validation of multiple groups, e.g. all fields of an annotated class</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/validation/constraints/NotNull.html">@NotNull</a> — Must be not null</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/validation/constraints/NotEmpty.html">@NotEmpty</a> — Must be not null nor empty</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/validation/constraints/NotBlank.html">@NotBlank</a> — Must be not null and at least one non-whitespace character</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/validation/constraints/Digits.html">@Digits</a> — Must be a number within accepted range</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/validation/constraints/Past.html">@Past</a> — Must be an instant, date or time in the past</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/validation/constraints/Future.html">@Future</a> — Must be an instant, date or time in the future</li></ul><h3>Spring Boot</h3><ul><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/SpringBootConfiguration.html">@SpringBootConfiguration</a> — Indicates Spring Boot application @Configuration</li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/autoconfigure/EnableAutoConfiguration.html">@EnableAutoConfiguration</a> — Enables application context auto-configuration to provide possibly needed beans based on the classpath</li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/context/properties/ConfigurationProperties.html">@ConfigurationProperties</a> — Provides external binding of key value properties</li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/context/properties/ConstructorBinding.html">@ConstructorBinding</a> — Bind properties by using constructor rather than setters</li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/context/properties/ConfigurationPropertiesScan.html">@ConfigurationPropertiesScan</a> — Enables auto-detection of @ConfigurationProperties classes</li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/autoconfigure/SpringBootApplication.html">@SpringBootApplication</a> — Combination of @SpringBootConfiguration, @EnableAutoConfiguration, @ConfigurationPropertiesScan and @ComponentScan</li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/autoconfigure/domain/EntityScan.html">@EntityScan</a> — Configures base packages to scan for entity classes</li><li><a href="https://docs.spring.io/spring-data/data-jpa/docs/current/api/org/springframework/data/jpa/repository/config/EnableJpaRepositories.html">@EnableJpaRepositories</a> — Enables auto-configuration of jpa repositories</li></ul><h3>Spring Boot Tests</h3><ul><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/test/context/SpringBootTest.html">@SpringBootTest</a> — Annotated test class will load the entire application context for integration tests</li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/test/autoconfigure/web/servlet/WebMvcTest.html">@WebMvcTest</a> — Annotated test class will load only the web layer (service and data layer are ignored)</li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/test/autoconfigure/orm/jpa/DataJpaTest.html">@DataJpaTest</a> — Annotated class will load only the JPA components</li><li><a href="https://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#features.testing.spring-boot-applications.json-tests">@JsonTest</a> — Annotated class will load only json mapper for serialization and deserialization tests</li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/test/mock/mockito/MockBean.html">@MockBean</a> — Marks annotated field as a mock and loads it as a bean into the application context</li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/test/mock/mockito/SpyBean.html">@SpyBean</a> — Allows partial mocking of beans</li><li><a href="https://www.javadoc.io/doc/org.mockito/mockito-core/latest/org/mockito/Mock.html">@Mock</a> — Defines annotated field as a mock</li></ul><h3>Spring Test</h3><ul><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/test/context/ContextConfiguration.html">@ContextConfiguration</a> — Defines @Configuration to load application context for integration test</li><li><a href="https://junit.org/junit5/docs/current/api/org.junit.jupiter.api/org/junit/jupiter/api/extension/ExtendWith.html">@ExtendWith</a> — Defines extensions to execute the tests with, e.g. MockitoExtension</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/test/context/junit/jupiter/SpringJUnitConfig.html">@SpringJUnitConfig</a> — Combines @ContextConfiguration and @ExtendWith(SpringExtension.class)</li><li><a href="https://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/test/context/TestPropertySource.html">@TestPropertySource</a> — Defines the location of property files used in integration tests</li><li><a href="https://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/test/annotation/DirtiesContext.html">@DirtiesContext</a> — Indicates that annotated tests dirty the application context and will be cleaned after each test</li><li><a href="https://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/test/context/ActiveProfiles.html">@ActiveProfiles</a> — Defines which active bean definition should be loaded when initializing the test application context</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/test/context/jdbc/Sql.html">@Sql</a> — Allows defining SQL scripts and statements to be executed before and after tests</li></ul><h3>Transactions</h3><ul><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/transaction/annotation/EnableTransactionManagement.html">@EnableTransactionManagement</a> — Enables annotation-driven transaction declaration @Transactional</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/transaction/annotation/Transactional.html">@Transactional</a> — Annotated methods will be executed in a transactional manner</li></ul><h3>Spring JPA and Hibernate</h3><ul><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/Id.html">@Id</a> — Marks annotated field as a primary key of an entity</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/GeneratedValue.html">@GeneratedValue</a> — Provides generation strategy of primary keys</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/Entity.html">@Entity</a> — Marks annotated class as an entity</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/Column.html">@Column</a> — Provides additional configuration for a field, e.g. column name</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/Table.html">@Table</a> — Provides additional configuration for an entity, e.g. table name</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/PersistenceContext.html">@PersistenceContext</a> — EntityManger is injected into annotated setters and fields</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/Embedded.html">@Embedded</a> — Annotated field is instantiated as a value of an Embeddable class</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/Embeddable.html">@Embeddable</a> — Instances of an annotated class are stored as part of an entity</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/EmbeddedId.html">@EmbeddedId</a> — Marks annotated property as a composite key mapped by an embeddable class</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/AttributeOverride.html">@AttributeOverride</a> — Overrides the default mapping of a field</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/Transient.html">@Transient</a> — Annotated field is not persistent</li><li><a href="https://docs.jboss.org/hibernate/orm/5.4/javadocs/org/hibernate/annotations/CreationTimestamp.html">@CreationTimestamp</a> — Annotated field contains the timestamp when an entity was stored for the first time</li><li><a href="https://docs.jboss.org/hibernate/orm/5.4/javadocs/org/hibernate/annotations/UpdateTimestamp.html">@UpdateTimestamp</a> — Annotated field contains the timestamp when an entity was updated last time</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/ManyToOne.html">@ManyToOne</a> — Indicates N:1 relationship, the entity containing annotated field has a single relation to an entity of other class, but the other class has multiple relations</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/JoinColumn.html">@JoinColumn</a> — Indicates a column for joining entities in @ManyToOne or @OneToOne relationships at the owning side or unidirectional @OneToMany</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/OneToOne.html">@OneToOne</a> — Indicates 1:1 relationship</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/MapsId.html">@MapsId</a> — References joining columns of owning side of @ManyToOne or @OneToOne relationships to be the primary key of referencing and referenced entities</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/ManyToMany.html">@ManyToMany</a> — Indicates N:M relationship</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/JoinTable.html">@JoinTable</a> — Specifies an association using a join table</li><li><a href="https://docs.jboss.org/hibernate/orm/5.4/javadocs/org/hibernate/annotations/BatchSize.html">@BatchSize</a> — Defines size to lazy load a collection of annotated entities</li><li><a href="https://docs.jboss.org/hibernate/orm/5.4/javadocs/org/hibernate/annotations/FetchMode.html">@FetchMode</a> — Defines fetching strategy for an association, e.g. loading all entities in a single subquery</li></ul><h3>Spring Security</h3><ul><li><a href="https://docs.spring.io/spring-security/site/docs/current/api/org/springframework/security/config/annotation/web/configuration/EnableWebSecurity.html">@EnableWebSecurity</a> — Enables web security</li><li><a href="https://docs.spring.io/spring-security/site/docs/current/api/org/springframework/security/config/annotation/method/configuration/EnableGlobalMethodSecurity.html">@EnableGlobalMethodSecurity</a> — Enables method security</li><li><a href="https://docs.spring.io/spring-security/site/docs/current/api/org/springframework/security/access/prepost/PreAuthorize.html">@PreAuthorize</a> — Defines access-control expression using SpEL, which is evaluated before invoking a protected method</li><li><a href="https://docs.spring.io/spring-security/site/docs/current/api/org/springframework/security/access/prepost/PostAuthorize.html">@PostAuthorize</a> — Defines access-control expression using SpEL, which is evaluated after invoking a protected method</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/annotation/security/RolesAllowed.html">@RolesAllowed</a> — Specifies a list of security roles allowed to invoke protected method</li><li><a href="https://docs.spring.io/spring-security/site/docs/current/api/org/springframework/security/access/annotation/Secured.html">@Secured</a> — Java 5 annotation for defining method level security</li></ul><h3>Spring AOP (Aspect Oriented Programming)</h3><ul><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/EnableAspectJAutoProxy.html">@EnableAspectJAutoProxy</a> — Enables support for handling components marked with @Aspect</li><li><a href="https://javadoc.io/static/org.aspectj/aspectjrt/1.9.5/org/aspectj/lang/annotation/Aspect.html">@Aspect</a> — Declares an annotated component as an aspect containing pointcuts and advices</li><li><a href="https://javadoc.io/static/org.aspectj/aspectjrt/1.9.5/org/aspectj/lang/annotation/Before.html">@Before</a> — Declares a pointcut executed before the call is propagated to the join point</li><li><a href="https://javadoc.io/static/org.aspectj/aspectjrt/1.9.5/org/aspectj/lang/annotation/AfterReturning.html">@AfterReturning</a> — Declares a pointcut executed if the join point successfully returns a result</li><li><a href="https://javadoc.io/static/org.aspectj/aspectjrt/1.9.5/org/aspectj/lang/annotation/AfterThrowing.html">@AfterThrowing</a> — Declares a pointcut executed if the join point throws an exception</li><li><a href="https://javadoc.io/static/org.aspectj/aspectjrt/1.9.5/org/aspectj/lang/annotation/After.html">@After</a> — Declares a pointcut executed if the join point successfully returns a result or throws an exception</li><li><a href="https://javadoc.io/static/org.aspectj/aspectjrt/1.9.5/org/aspectj/lang/annotation/Around.html">@Around</a> — Declares a pointcut executed before the call giving control over the execution of the join point to the advice</li><li><a href="https://javadoc.io/static/org.aspectj/aspectjrt/1.9.5/org/aspectj/lang/annotation/Pointcut.html">@Pointcut</a> — Externalized definition a pointcut expression</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3dad8c936ea7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[All Spring Annotations Explained Cheat Sheet]]></title>
            <link>https://medium.com/@psdurgadevi/all-spring-annotations-explained-cheat-sheet-9452712ba510?source=rss-fc52b35d91fb------2</link>
            <guid isPermaLink="false">https://medium.com/p/9452712ba510</guid>
            <dc:creator><![CDATA[Durgadevi Subramanian]]></dc:creator>
            <pubDate>Sun, 22 Mar 2026 04:19:32 GMT</pubDate>
            <atom:updated>2026-03-22T04:19:32.521Z</atom:updated>
            <content:encoded><![CDATA[<p>Nowadays, there are so many spring annotations that it could become overwhelming. Spring Framework started out with XML configuration and over time it has introduced many capabilities to reduce code verbose and get things done quickly. With Spring Boot, we can do almost everything with annotations. Let’s look at all the annotations provided by the Spring Framework.</p><h3>Spring Core Annotations</h3><h3>@Configuration</h3><p>@Configuration is used on classes that define beans. @Configuration is an analog for an XML configuration file — it is configured using Java classes. A Java class annotated with @Configuration is a configuration by itself and will have methods to instantiate and configure the dependencies.</p><h3>@ComponentScan</h3><p>@ComponentScan is used with the @Configuration annotation to allow Spring to know the packages to scan for annotated components. @ComponentScan is also used to specify base packages using basePackageClasses or basePackage attributes to scan. If specific packages are not defined, scanning will occur from the package of the class that declares this annotation.</p><h3>@Autowired</h3><p>@Autowired is used to mark a dependency which Spring is going to resolve and inject automatically. We can use this annotation with a constructor, setter, or field injection.</p><h3>@Component</h3><p>@Component is used on classes to indicate a Spring component. The @Component annotation marks the Java class as a bean or component so that the component-scanning mechanism of Spring can add it into the application context.</p><h3>@Bean</h3><p>@Bean is a method-level annotation and a direct analog of the XML element. @Bean marks a factory method which instantiates a Spring bean. Spring calls these methods when a new instance of the return type is required.</p><h3>@Qualifier</h3><p>@Qualifier helps fine-tune annotation-based autowiring. There may be scenarios when we create more than one bean of the same type and want to wire only one of them with a property. This can be controlled using @Qualifier annotation along with the @Autowired annotation. We use @Qualifier along with @Autowired to provide the bean ID or bean name we want to use in ambiguous situations.</p><h3>@Primary</h3><p>We use @Primary to give higher preference to a bean when there are multiple beans of the same type. When a bean is not marked with @Qualifier, a bean marked with @Primary will be served in case on ambiquity.</p><h3>@Required</h3><p>The @Required annotation is method-level annotation, and shows that the setter method must be configured to be dependency-injected with a value at configuration time. @Required on setter methods to mark dependencies we want to populate through XML; Otherwise, BeanInitializationException will be thrown.</p><h3>@Value</h3><p>Spring @Value annotation is used to assign default values to variables and method arguments. We can read spring environment variables as well as system variables using @Value annotation. We can use @Value for injecting property values into beans. It’s compatible with the constructor, setter, and field injection.</p><h3>@DependsOn</h3><p>@DependsOn makes Spring initialize other beans before the annotated one. Usually, this behavior is automatic, based on the explicit dependencies between beans. The @DependsOn annotation may be used on any class directly or indirectly annotated with @Component or on methods annotated with @Bean.</p><h3>@Lazy</h3><p>@Lazy makes beans to initialize lazily. By default, the Spring IoC container creates and initializes all singleton beans at the time of application startup. @Lazy annotation may be used on any class directly or indirectly annotated with @Component or on methods annotated with @Bean.</p><h3>@Lookup</h3><p>A method annotated with @Lookup tells Spring to return an instance of the method’s return type when we invoke it.</p><h3>@Scope</h3><p>@Scope is used to define the scope of a @Component class or a @Bean definition. It can be either singleton, prototype, request, session, globalSession or some custom scope.</p><h3>@Profile</h3><p>Beans marked with @Profile will be initialized in the container by Spring only when that profile is active. By Default, all beans has “default” value as Profile. We can configure the name of the profile with the value argument of the annotation.</p><h3>@Import</h3><p>@Import allows to use specific @Configuration classes without component scanning. We can provide those classes with @Import‘s value argument.</p><h3>@ImportResource</h3><p>@ImportResource allows to import XML configurations with this annotation. We can specify the XML file locations with the locations argument, or with its alias, the value argument.</p><h3>@PropertySource</h3><p>@PropertySource annotation provides a convenient and declarative mechanism for adding a PropertySource to Spring’s Environment. To be used in conjunction with @Configuration classes.</p><h3>Spring MVC Annotations</h3><h3>@Controller</h3><p>The @Controller annotation is used to indicate the class is a Spring controller. This annotation is simply a specialization of the @Component class and allows implementation classes to be auto-detected through the class path scanning.</p><h3>@Service</h3><p>@Service marks a Java class that performs some service, such as executing business logic, performing calculations, and calling external APIs. This annotation is a specialized form of the @Component annotation intended to be used in the service layer.</p><h3>@Repository</h3><p>This annotation is used on Java classes that directly access the database. The @Repository annotation works as a marker for any class that fulfills the role of repository or Data Access Object. This annotation has an automatic translation feature. For example, when an exception occurs in the @Repository, there is a handler for that exception and there is no need to add a try-catch block.</p><h3>@RequestMapping</h3><p>@RequestMapping marks request handler methods inside @Controller classes. It accepts below options: path/name/value: which URL the method is mapped to.</p><ul><li>method: compatible HTTP methods.</li><li>params: filters requests based on presence, absence, or value of HTTP parameters.</li><li>headers: filters requests based on presence, absence, or value of HTTP headers.</li><li>consumes: which media types the method can consume in the HTTP request body.</li><li>produces: which media types the method can produce in the HTTP response body.</li></ul><h3>@RequestBody</h3><p>@RequestBody indicates a method parameter should be bound to the body of the web request. It maps the body of the HTTP request to an object. The body of the request is passed through an HttpMessageConverter to resolve the method argument depending on the content type of the request. The deserialization is automatic and depends on the content type of the request.</p><h3>@GetMapping</h3><p>@GetMapping is used for mapping HTTP GET requests onto specific handler methods. Specifically, @GetMapping is a composed annotation that acts as a shortcut for @RequestMapping(method = RequestMethod.GET).</p><h3>@PostMapping</h3><p>@PostMapping is used for mapping HTTP POST requests onto specific handler methods. Specifically, @PostMapping is a composed annotation that acts as a shortcut for @RequestMapping(method = RequestMethod.POST).</p><h3>@PutMapping</h3><p>@PutMapping is used for mapping HTTP PUT requests onto specific handler methods. Specifically, @PutMapping is a composed annotation that acts as a shortcut for @RequestMapping(method = RequestMethod.PUT).</p><h3>@DeleteMapping</h3><p>@DeleteMapping is used for mapping HTTP DELETE requests onto specific handler methods. Specifically, @DeleteMapping is a composed annotation that acts as a shortcut for @RequestMapping(method = RequestMethod.DELETE).</p><h3>@PatchMapping</h3><p>@PatchMapping is used for mapping HTTP PATCH requests onto specific handler methods. Specifically, @PatchMapping is a composed annotation that acts as a shortcut for @RequestMapping(method = RequestMethod.PATCH).</p><h3>@ControllerAdvice</h3><p>@ControllerAdvice is applied at the class level. For each controller, you can use @ExceptionHandler on a method that will be called when a given exception occurs. But this handles only those exceptions that occur within the controller in which it is defined. To overcome this problem, you can now use the @ControllerAdvice annotation. This annotation is used to define @ExceptionHandler, @InitBinder, and @ModelAttribute methods that apply to all @RequestMapping methods. Thus, if you define the @ExceptionHandler annotation on a method in a @ControllerAdvice class, it will be applied to all the controllers.</p><h3>@ResponseBody</h3><p>@ResponseBody on a request handler method tells Spring to converts the return value and writes it to the HTTP response automatically. It tells Spring to treat the result of the method as the response itself. The @ResponseBody annotation tells a controller that the object returned is automatically serialized into JSON and passed back into the HttpResponse object. If we annotate a @Controller class with this annotation, all request handler methods will use it.</p><h3>@ExceptionHandler</h3><p>@ExceptionHandler is used to declare a custom error handler method. Spring calls this method when a request handler method throws any of the specified exceptions. The caught exception can be passed to the method as an argument.</p><h3>@ResponseStatus</h3><p>@ResponseStatus is used to specify the desired HTTP status of the response if we annotate a request handler method with this annotation. We can declare the status code with the code argument, or its alias, the value argument.</p><h3>@PathVariable</h3><p>@PathVariable is used to indicates that a method argument is bound to a URI template variable. We can specify the URI template with the @RequestMapping annotation and bind a method argument to one of the template parts with @PathVariable.</p><h3>@RequestParam</h3><p>@RequestParam indicates that a method parameter should be bound to a web request parameter. We use @RequestParam for accessing HTTP request parameters. With @RequestParam we can specify an injected value when Spring finds no or empty value in the request. To achieve this, we have to set the defaultValue argument.</p><h3>@RestController</h3><p>@RestController combines @Controller and @ResponseBody. By annotating the controller class with @RestController annotation, we no longer need to add @ResponseBody to all the request mapping methods.</p><h3>@ModelAttribute</h3><p>@ModelAttribute is used to access elements that are already in the model of an MVC @Controller, by providing the model key.</p><h3>@CrossOrigin</h3><p>@CrossOrigin enables cross-domain communication for the annotated request handler methods. If we mark a class with it, it applies to all request handler methods in it. We can fine-tune CORS behavior with this annotation’s arguments.</p><h3>@InitBinder</h3><p>@InitBinder is a method-level annotation that plays the role of identifying the methods that initialize the WebDataBinder — a DataBinder that binds the request parameter to Java Bean objects. To customize request parameter data binding, you can use @InitBinder annotated methods within our controller. The methods annotated with @InitBinder include all argument types that handler methods support.</p><p>The @InitBinder annotated methods will get called for each HTTP request if we don’t specify the value element of this annotation. The value element can be a single or multiple form names or request parameters that the init binder method is applied to.</p><h3>Spring Boot Annotations</h3><h3>@SpringBootApplication</h3><p>@SpringBootApplication marks the main class of a Spring Boot application. This is used usually on a configuration class that declares one or more @Bean methods and also triggers auto-configuration and component scanning. The @SpringBootApplication annotation is equivalent to using @Configuration, @EnableAutoConfiguration, and @ComponentScan with their default attributes.</p><h3>@EnableAutoConfiguration</h3><p>@EnableAutoConfiguration tells Spring Boot to look for auto-configuration beans on its classpath and automatically applies them. It tells Spring Boot to “guess” how you want to configure Spring based on the jar dependencies that you have added. Since spring-boot-starter-web dependency added to classpath leads to configure Tomcat and Spring MVC, the auto-configuration assumes that you are developing a web application and sets up Spring accordingly. This annotation is used with @Configuration.</p><h3>@ConditionalOnClass and @ConditionalOnMissingClass</h3><p>The @ConditionalOnClass and @ConditionalOnMissingClass annotations let configuration be included based on the presence or absence of specific classes. With these annotations, Spring will only use the marked auto-configuration bean if the class in the annotation’s argument is present/absent. @ConditionalOnBean and @ConditionalOnMissingBean</p><p>@ConditionalOnBean and @ConditionalOnMissingBean annotations let a bean be included based on the presence or absence of specific beans.</p><h3>@ConditionalOnProperty</h3><p>@ConditionalOnProperty annotation lets configuration be included based on a Spring Environment property i.e. make conditions on the values of properties.</p><h3>@ConditionalOnResource</h3><p>@ConditionalOnResource annotation lets configuration be included only when a specific resource is present.</p><h3>@ConditionalOnWebApplication and @ConditionalOnNotWebApplication</h3><p>@ConditionalOnWebApplication and @ConditionalOnNotWebApplication annotations let configuration be included depending on whether the application is a “web application”. A web application is an application that uses a spring WebApplicationContext, defines a session scope, or has a StandardServletEnvironment.</p><h3>@ConditionalExpression</h3><p>@ConditionalExpression is used in more complex situations. Spring will use the marked definition when the SpEL expression is evaluated to true.</p><h3>@Conditional</h3><p>@Conditional is used in complex conditions, we can create a class evaluating the custom condition.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9452712ba510" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[List of frequently used annotations in Spring Boot apps]]></title>
            <link>https://medium.com/@psdurgadevi/list-of-frequently-used-annotations-in-spring-boot-apps-53885e6eeb57?source=rss-fc52b35d91fb------2</link>
            <guid isPermaLink="false">https://medium.com/p/53885e6eeb57</guid>
            <dc:creator><![CDATA[Durgadevi Subramanian]]></dc:creator>
            <pubDate>Sat, 21 Mar 2026 02:50:41 GMT</pubDate>
            <atom:updated>2026-03-21T02:50:41.296Z</atom:updated>
            <content:encoded><![CDATA[<h3>Core Spring</h3><ul><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Bean.html">@Bean</a> — Annotated method produces a bean managed by the Spring IoC container</li><li>Stereotype annotations</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/stereotype/Component.html">@Component</a> — Marks annotated class as a bean found by the component-scanning and loaded into the application context</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/stereotype/Controller.html">@Controller</a> — Marks annotated class as a bean for Spring MVC containing request handler</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/web/bind/annotation/RestController.html">@RestController</a> — Marks annotated class as a @Controller bean and adds @ResponseBody to serialize returned results as messages</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Configuration.html">@Configuration</a> — Marks annotated class as a Java configuration defining beans</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/stereotype/Service.html">@Service</a> — Marks annotated class as a bean (as convention usually containing business logic)</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/stereotype/Repository.html">@Repository</a> — Marks annotated class as a bean (as convention usually providing data access) and adds auto-translation from SQLException to DataAccessExceptions</li></ul><h4>Bean state</h4><ul><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/annotation/PostConstruct.html">@PostConstruct</a> — Annotated method is executed after dependency injection is done to perform initialization</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/annotation/PreDestroy.html">@PreDestroy</a> — Annotated method is executed before the bean is destroyed, e.g. on the shutdown</li></ul><p><strong>Configuration</strong></p><ul><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Import.html">@Import</a> — Imports one or more Java configuration classes @Configuration</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/PropertySource.html">@PropertySource</a> — Indicates the location of applicaiton.properties file to add key-value pairs to Spring Environment</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/beans/factory/annotation/Value.html">@Value</a> — Annotated fields and parameters values will be injected</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/ComponentScan.html">@ComponentScan</a> — Configures component scanning @Compenent, @Service, etc.<br><strong>Bean properties</strong></li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Lazy.html">@Lazy</a> — Annotated bean will be lazily initialized on the first usage</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Profile.html">@Profile</a> — Indicates that beans will be only initialized if the defined profiles are active</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Scope.html">@Scope</a> — Defines bean creation scope, e.g. prototype, singleton, etc.</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/DependsOn.html">@DependsOn</a> — Explicitly defines a dependency to other beans in terms of creation order</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/core/annotation/Order.html">@Order</a> — Defines sorting order if injecting a list of beans, but it does not resolve the priority if only a single bean is expected</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Primary.html">@Primary</a> — Annotated bean will be picked if multiple beans can be autowired</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/Conditional.html">@Conditional</a> — Annotated bean is created only if conditions are satisfied</li><li>Additionally available in Spring Boot:</li><li><strong>@ConditionalOnBean</strong>: The annotated bean is only created if a specific bean (of a certain type or name) <strong>already exists</strong> in the context.</li><li><em>Use Case:</em> Creating a custom audit logger only if a specific NotificationService bean is already active.</li></ul><p><strong>@ConditionalOnMissingBean</strong>: The annotated bean is only created if a bean of that type <strong>does not yet exist</strong>.</p><ul><li><em>Use Case:</em> This is the core of “default” auto-configuration. It allows you to provide a default bean (like an in-memory database) that only gets used if the user hasn’t defined their own custom one.</li><li><strong>@ConditionalOnClass</strong>: The bean is created only if a specific class is <strong>present on the classpath</strong>.</li><li><em>Use Case:</em> Automatically enabling Redis-based caching only if the Redis client library is included in your pom.xml.</li></ul><p><strong>@ConditionalOnMissingClass</strong>: The bean is created only if a specific class is <strong>not present</strong> on the classpath.</p><ul><li><em>Use Case:</em> Providing a fallback implementation when a preferred external library is missing.</li><li><strong>@ConditionalOnProperty</strong>: The bean is created if a property exists and matches a specific value.</li><li><em>Attributes:</em></li><li>name: The property key to check.</li><li>havingValue: The value the property must have (e.g., &quot;true&quot;).</li><li>matchIfMissing: If true, the bean will still be created even if the property isn&#39;t defined at all.</li><li><strong>@ConditionalOnMissingProperty</strong>: Note that there is <strong>no official annotation</strong> with this exact name in the standard Spring Boot library.</li><li><em>How to achieve this:</em> Instead, you use @ConditionalOnProperty with the attribute matchIfMissing = true and omit havingValue, or use Spring Expression Language (SpEL) with @ConditionalOnExpression to check for missing properties.<br><a href="https://docs.spring.io/spring-boot/api/java/org/springframework/boot/autoconfigure/condition/ConditionalOnMissingBean.html">@ConditionalOnResource</a>: Matches when a specific resource (e.g., a .properties or .xml file) is present on the <a href="https://docs.spring.io/spring-boot/docs/1.2.1.RELEASE/reference/html/boot-features-developing-auto-configuration.html">classpath</a>.</li><li><strong>@ConditionalOnWebApplication</strong>: Matches only if the application is a <a href="https://medium.com/@gaddamnaveen192/efficiently-handle-web-and-non-web-applications-in-spring-boot-using-conditionalonwebapplication-aea108f278d7">web application</a> (either Servlet-based or Reactive).</li><li><strong>@ConditionalOnNotWebApplication</strong>: Matches only when the application is <strong>not</strong> a web application.</li><li><strong>@ConditionalOnExpression</strong>: Matches based on a SpEL expression.</li><li><strong>@ConditionalOnJava</strong>: Matches based on the version of the Java Runtime Environment.</li><li><strong>@ConditionalOnSingleCandidate</strong>: Matches when a specific bean is already contained in the BeanFactory and a single candidate can be determined.</li><li><strong>@ConditionalOnCloudPlatform</strong>: Matches if a specific cloud platform is active (e.g., Cloud Foundry, Kubernetes).</li><li><strong>@ConditionalOnJndi</strong>: Matches if a JNDI location exists.</li></ul><p><strong>Bean Injection<br></strong><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/beans/factory/annotation/Autowired.html">@Autowired</a> — Beans are injected into annotated setters, fields, or constructor params.</p><ul><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/beans/factory/annotation/Qualifier.html">@Qualifier</a> — Specifies the name of a bean as an additional condition to identify a unique candidate for autowiring</li></ul><h4>Validation</h4><ul><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/validation/Valid.html">@Valid</a> — Mark a property, method parameters or return type for validation</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/validation/annotation/Validated.html">@Validated</a> — Variant of @Valid that allows validation of multiple groups, e.g. all fields of an annotated class</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/validation/constraints/NotNull.html">@NotNull</a> — Must be not null</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/validation/constraints/NotEmpty.html">@NotEmpty</a> — Must be not null nor empty</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/validation/constraints/NotBlank.html">@NotBlank</a> — Must be not null and at least one non-whitespace character</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/validation/constraints/Digits.html">@Digits</a> — Must be a number within accepted range</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/validation/constraints/Past.html">@Past</a> — Must be an instant, date or time in the past</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/validation/constraints/Future.html">@Future</a> — Must be an instant, date or time in the future</li></ul><p><strong>Basic Content &amp; Type Checks</strong></p><ul><li><strong>@Email</strong>: Validates that the annotated string is a well-formed <strong>email address</strong>.</li><li><strong>@Pattern</strong>: Validates that the string matches a specific <strong>regular expression</strong> (e.g., @Pattern(regexp = &quot;^[A-Z0-9]*$&quot;)).</li><li><strong>@Size</strong>: Specifies the <strong>minimum and maximum</strong> boundaries for strings, collections, maps, or arrays (e.g., @Size(min = 2, max = 10)).</li><li><strong>@Null</strong>: The exact opposite of @NotNull; ensures the field <strong>must be null</strong>.</li></ul><p><strong>Numeric Range Annotations</strong></p><ul><li><strong>@Min</strong>: Ensures the numeric value is <strong>greater than or equal</strong> to the specified minimum.</li><li><strong>@Max</strong>: Ensures the numeric value is <strong>less than or equal</strong> to the specified maximum.</li><li><strong>@Positive / @PositiveOrZero</strong>: Validates that the number is strictly <strong>positive</strong> (&gt; 0) or positive including <strong>zero</strong> (≥ 0).</li><li><strong>@Negative / @NegativeOrZero</strong>: Validates that the number is strictly <strong>negative</strong> (&lt; 0) or negative including <strong>zero</strong> (≤ 0).</li><li><strong>@DecimalMin / @DecimalMax</strong>: Similar to @Min/@Max but accepts a string value, making it useful for BigDecimal and BigInteger types.</li></ul><p><strong>Extended Date &amp; Time Checks</strong></p><ul><li><strong>@PastOrPresent</strong>: Validates that the date/time is in the <strong>past or exactly the current</strong> moment.</li><li><strong>@FutureOrPresent</strong>: Validates that the date/time is in the <strong>future or exactly the current</strong> moment.</li></ul><p><strong>Boolean &amp; Logic Checks</strong></p><ul><li><strong>@AssertTrue</strong>: The annotated element must be <strong>true</strong>. Often used on custom “is valid” methods for complex logic.</li><li><strong>@AssertFalse</strong>: The annotated element must be <strong>false</strong>.</li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/SpringBootConfiguration.html">@SpringBootConfiguration</a> — Indicates Spring Boot application @Configuration</li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/autoconfigure/EnableAutoConfiguration.html">@EnableAutoConfiguration</a> — Enables application context auto-configuration to provide possibly needed beans based on the classpath</li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/context/properties/ConfigurationProperties.html">@ConfigurationProperties</a> — Provides external binding of key value properties</li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/context/properties/ConstructorBinding.html">@ConstructorBinding</a> — Bind properties by using constructor rather than setters</li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/context/properties/ConfigurationPropertiesScan.html">@ConfigurationPropertiesScan</a> — Enables auto-detection of @ConfigurationProperties classes</li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/autoconfigure/SpringBootApplication.html">@SpringBootApplication</a> — Combination of @SpringBootConfiguration, @EnableAutoConfiguration, @ConfigurationPropertiesScan and @ComponentScan</li><li><a href="https://docs.spring.io/spring-boot/docs/current/api/org/springframework/boot/autoconfigure/domain/EntityScan.html">@EntityScan</a> — Configures base packages to scan for entity classes</li><li><a href="https://docs.spring.io/spring-data/data-jpa/docs/current/api/org/springframework/data/jpa/repository/config/EnableJpaRepositories.html">@EnableJpaRepositories</a> — Enables auto-configuration of jpa repositories</li></ul><p><strong>Transactions</strong></p><ul><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/transaction/annotation/EnableTransactionManagement.html">@EnableTransactionManagement</a> — Enables annotation-driven transaction declaration @Transactional</li><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/transaction/annotation/Transactional.html">@Transactional</a> — Annotated methods will be executed in a transactional manner</li></ul><h3>Spring Security</h3><ul><li><a href="https://docs.spring.io/spring-security/site/docs/current/api/org/springframework/security/config/annotation/web/configuration/EnableWebSecurity.html">@EnableWebSecurity</a> — Enables web security</li><li><a href="https://docs.spring.io/spring-security/site/docs/current/api/org/springframework/security/config/annotation/method/configuration/EnableGlobalMethodSecurity.html">@EnableGlobalMethodSecurity</a> — Enables method security</li><li><a href="https://docs.spring.io/spring-security/site/docs/current/api/org/springframework/security/access/prepost/PreAuthorize.html">@PreAuthorize</a> — Defines access-control expression using SpEL, which is evaluated before invoking a protected method</li><li><a href="https://docs.spring.io/spring-security/site/docs/current/api/org/springframework/security/access/prepost/PostAuthorize.html">@PostAuthorize</a> — Defines access-control expression using SpEL, which is evaluated after invoking a protected method</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/annotation/security/RolesAllowed.html">@RolesAllowed</a> — Specifies a list of security roles allowed to invoke protected method</li><li><a href="https://docs.spring.io/spring-security/site/docs/current/api/org/springframework/security/access/annotation/Secured.html">@Secured</a> — Java 5 annotation for defining method level security</li></ul><h3>Spring AOP</h3><ul><li><a href="https://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/context/annotation/EnableAspectJAutoProxy.html">@EnableAspectJAutoProxy</a> — Enables support for handling components marked with @Aspect</li><li><a href="https://javadoc.io/static/org.aspectj/aspectjrt/1.9.5/org/aspectj/lang/annotation/Aspect.html">@Aspect</a> — Declares an annotated component as an aspect containing pointcuts and advices</li><li><a href="https://javadoc.io/static/org.aspectj/aspectjrt/1.9.5/org/aspectj/lang/annotation/Before.html">@Before</a> — Declares a pointcut executed before the call is propagated to the join point</li><li><a href="https://javadoc.io/static/org.aspectj/aspectjrt/1.9.5/org/aspectj/lang/annotation/AfterReturning.html">@AfterReturning</a> — Declares a pointcut executed if the join point successfully returns a result</li><li><a href="https://javadoc.io/static/org.aspectj/aspectjrt/1.9.5/org/aspectj/lang/annotation/AfterThrowing.html">@AfterThrowing</a> — Declares a pointcut executed if the join point throws an exception</li><li><a href="https://javadoc.io/static/org.aspectj/aspectjrt/1.9.5/org/aspectj/lang/annotation/After.html">@After</a> — Declares a pointcut executed if the join point successfully returns a result or throws an exception</li><li><a href="https://javadoc.io/static/org.aspectj/aspectjrt/1.9.5/org/aspectj/lang/annotation/Around.html">@Around</a> — Declares a pointcut executed before the call giving control over the execution of the join point to the advice</li><li><a href="https://javadoc.io/static/org.aspectj/aspectjrt/1.9.5/org/aspectj/lang/annotation/Pointcut.html">@Pointcut</a> — Externalized definition a pointcut expression</li></ul><h3>Spring JPA and Hibernate</h3><ul><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/Id.html">@Id</a> — Marks annotated field as a primary key of an entity</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/GeneratedValue.html">@GeneratedValue</a> — Provides generation strategy of primary keys</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/Entity.html">@Entity</a> — Marks annotated class as an entity</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/Column.html">@Column</a> — Provides additional configuration for a field, e.g. column name</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/Table.html">@Table</a> — Provides additional configuration for an entity, e.g. table name</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/PersistenceContext.html">@PersistenceContext</a> — EntityManger is injected into annotated setters and fields</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/Embedded.html">@Embedded</a> — Annotated field is instantiated as a value of an Embeddable class</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/Embeddable.html">@Embeddable</a> — Instances of an annotated class are stored as part of an entity</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/EmbeddedId.html">@EmbeddedId</a> — Marks annotated property as a composite key mapped by an embeddable class</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/AttributeOverride.html">@AttributeOverride</a> — Overrides the default mapping of a field</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/Transient.html">@Transient</a> — Annotated field is not persistent</li><li><a href="https://docs.jboss.org/hibernate/orm/5.4/javadocs/org/hibernate/annotations/CreationTimestamp.html">@CreationTimestamp</a> — Annotated field contains the timestamp when an entity was stored for the first time</li><li><a href="https://docs.jboss.org/hibernate/orm/5.4/javadocs/org/hibernate/annotations/UpdateTimestamp.html">@UpdateTimestamp</a> — Annotated field contains the timestamp when an entity was updated last time</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/ManyToOne.html">@ManyToOne</a> — Indicates N:1 relationship, the entity containing annotated field has a single relation to an entity of other class, but the other class has multiple relations</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/JoinColumn.html">@JoinColumn</a> — Indicates a column for joining entities in @ManyToOne or @OneToOne relationships at the owning side or unidirectional @OneToMany</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/OneToOne.html">@OneToOne</a> — Indicates 1:1 relationship</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/MapsId.html">@MapsId</a> — References joining columns of owning side of @ManyToOne or @OneToOne relationships to be the primary key of referencing and referenced entities</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/ManyToMany.html">@ManyToMany</a> — Indicates N:M relationship</li><li><a href="https://javaee.github.io/javaee-spec/javadocs/javax/persistence/JoinTable.html">@JoinTable</a> — Specifies an association using a join table</li><li><a href="https://docs.jboss.org/hibernate/orm/5.4/javadocs/org/hibernate/annotations/BatchSize.html">@BatchSize</a> — Defines size to lazy load a collection of annotated entities</li><li><a href="https://docs.jboss.org/hibernate/orm/5.4/javadocs/org/hibernate/annotations/FetchMode.html">@FetchMode</a> — Defines fetching strategy for an association, e.g. loading all entities in a single subquery</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53885e6eeb57" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reducing Database Backup Time and Improving Performance in DB2]]></title>
            <link>https://medium.com/@psdurgadevi/reducing-database-backup-time-and-improving-performance-in-db2-59b0aa46725c?source=rss-fc52b35d91fb------2</link>
            <guid isPermaLink="false">https://medium.com/p/59b0aa46725c</guid>
            <dc:creator><![CDATA[Durgadevi Subramanian]]></dc:creator>
            <pubDate>Sat, 21 Mar 2026 02:31:50 GMT</pubDate>
            <atom:updated>2026-03-21T02:31:50.465Z</atom:updated>
            <content:encoded><![CDATA[<p>Multi-Partitioned Tables, Data Migration, and Index Lifecycle Optimization</p><p>Overview</p><p>Efficient management of large-scale databases is a critical concern for organizations relying on IBM Db2, especially as data volumes grow and backup windows shrink. Traditional monolithic table structures and legacy index designs can lead to prolonged backup times, increased maintenance overhead, and suboptimal query performance. Modern versions of Db2 (including LUW 11.5/12.1 and z/OS 12.x) provide advanced partitioning, data migration, and index management features that, when properly leveraged, can dramatically reduce backup durations and enhance overall system performance.</p><p>This technical documentation report provides a comprehensive, step-by-step guide to reducing Db2 backup time and improving performance by:</p><ul><li>Creating new tables with multi-partitioning schemes</li><li>Migrating existing data efficiently</li><li>Dropping and recreating indexes with optimal strategies</li></ul><p>The report details the rationale, benefits, best practices, and key considerations for each step, drawing on the latest IBM documentation, expert analyses, and real-world case studies. It is structured for database administrators, architects, and technical leads seeking to modernize their Db2 environments for scalability, maintainability, and operational excellence.</p><p>Objectives</p><p>The primary objectives of this process are:</p><ul><li><strong>Reduce database backup time</strong> by enabling parallelism, per-partition backups, and more granular maintenance.</li><li><strong>Improve overall Db2 performance</strong> through partition elimination, optimized index design, and efficient data placement.</li><li><strong>Facilitate efficient data migration</strong> from legacy or non-partitioned tables to modern, partitioned structures.</li><li><strong>Minimize downtime</strong> during migration and index operations by leveraging online utilities and deferred index creation.</li><li><strong>Establish best practices</strong> for partitioning, index lifecycle management, and backup optimization in both Db2 LUW and z/OS environments.</li></ul><p>DB2 Table Partitioning: Overview and Impact on Backup</p><p>Table Partitioning Concepts</p><p><strong>Table partitioning</strong> in Db2 is a data organization scheme where table data is divided across multiple storage objects (partitions) based on the values of one or more key columns. Each partition is stored separately, often in its own tablespace, and can be managed independently.</p><p>Partitioning enables:</p><ul><li><strong>Efficient roll-in/roll-out</strong> of data (e.g., for time-based data retention)</li><li><strong>Parallel query and maintenance operations</strong></li><li><strong>Partition-level backup and restore</strong></li><li><strong>Improved query performance via partition elimination</strong></li></ul><p><strong>Partitioned tables</strong> can contain thousands of partitions, each mapped to specific value ranges or hash buckets, and can be distributed across multiple database partitions in a DPF (Database Partitioning Feature) environment.</p><p>Impact on Backup Operations</p><p>Partitioning fundamentally changes the backup paradigm:</p><ul><li><strong>Parallelism:</strong> Each partition (or tablespace) can be backed up in parallel, dramatically reducing total backup time.</li><li><strong>Selective Backup:</strong> Only changed or critical partitions need to be backed up, minimizing data movement and storage requirements.</li><li><strong>Reduced Contention:</strong> Maintenance operations (REORG, RUNSTATS, etc.) can be performed on individual partitions, reducing system-wide impact.</li></ul><p><strong>Table space-level backups</strong> are especially practical for large, multi-terabyte databases, where full database backups are often impractical due to time and resource constraints.</p><p>DB2 Partitioning Types and Selection Criteria</p><p>Db2 supports several partitioning and data distribution schemes, each suited to different data and workload characteristics:</p><p><strong>Selection Criteria:</strong></p><ul><li><strong>HASH partitioning</strong> ensures even data distribution, reducing hotspots and balancing I/O.</li></ul><p><strong>Best Practice:</strong> Choose partitioning keys that align with common query predicates and maintenance operations. For example, partitioning sales data by month enables efficient archiving and backup of historical data.</p><p>Creating Multi-Partitioned Tables and Tablespace Placement</p><p>Table Creation Syntax and Examples</p><p>To create a partitioned table in Db2 LUW:</p><p>CREATE TABLE sales ( id INT, sale_date DATE, amount DECIMAL(10,2) ) IN ts_jan, ts_feb, ts_mar PARTITION BY RANGE (sale_date) ( STARTING FROM (‘2026–01–01’) ENDING AT (‘2026–03–31’) EVERY (1 MONTH) );</p><p>This example creates a table with three partitions, each mapped to a different tablespace for January, February, and March.</p><p><strong>Key Points:</strong></p><ul><li><strong>Tablespace Placement:</strong> Each partition can be placed in a separate tablespace, allowing for independent backup, restore, and storage optimization.</li><li><strong>Page and Extent Size:</strong> All tablespaces used must have the same page size, extent size, and storage type.</li><li><strong>Partition Count:</strong> Db2 supports up to 32,767 partitions per table.</li></ul><p>Partitioned Database Environments (DPF)</p><p>In DPF environments, data can be distributed across multiple database partitions (nodes) using the DISTRIBUTE BY clause:</p><p>Table-Controlled vs. Index-Controlled Partitioning</p><p>Modern Db2 versions recommend <strong>table-controlled partitioning (TCP)</strong>, where partition boundaries are defined in the CREATE TABLE statement. This approach is more flexible and eliminates the need for special partitioning indexes required by legacy index-controlled partitioning (ICP).</p><p><strong>Best Practice:</strong> Always use table-controlled partitioning for new tables. Convert legacy ICP tables to TCP for improved manageability and performance.</p><p>Migrating Existing Data: Strategies and Tools</p><p>Migrating data from non-partitioned tables (or legacy partitioning schemes) to new multi-partitioned tables is a multi-step process. The main strategies include:</p><p>1. LOAD FROM CURSOR</p><p>The LOAD FROM CURSOR command allows direct data movement from a source table (or query) into a target partitioned table without intermediate files:</p><p>DECLARE c1 CURSOR FOR SELECT * FROM old_table; LOAD FROM c1 OF CURSOR INSERT INTO new_partitioned_table;</p><p><strong>Advantages:</strong></p><ul><li>No intermediate export/import files required</li><li>Supports parallelism and high throughput</li><li>Can be used across databases with federation or remote fetch options</li></ul><p>2. EXPORT/IMPORT or High-Performance Unload</p><p>For very large tables or cross-platform migrations, use EXPORT to dump data to files, then IMPORT or LOAD into the new partitioned table. IBM’s High Performance Unload tool can accelerate this process for massive datasets.</p><p>3. Converting UNION ALL Views and ATTACH/DETACH</p><p>Legacy systems often use UNION ALL views to simulate partitioning. Modern Db2 allows these to be converted to true partitioned tables using the ALTER TABLE … ATTACH PARTITION statement:</p><ul><li>Create a new partitioned table with a dummy partition</li><li>Attach each source table as a new partition</li><li>Drop the dummy partition</li><li>Use SET INTEGRITY to validate and activate the data</li></ul><p><strong>Example:</strong></p><p>ALTER TABLE sales_dp ATTACH PARTITION STARTING FROM (‘2026–01–01’) ENDING AT (‘2026–01–31’) FROM sales_jan2026; SET INTEGRITY FOR sales_dp IMMEDIATE CHECKED;</p><p>4. ATTACH/DETACH Partition Operations</p><ul><li><strong>ATTACH:</strong> Incorporates an existing table as a new partition in a partitioned table, with no data movement.</li><li><strong>DETACH:</strong> Removes a partition from a partitioned table, creating a standalone table for archiving or further processing.</li></ul><p><strong>Best Practice:</strong> Use ATTACH/DETACH for efficient roll-in/roll-out of data, minimizing downtime and I/O.</p><p>Index Lifecycle During Migration: Drop, Defer, and Recreate Strategies</p><p>Rationale for Index Management</p><p>Indexes can significantly impact data migration and backup performance. Maintaining indexes during large data loads or migration can cause excessive overhead, logging, and contention. The recommended approach is:</p><ol><li><strong>Drop or defer index creation</strong> before bulk data movement</li><li><strong>Load or migrate data</strong> into the new partitioned table</li><li><strong>Recreate indexes</strong> with optimal definitions and placement after data is loaded</li></ol><p>Index Creation Modes During LOAD</p><p>Db2’s LOAD utility supports several index creation modes:</p><ul><li><strong>REBUILD:</strong> Rebuilds all indexes after data load (default for LOAD REPLACE)</li><li><strong>INCREMENTAL:</strong> Extends existing indexes with new data (used when the ratio of new to existing data is low)</li><li><strong>DEFERRED:</strong> Defers index creation; indexes must be rebuilt manually after load</li><li><strong>AUTOSELECT:</strong> Db2 chooses REBUILD or INCREMENTAL based on data volume</li></ul><p><strong>Best Practice:</strong> Use DEFERRED or drop indexes before large loads to maximize throughput. Rebuild indexes after data is loaded, using parallelism and optimized settings.</p><p>Online Index Creation and REORG</p><ul><li><strong>Online index creation</strong> allows indexes to be built while the table remains available for queries, minimizing downtime.</li><li><strong>REORG utility</strong> can rebuild indexes and reorganize data for optimal clustering and performance, with both online and offline modes available.</li></ul><p>Index Rebuild and Placement</p><ul><li>Use the REBUILD INDEX utility to reconstruct indexes or index partitions after migration or ATTACH/DETACH operations.</li><li>Place indexes in dedicated tablespaces to optimize I/O and enable independent backup/restore.</li><li>For partitioned tables, create <strong>partitioned indexes</strong> to align with table partitions, enabling partition-level maintenance and backup.</li></ul><p>Index Design Considerations for Partitioned Tables</p><p>Padded vs. Non-Padded Indexes</p><ul><li><strong>PADDED:</strong> Varying-length columns in the index key are padded to their maximum length. This can increase index size but may improve key comparison speed.</li><li><strong>NOT PADDED:</strong> Only actual data is stored, reducing index size and enabling index-only access for varying-length columns. However, key comparisons may be slower.</li></ul><p><strong>Best Practice:</strong> Use NOT PADDED for indexes on varying-length columns to enable index-only access and reduce storage requirements, unless specific performance testing suggests otherwise.</p><p>Index Page Sizes and Compression</p><ul><li>Choose appropriate <strong>page sizes</strong> (4K, 8K, 16K, 32K) based on index key length and access patterns.</li><li>Enable <strong>index compression</strong> for large or scan-heavy indexes to reduce storage and I/O.</li></ul><p>Partitioned vs. Non-Partitioned Indexes</p><ul><li><strong>Partitioned Indexes:</strong> Each partition contains keys for its corresponding table partition, enabling partition-level maintenance and backup.</li><li><strong>Non-Partitioned Indexes:</strong> Single index structure spans all table partitions; may become a bottleneck for very large tables.</li></ul><p><strong>Best Practice:</strong> Prefer partitioned indexes for large, partitioned tables to maximize parallelism and minimize contention.</p><p>Index Placement</p><ul><li>Place indexes in separate tablespaces from data to reduce I/O contention.</li><li>Use different buffer pools for indexes and data to optimize caching and throughput.</li></ul><p>Backup Optimization Parameters and Strategies</p><p>Key Parameters</p><p><strong>Best Practice:</strong> Use multiple target devices and increase PARALLELISM to match the number of tablespaces or partitions being backed up. Monitor system resource usage to avoid contention.</p><p>Registry Variables and Performance Flags</p><ul><li><strong>DB2_REDUCE_FLUSHING_DURING_BACKUP:</strong> Reduces bufferpool flushing during online backups, improving performance.</li><li><strong>DB2_BACKUP_USE_DIO:</strong> Enables direct I/O for backup files, bypassing OS cache (especially beneficial on Linux).</li><li><strong>DB2_BACKUP_ITP (Db2 LUW 12.1+):</strong> Enables intra-tablespace parallelism for backup, further reducing backup time for large tablespaces.</li></ul><p><strong>Best Practice:</strong> Set these variables as appropriate for your platform and workload. Changes take effect on the next backup and do not require instance restart.</p><p>Table Space and Per-Partition Backup</p><ul><li>Use the BACKUP DATABASE … TABLESPACE (ts1, ts2, …) command to back up only selected tablespaces.</li><li>In DPF environments, use the ALL DBPARTITIONNUMS clause to ensure backups are taken on all relevant partitions.</li></ul><p><strong>Best Practice:</strong> For very large databases, schedule rolling backups of different partitions/tablespaces to minimize impact on production workloads.</p><p>Bufferpool, I/O, and Storage Tuning</p><p>Bufferpool Sizing and Placement</p><ul><li>Assign separate buffer pools for tablespaces containing data and indexes.</li><li>Size buffer pools to fit the working set of frequently accessed data and indexes.</li><li>Use large page sizes (1M, 2G) for high-I/O workloads to improve TLB hit ratios and reduce CPU usage.</li></ul><p>Storage Layout</p><ul><li>Distribute tablespaces and indexes across multiple physical storage devices to maximize I/O throughput.</li><li>Use SSDs or high-performance storage for active partitions and indexes.</li><li>For backups, use multiple target devices to parallelize data movement.</li></ul><p>Monitoring and Simulation</p><ul><li>Use Db2’s Buffer Pool Analyzer and simulation features to model the impact of buffer pool changes before implementation.</li><li>Monitor buffer pool hit ratios, page residency times, and deferred write thresholds to identify tuning opportunities.</li></ul><p>Db2 Utilities and Tools</p><p><strong>Best Practice:</strong> Run RUNSTATS after major data loads, index rebuilds, or partition operations to ensure accurate statistics. Use REORG to maintain data and index organization, especially after large migrations or partition changes.</p><p>SET INTEGRITY, Constraints, and SYSCAT.COLUMNS.IMPLICITVALUE</p><p>SET INTEGRITY Statement</p><p>The SET INTEGRITY statement is used to:</p><ul><li>Bring tables out of integrity pending state after LOAD, ATTACH, or DETACH operations</li><li>Perform incremental or full integrity checking</li><li>Generate identity or computed column values as needed</li></ul><p><strong>Key Options:</strong></p><ul><li>IMMEDIATE CHECKED: Performs required integrity processing</li><li>IMMEDIATE UNCHECKED: Bypasses integrity checks (use with caution)</li><li>FOR EXCEPTION IN … USE …: Moves violating rows to exception tables</li><li>GENERATE IDENTITY / FORCE GENERATED: Recomputes generated columns</li></ul><p><strong>Best Practice:</strong> Use FOR EXCEPTION to handle constraint violations gracefully. Use IMMEDIATE UNCHECKED only if data integrity has been validated externally.</p><p>SYSCAT.COLUMNS.IMPLICITVALUE</p><ul><li>Ensure that source and target tables involved in ATTACH operations have matching column definitions and implicit values.</li><li>Avoid using ALTER TABLE … ADD COLUMN on target tables after creation, as this can cause mismatches and prevent partition attachment.</li></ul><p>Transactional, Locking, and Concurrency Implications</p><ul><li>Use appropriate isolation levels (e.g., CS, RS, UR) to minimize locking contention during migration and backup operations.</li><li>For large batch updates or loads, use frequent commits and restart logic to ensure recoverability and minimize lock escalation.</li><li>Page-level locking is generally preferred for partitioned tables to balance concurrency and performance.</li></ul><p><strong>Best Practice:</strong> Schedule migration and index rebuild operations during low-activity windows to minimize impact on concurrent workloads.</p><p>Testing, Validation, Rollback, and Recovery Planning</p><ul><li><strong>Testing:</strong> Validate migration scripts and backup/restore procedures in a non-production environment.</li><li><strong>Validation:</strong> Use row counts, checksums, and parallel reporting to ensure data consistency after migration.</li><li><strong>Rollback:</strong> Maintain recent backups and use point-in-time recovery features to enable rollback if issues are detected.</li><li><strong>Recovery:</strong> Document and test recovery procedures for both full and partition-level restores.</li></ul><p><strong>Best Practice:</strong> Automate validation and rollback steps where possible to reduce human error and downtime.</p><p>Performance Measurement and Monitoring</p><ul><li><strong>Baseline:</strong> Collect performance metrics (backup time, query response, I/O throughput) before migration for comparison.</li><li><strong>Monitoring:</strong> Use Db2 monitoring tools (e.g., MON_GET, SYSIBMADM views) to track backup progress, buffer pool usage, and index health.</li><li><strong>After Migration:</strong> Compare post-migration metrics to baseline to quantify improvements in backup time and performance.</li></ul><p><strong>Best Practice:</strong> Regularly review backup logs and performance reports to identify bottlenecks and guide further optimization.</p><p>Hardware and Storage Considerations</p><ul><li><strong>Multiple Target Devices:</strong> Use multiple backup targets (disks, tapes, cloud storage) to parallelize backup and restore operations.</li><li><strong>Storage Layout:</strong> Distribute tablespaces and indexes across different storage volumes to maximize I/O bandwidth.</li><li><strong>Throughput:</strong> Monitor and tune storage subsystem throughput to avoid bottlenecks during backup, load, and index rebuild operations.</li></ul><p><strong>Best Practice:</strong> Plan storage upgrades and layout changes in conjunction with partitioning and migration projects for maximum impact.</p><p>Production Rollout Checklist and Best Practices</p><p>Version-Specific Features and Compatibility</p><ul><li><strong>Db2 LUW 12.1:</strong> Enhanced backup performance with intra-tablespace parallelism (DB2_BACKUP_ITP), improved manageability, and AI-powered query optimization.</li><li><strong>Db2 z/OS 12.x:</strong> Continued support for table-controlled partitioning, online utilities, and advanced index management.</li><li><strong>Deprecated Features:</strong> Avoid index-controlled partitioning and legacy utilities; migrate to modern equivalents for long-term support.</li></ul><p><strong>Best Practice:</strong> Regularly review IBM’s release notes and support timelines to plan upgrades and avoid end-of-support risks.</p><p>Registry Variables and Performance Flags Affecting Backup and Online Operations</p><p><strong>Best Practice:</strong> Tune these variables based on workload, platform, and backup requirements. Test changes in a controlled environment before production rollout.</p><p>Real-World Examples and Case Studies</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59b0aa46725c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DEVIN AI]]></title>
            <link>https://medium.com/@psdurgadevi/devin-ai-49e9f8830651?source=rss-fc52b35d91fb------2</link>
            <guid isPermaLink="false">https://medium.com/p/49e9f8830651</guid>
            <dc:creator><![CDATA[Durgadevi Subramanian]]></dc:creator>
            <pubDate>Mon, 25 Mar 2024 03:47:58 GMT</pubDate>
            <atom:updated>2024-03-25T03:47:58.724Z</atom:updated>
            <content:encoded><![CDATA[<p>What is Devin AI?</p><p>Devin AI, introduced by Cognition, stands as a groundbreaking advancement in the world of software development. It represents the world’s first AI software engineer, redefining the traditional paradigms of coding and machine learning.</p><p><a href="https://rgkarmch.org/what-is-devin-ai">Devin AI</a> is not merely an assistant but a full-fledged teammate, capable of autonomously handling entire projects from conceptualization to deployment, thereby streamlining the software development process.</p><p>It can handle entire projects autonomously, from concept to code, streamlining the development process and allowing human developers to focus on strategic thinking and innovation.</p><p>Key Components and Capabilities of Devin AI</p><p>Devin AI’s capabilities as an AI software engineer stem from a combination of key components:</p><ul><li>Natural Language Processing (NLP): This allows Devin to understand the human element of software development. It can interpret your descriptions, translate natural language instructions into functional code, and potentially even grasp design concepts you outline verbally.</li><li>Machine Learning (ML): This is the engine that drives Devin’s continuous learning and improvement. By analysing vast amounts of code, data, and development patterns, Devin refines its coding skills, learns new functionalities, and adapts to various programming languages.</li><li>Advanced Reasoning and Planning: Unlike simpler coding assistants, Devin can tackle complex projects with long-term planning capabilities. It breaks down projects, strategizes development, and guides decisions during coding.</li><li>Real-World Development Tools: Devin isn’t confined to a closed system. It can access and utilise a virtualized environment with a code editor, terminal, and web browser.</li></ul><p>Benefits of using Devin AI in Software Development</p><p>Devin AI boasts a range of benefits that can significantly enhance the software development process.</p><p>Enhanced Efficiency:</p><ul><li>Automation Powerhouse: Devin excels at automating repetitive tasks like code generation and deployment, freeing up valuable time for human developers to focus on more complex problem-solving and core functionalities.</li><li>Faster Development Cycles: The automation capabilities and streamlined workflow Devin offers can lead to significantly faster completion times for software projects.</li></ul><p>Improved Accuracy and Quality:</p><ul><li>Reduced Errors: Devin’s ability to analyse and debug code effectively minimises the risk of human errors creeping into the development process, leading to higher quality software.</li><li>Consistent Performance: Unlike human developers who might experience fatigue or creative roadblocks, Devin delivers consistent performance, ensuring reliable and predictable development progress.</li></ul><p>Unlocking New Possibilities:</p><ul><li>Democratizing Development: Devin’s ability to translate natural language descriptions into code opens doors for those who may not have extensive coding experience. This could lead to a more diverse pool of software developers.</li><li>Fueling Innovation: By handling routine tasks, Devin allows developers to dedicate more time to creative endeavours and exploration of new technologies, fostering a more innovative development environment.</li></ul><p>Strengthening Collaboration:</p><ul><li>Human-AI Partnership: Devin is designed to complement, not replace, human developers. Its ability to collaborate effectively with human counterparts fosters a powerful team dynamic, leveraging the strengths of both AI and human intelligence.</li><li>Improved Communication: Devin’s real-time progress reports and openness to feedback can enhance communication between human team members, leading to a more streamlined development flow.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49e9f8830651" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS Certified Solutions Architect Associate Exam (SAA-C03)]]></title>
            <link>https://medium.com/@psdurgadevi/aws-certified-solutions-architect-associate-exam-saa-c03-a447b81a0563?source=rss-fc52b35d91fb------2</link>
            <guid isPermaLink="false">https://medium.com/p/a447b81a0563</guid>
            <dc:creator><![CDATA[Durgadevi Subramanian]]></dc:creator>
            <pubDate>Tue, 20 Feb 2024 17:42:04 GMT</pubDate>
            <atom:updated>2024-02-20T17:42:04.191Z</atom:updated>
            <content:encoded><![CDATA[<h3>What are the topics that are in the scope of the SAA-C03 exam?</h3><h3>Domain 1: Design Secure Architectures</h3><p>This exam domain focuses on securing your AWS architectures and accounts for 30% of the exam. Task Statements include:</p><ul><li>Design secure access to AWS resources.</li><li>Design secure workloads and applications.</li><li>Determine appropriate data security controls.</li></ul><h3>Domain 2: Design Resilient Architectures</h3><p>This exam domain focuses on designing resilient architectures on AWS and accounts for 26% of the exam. Task</p><p>Statements include:</p><ul><li>Design scalable and loosely coupled architectures.</li><li>Design highly available and/or fault-tolerant architectures.</li></ul><h3>Domain 3: Design High-Performing Architectures</h3><p>This exam domain focuses on creating high-performance architectures on AWS and accounts for 24% of the exam. Task Statements include:</p><ul><li>Determine high-performing and/or scalable storage solutions.</li><li>Design high-performing and elastic compute solutions.</li><li>Determine high-performing database solutions.</li><li>Determine high-performing and/or scalable network architectures.</li><li>Determine high-performing data ingestion and transformation solutions.</li></ul><h3>Domain 4: Design Cost-Optimized Architectures</h3><p>This exam domain focuses on optimizing solutions for cost-effectiveness on AWS and accounts for 20% of the exam. Task statements include:</p><ul><li>Design cost-optimized storage solutions.</li><li>Design cost-optimized compute solutions.</li><li>Design cost-optimized database solutions.</li><li>Design cost-optimized network architectures.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7Rdfhb3UlFg3Xf5j.png" /></figure><p>First off, this list is quite long so brace yourselves! But please don’t be frustrated and get scared by its sheer length. With proper training and study strategy, you would be able to adequately cover these topics on your review:</p><h3>Analytics:</h3><ul><li>Amazon Athena</li><li>AWS Data Exchange</li><li>AWS Data Pipeline</li><li>Amazon EMR</li><li>AWS Glue</li><li>Amazon Kinesis</li><li>AWS Lake Formation</li><li>Amazon Managed Streaming for Apache Kafka (Amazon MSK)</li><li>Amazon OpenSearch Service (Amazon Elasticsearch Service)</li><li>Amazon QuickSight</li><li>Amazon Redshift</li></ul><h3>Application Integration:</h3><ul><li>Amazon AppFlow</li><li>AWS AppSync</li><li>Amazon EventBridge (Amazon CloudWatch Events)</li><li>Amazon MQ</li><li>Amazon Simple Notification Service (Amazon SNS)</li><li>Amazon Simple Queue Service (Amazon SQS)</li><li>AWS Step Functions</li></ul><h3>AWS Cost Management:</h3><ul><li>AWS Budgets</li><li>AWS Cost and Usage Report</li><li>AWS Cost Explorer</li><li>Savings Plans</li></ul><h3>Compute:</h3><ul><li>AWS Batch</li><li>Amazon EC2</li><li>Amazon EC2 Auto Scaling</li><li>AWS Elastic Beanstalk</li><li>AWS Outposts</li><li>AWS Serverless Application Repository</li><li>VMware Cloud on AWS</li><li>AWS Wavelength</li></ul><h3>Containers:</h3><ul><li>Amazon Elastic Container Registry (Amazon ECR)</li><li>Amazon Elastic Container Service (Amazon ECS)</li><li>Amazon ECS Anywhere</li><li>Amazon Elastic Kubernetes Service (Amazon EKS)</li><li>Amazon EKS Anywhere</li><li>Amazon EKS Distro</li></ul><h3>Database:</h3><ul><li>Amazon Aurora</li><li>Amazon Aurora Serverless</li><li>Amazon DocumentDB (with MongoDB compatibility)</li><li>Amazon DynamoDB</li><li>Amazon ElastiCache</li><li>Amazon Keyspaces (for Apache Cassandra)</li><li>Amazon Neptune</li><li>Amazon Quantum Ledger Database (Amazon QLDB)</li><li>Amazon RDS</li><li>Amazon Redshift</li><li>Amazon Timestream</li></ul><h3>Developer Tools:</h3><ul><li>AWS X-Ray</li></ul><h3>Front-End Web and Mobile:</h3><ul><li>AWS Amplify</li><li>Amazon API Gateway</li><li>AWS Device Farm</li><li>Amazon Pinpoint</li></ul><h3>Machine Learning:</h3><ul><li>Amazon Comprehend</li><li>Amazon Forecast</li><li>Amazon Fraud Detector</li><li>Amazon Kendra</li><li>Amazon Lex</li><li>Amazon Polly</li><li>Amazon Rekognition</li><li>Amazon SageMaker</li><li>Amazon Textract</li><li>Amazon Transcribe</li><li>Amazon Translate</li></ul><h3>Management and Governance:</h3><ul><li>AWS Auto Scaling</li><li>AWS CloudFormation</li><li>AWS CloudTrail</li><li>Amazon CloudWatch</li><li>AWS Command Line Interface (AWS CLI)</li><li>AWS Compute Optimizer</li><li>AWS Config</li><li>AWS Control Tower</li><li>AWS License Manager</li><li>Amazon Managed Grafana</li><li>Amazon Managed Service for Prometheus</li><li>AWS Management Console</li><li>AWS Organizations</li><li>AWS Personal Health Dashboard</li><li>AWS Proton</li><li>AWS Service Catalog</li><li>AWS Systems Manager</li><li>AWS Trusted Advisor</li><li>AWS Well-Architected Tool</li></ul><h3>Media Services:</h3><ul><li>Amazon Elastic Transcoder</li><li>Amazon Kinesis Video Streams</li></ul><h3>Migration and Transfer:</h3><ul><li>AWS Application Discovery Service</li><li>AWS Application Migration Service (CloudEndure Migration)</li><li>AWS Database Migration Service (AWS DMS)</li><li>AWS DataSync</li><li>AWS Migration Hub</li><li>AWS Server Migration Service (AWS SMS)</li><li>AWS Snow Family</li><li>AWS Transfer Family</li></ul><h3>Networking and Content Delivery:</h3><ul><li>Amazon CloudFront</li><li>AWS Direct Connect</li><li>Elastic Load Balancing (ELB)</li><li>AWS Global Accelerator</li><li>AWS PrivateLink</li><li>Amazon Route 53</li><li>AWS Transit Gateway</li><li>Amazon VPC</li><li>AWS Virtual Private Network (AWS VPN)</li></ul><h3>Security, Identity, and Compliance:</h3><ul><li>AWS Artifact</li><li>AWS Audit Manager</li><li>AWS Certificate Manager (ACM)</li><li>AWS CloudHSM</li><li>Amazon Cognito</li><li>Amazon Detective</li><li>AWS Directory Service</li><li>AWS Firewall Manager</li><li>Amazon GuardDuty</li><li>AWS Identity and Access Management (IAM)</li><li>Amazon Inspector</li><li>AWS Key Management Service (AWS KMS)</li><li>Amazon Macie</li><li>AWS Network Firewall</li><li>AWS Resource Access Manager (AWS RAM)</li><li>AWS Secrets Manager • AWS Security Hub</li><li>AWS Shield</li><li>AWS Single Sign-On</li><li>AWS WAF</li></ul><h3>Serverless:</h3><ul><li>AWS AppSync</li><li>AWS Fargate</li><li>AWS Lambda</li></ul><h3>Storage:</h3><ul><li>AWS Backup</li><li>Amazon Elastic Block Store (Amazon EBS)</li><li>Amazon Elastic File System (Amazon EFS)</li><li>Amazon FSx (for all types)</li><li>Amazon S3</li><li>Amazon S3 Glacier</li><li>AWS Storage Gateway</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a447b81a0563" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Amazon MQ]]></title>
            <link>https://medium.com/@psdurgadevi/amazon-mq-d186475ecde2?source=rss-fc52b35d91fb------2</link>
            <guid isPermaLink="false">https://medium.com/p/d186475ecde2</guid>
            <dc:creator><![CDATA[Durgadevi Subramanian]]></dc:creator>
            <pubDate>Tue, 20 Feb 2024 17:30:52 GMT</pubDate>
            <atom:updated>2024-02-20T17:30:52.203Z</atom:updated>
            <content:encoded><![CDATA[<p>Amazon MQ is a managed message broker service for <a href="http://activemq.apache.org/components/classic/">Apache ActiveMQ</a> and <a href="https://www.rabbitmq.com/">RabbitMQ</a> that makes it easy to set up and operate message brokers in the cloud. You get direct access to the ActiveMQ and RabbitMQ consoles and industry standard APIs and protocols for messaging, including JMS, NMS, AMQP 1.0 and 0.9.1, STOMP, MQTT, and WebSocket. You can easily move from any message broker that uses these standards to Amazon MQ because you don’t have to rewrite any messaging code in your applications.</p><p><strong>1.Message Broker Service:</strong> <br>Amazon MQ acts as a message broker, which is a critical component for decoupling and enabling communication between various parts of a distributed system. It allows different components, applications, or microservices to exchange messages in an asynchronous and loosely coupled manner.</p><p>2. <strong>Supported Technologies:<br></strong>Amazon MQ supports two popular message broker technologies:</p><ul><li><strong>ActiveMQ</strong>: Amazon MQ provides a managed version of Apache ActiveMQ, which is a widely used open-source message broker. ActiveMQ supports features like queues and topics and is based on the Java Message Service (JMS) standard.</li><li><strong>RabbitMQ:</strong> Amazon MQ also offers a managed RabbitMQ service, which is another well-known open-source message broker. RabbitMQ is known for its robust support of message queuing patterns and protocols, including Advanced Message Queuing Protocol (AMQP).</li></ul><p><strong>3. Queue and Topic Features:</strong></p><ul><li>Amazon MQ provides both queue and topic features, which are similar to the core concepts found in other messaging services like Amazon SQS and Amazon SNS:</li></ul><p><strong>Queues:<br></strong>Queues in Amazon MQ are similar to Amazon SQS. They allow you to send, store, and retrieve messages in a FIFO (First-In-First-Out) manner. This is useful for building systems where messages must be processed in a specific order, ensuring that no messages are lost, and enabling reliable point-to-point communication.</p><p><strong>Topics:<br></strong>Topics in Amazon MQ are similar to Amazon SNS. They support publish-subscribe messaging patterns, where a single message can be broadcast to multiple subscribers. This is ideal for building systems where multiple components or microservices need to receive and act upon the same message independently.</p><p><strong>4. Managed Service:<br></strong>Amazon MQ is fully managed by AWS, which means AWS takes care of the operational overhead, such as hardware provisioning, software patching, and scaling. This allows you to focus on developing your applications without worrying about managing the underlying infrastructure.</p><p>5.<strong> Integration with AWS Services:</strong> <br>Amazon MQ can be seamlessly integrated with other AWS services, enabling you to build complex and scalable architectures. For example, you can use Amazon MQ to enable communication between various components of your application and integrate it with AWS Lambda, EC2, or other AWS services.</p><p>Amazon MQ is well-suited for applications that require message queuing and publish-subscribe capabilities and are migrating to the cloud. It’s particularly useful when you have existing applications that are already using technologies like ActiveMQ or RabbitMQ, as it allows you to migrate to the cloud without significant code changes. It’s also suitable for microservices architectures where decoupling and scalability are essential.</p><p>Any application that runs on an AWS compute service, such as <a href="https://aws.amazon.com/ec2/">Amazon EC2</a>, <a href="https://aws.amazon.com/ecs/">Amazon ECS</a>, or <a href="https://aws.amazon.com/lambda/">AWS Lambda</a>, can use Amazon MQ. Amazon MQ is also integrated with the following AWS services:</p><ul><li><a href="https://aws.amazon.com/cloudwatch/">Amazon CloudWatch</a> — monitor metrics and generate alarms</li><li><a href="https://aws.amazon.com/cloudwatch/features/">Amazon CloudWatch Logs</a> — publish logs from your Amazon MQ brokers to Amazon CloudWatch Logs</li><li><a href="https://aws.amazon.com/cloudtrail/">AWS CloudTrail</a> — log, continously monitor, and retain Amazon MQ API calls</li><li><a href="https://aws.amazon.com/cloudformation/">AWS CloudFormation</a> — automate the process of creating, updating, and deleting message brokers</li><li><a href="https://aws.amazon.com/iam/">AWS Identity and Access Management (IAM)</a> — authentication and authorization of the service API</li><li><a href="https://aws.amazon.com/kms/">AWS Key Management Service (KMS)</a> — create and control the keys used to encrypt your data</li></ul><h3>Use cases</h3><p><strong>Low-latency event messaging<br></strong>Ensure low latency for thousands of events, so that applications have the most recent information possible.</p><p><strong>Migrate with flexible configurations <br></strong>Migrate from on premises to Amazon MQ with active/standby, a network of brokers, or cluster configurations.</p><p><strong>Invoke AWS Lambda functions<br></strong>Integrate applications and use Lambda functions to poll the Amazon MQ message broker.</p><p><strong>Legacy Application Migration:<br></strong>If you have an on-premises application that relies on message brokers like ActiveMQ or RabbitMQ and you want to migrate it to the cloud, Amazon MQ is an excellent choice. You can seamlessly move your existing message-driven applications to AWS without major code changes, benefiting from AWS’s managed service and scalability.</p><p><strong>Microservices Communication:<br></strong>In a microservices architecture, different services need to communicate with each other efficiently. Amazon MQ can facilitate asynchronous communication between microservices, allowing them to exchange messages in a decoupled and reliable manner. This helps maintain the independence of microservices while enabling them to work together as part of a larger application.</p><p><strong>Highly Reliable and Ordered Messaging: <br></strong>For applications that require highly reliable and ordered message delivery, Amazon MQ is a good fit. It provides features similar to traditional message brokers, ensuring that messages are delivered in the order they are sent and with minimal risk of data loss. This is crucial for applications with financial transactions, stock trading, or any process where the order of events is critical.</p><p><strong>When should I use Amazon MQ vs. Amazon SQS and SNS?</strong></p><p>Amazon MQ, <a href="https://aws.amazon.com/sqs/">Amazon SQS</a>, and <a href="https://aws.amazon.com/sns/">Amazon SNS</a> are messaging services that are suitable for anyone from startups to enterprises. If you’re using messaging with existing applications, and want to move your messaging to the cloud quickly and easily, we recommend you consider Amazon MQ. <br>It supports industry-standard APIs and protocols so you can switch from any standards-based message broker to Amazon MQ without rewriting the messaging code in your applications. <br>If you are building brand new applications in the cloud, we recommend you consider Amazon SQS and Amazon SNS. <br>Amazon SQS and SNS are lightweight, fully managed message queue and topic services that scale almost infinitely and provide simple, easy-to-use APIs. <br>You can use Amazon SQS and SNS to decouple and scale microservices, distributed systems, and serverless applications, and improve reliability.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d186475ecde2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Amazon AppFlow]]></title>
            <link>https://medium.com/@psdurgadevi/amazon-appflow-677515e1a89c?source=rss-fc52b35d91fb------2</link>
            <guid isPermaLink="false">https://medium.com/p/677515e1a89c</guid>
            <dc:creator><![CDATA[Durgadevi Subramanian]]></dc:creator>
            <pubDate>Tue, 20 Feb 2024 17:17:43 GMT</pubDate>
            <atom:updated>2024-02-20T17:17:43.718Z</atom:updated>
            <content:encoded><![CDATA[<h3>Amazon AppFlow</h3><p>Amazon AppFlow is a fully managed API integration service that you use to connect your software as a service (SaaS) applications to AWS services, and securely transfer data. Use Amazon AppFlow flows to manage and automate your data transfers without needing to write code.</p><p>Fully managed integration service to transfer data between services such as Salesforce, SAP, Google Analytics, and Amazon Redshift.</p><p>Transfer data at scale without the need to provision system resources.</p><p>Automate cataloging your data to discover and share across AWS analytics and machine learning services, such as SageMaker Data Wrangler.</p><p>Simplify and automate data preparation with transformations, partitioning, and aggregation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WKK0kfFfzKuI3kOD.png" /></figure><p><strong>What are the benefits of AppFlow?<br></strong>AppFlow relieves you from investing significant time and highly skilled developer staff to build and maintain custom API connectors for AWS services to exchange data with SaaS applications. SaaS application administrators and business analysts can quickly implement most of the integrations they need without waiting months for IT to finish integration projects. Specifically, the benefits include:</p><ul><li>Speed and agility: Amazon AppFlow enables you to integrate applications in a few minutes — no more waiting days or weeks to code custom connectors. Features like data pagination, error logging, and network connection retries are included by default so there’s no coding or management. With Amazon Appflow, data flow quality is built in, and you can enrich the flow of data through masking, mapping, merging, filtering, and validation as part of the flow itself.</li><li>Privacy and security: AppFlow encrypts data at rest and in motion. You can encrypt data with AWS managed keys or bring your own custom keys. It also allows users to restrict data from flowing over the public Internet using Amazon VPC endpoints enabled by AWS PrivateLink. This minimizes the threat from Internet based attacks and the risk of sensitive data leakage.</li><li>Scalability: AppFlow easily scales up without the need to plan or provision resources, so you can move large volumes of data without breaking it down into multiple batches. Using Amazon AppFlow, you can easily transfer millions of Salesforce records or Zendesk tickets — all while running a single flow.</li><li>Reliability: AppFlow uses a highly available architecture with redundant, isolated resources to prevent any single points of failure while running within the resilient AWS infrastructure.<br>Scalable</li></ul><h3>High-scale data transfer</h3><p>Amazon AppFlow can run up to 100 GB of data per flow, which helps you more easily transfer millions of Salesforce records, Marketo leads, or Zendesk tickets.</p><p><strong>Which AWS services are supported by Amazon AppFlow?</strong></p><p>Supported AWS services include Amazon S3, Amazon RedShift, Amazon Connector Customer Profiles, Amazon Lookout for Metrics, and Amazon Honeycode, and we’re continuing to add more all the time.</p><p><strong>What are some examples of Flows that I can configure using Amazon AppFlow</strong>?</p><p>AppFlow gives you the flexibility to configure their own Flows. Some examples of flows include:</p><ul><li>Create a copy of a Salesforce object (i.e. opportunity, case, campaign) in Amazon S3.</li><li>Send case tickets from Zendesk into an Amazon Redshift table.</li><li>Hydrate an Amazon S3 data lake with transactional data from SAP S/4HANA ERP.</li><li>Push records from a CSV file in Amazon S3 into a Salesforce account, contact, or lead object.</li><li>Transfer results such as lead scores and account churn risk scores from Amazon S3 to Salesforce.</li></ul><p><strong>What are the trigger mechanisms available for flows?</strong></p><p>You can run flows on demand, based on business events, or on a schedule:</p><ul><li>On Demand: Run data flows on demand, as soon as you click “Run Flow” to do bulk transfers or tests,</li><li>Event-based: Run data flows in response to business events like the creation of a sales opportunity, the status change of a support ticket, or the completion of a registration form.</li><li>Scheduled: Run data flows at a routine schedule at the time interval you choose to keep data in sync, or run flows routinely.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=677515e1a89c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>