<?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 Ibrahim Fundi on Medium]]></title>
        <description><![CDATA[Stories by Ibrahim Fundi on Medium]]></description>
        <link>https://medium.com/@ibrahimnjeru?source=rss-3cefd94bf383------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*bqWW_zewRDeahGHeWDpGEw.jpeg</url>
            <title>Stories by Ibrahim Fundi on Medium</title>
            <link>https://medium.com/@ibrahimnjeru?source=rss-3cefd94bf383------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:43:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ibrahimnjeru/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[Spring Boot 3 to 4 Migration Guide]]></title>
            <link>https://medium.com/@ibrahimnjeru/spring-boot-3-to-4-migration-guide-26ef4d839a24?source=rss-3cefd94bf383------2</link>
            <guid isPermaLink="false">https://medium.com/p/26ef4d839a24</guid>
            <category><![CDATA[gradle]]></category>
            <category><![CDATA[maven]]></category>
            <category><![CDATA[spring-boot-4]]></category>
            <category><![CDATA[java21]]></category>
            <category><![CDATA[spring-boot-3]]></category>
            <dc:creator><![CDATA[Ibrahim Fundi]]></dc:creator>
            <pubDate>Sun, 06 Sep 2026 13:44:49 GMT</pubDate>
            <atom:updated>2026-09-06T13:44:49.566Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VnVSrcHUUCQBoyEN1LIZDA.png" /></figure><p>Spring Boot 3.5.x reached the end of <strong>open-source support</strong> on June 30, 2026. This means teams that depend on public community releases should start planning their move to Spring Boot 4.</p><p>Spring Boot 4 moves the stack forward significantly. It is built on Spring Framework 7 and introduces a more modular dependency layout, including new or split boot starter artifacts for several technology areas. <a href="https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-4.0-Migration-Guide">The official migration guide</a> recommends upgrading first to the latest Spring Boot 3.5.x release, removing deprecations, then moving to version 4.</p><p>This new version requires at least Java 17 . In practice, Java 21 is a sensible production baseline for modern Spring Boot 4 services, especially if your organization already standardizes on Java 21 containers.</p><p>If you prefer an automated migration approach, you can also explore <a href="https://medium.com/@kanishks772/the-spring-boot-4-migration-hack-every-developer-needs-to-know-in-2025-7c8ae3529cff?sharedUserId=ibrahimnjeru">OpenRewrite-based migration recipes here</a>.</p><p>The biggest changes are:</p><pre>Spring Boot 3.5.x  -&gt; Spring Boot 4.x<br>Spring Framework 6 -&gt; Spring Framework 7<br>Spring Security 6  -&gt; Spring Security 7<br>Hibernate 6        -&gt; Hibernate 7<br>Jackson 2          -&gt; Jackson 3<br>Testcontainers 1.x -&gt; Testcontainers 2.x<br>Spring Cloud compatibility is from 2025.1.x release train</pre><p>This means moving to something like:</p><pre>plugins {<br>    id &#39;java&#39;<br>    id &#39;org.springframework.boot&#39; version &#39;4.1.1&#39;<br>    id &#39;io.spring.dependency-management&#39; version &#39;1.1.7&#39;<br>}<br><br>java {<br>    toolchain {<br>        languageVersion = JavaLanguageVersion.of(21)<br>    }<br>}<br><br>dependencyManagement {<br>    imports {<br>        mavenBom &#39;org.springframework.cloud:spring-cloud-dependencies:2025.1.3&#39;<br>    }<br>}<br></pre><p>Or for maven:</p><pre>&lt;parent&gt;<br>    &lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;<br>    &lt;artifactId&gt;spring-boot-starter-parent&lt;/artifactId&gt;<br>    &lt;version&gt;4.1.1&lt;/version&gt;<br>    &lt;relativePath/&gt;<br>&lt;/parent&gt;<br>&lt;properties&gt;<br>    &lt;java.version&gt;21&lt;/java.version&gt;<br>    &lt;spring-cloud.version&gt;2025.1.3&lt;/spring-cloud.version&gt;<br>&lt;/properties&gt;<br>&lt;dependencyManagement&gt;<br>    &lt;dependencies&gt;<br>        &lt;dependency&gt;<br>            &lt;groupId&gt;org.springframework.cloud&lt;/groupId&gt;<br>            &lt;artifactId&gt;spring-cloud-dependencies&lt;/artifactId&gt;<br>            &lt;version&gt;${spring-cloud.version}&lt;/version&gt;<br>            &lt;type&gt;pom&lt;/type&gt;<br>            &lt;scope&gt;import&lt;/scope&gt;<br>        &lt;/dependency&gt;<br>    &lt;/dependencies&gt;<br>&lt;/dependencyManagement&gt;</pre><p>Spring Boot manages a tested set of dependency versions. Unless you are fixing a specific CVE or resolving a proven compatibility issue, prefer Boot-managed versions.</p><p>For example, prefer:</p><pre>implementation(&#39;org.springframework.boot:spring-boot-starter-data-jpa&#39;)<br>runtimeOnly(&#39;org.postgresql:postgresql&#39;)</pre><p>instead of:</p><pre>implementation(&#39;org.springframework.data:spring-data-jpa&#39;)<br>implementation(&#39;org.hibernate.orm:hibernate-core:6.6.X&#39;)<br>runtimeOnly(&#39;org.postgresql:postgresql:42.X&#39;)</pre><h3>Use the properties migrator, then remove it</h3><p>Spring Boot 4 renames and removes configuration properties. Do not try to find all of them manually.</p><p>Add the migrator temporarily:</p><pre>runtimeOnly(&quot;org.springframework.boot:spring-boot-properties-migrator&quot;)</pre><p>For maven:</p><pre>&lt;dependency&gt;<br>    &lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;<br>    &lt;artifactId&gt;spring-boot-properties-migrator&lt;/artifactId&gt;<br>    &lt;scope&gt;runtime&lt;/scope&gt;<br>&lt;/dependency&gt;</pre><p>Run the app and fix every property warnings:</p><pre>./gradlew bootRun --args=&#39;--spring.profiles.active=local&#39;</pre><p>For maven:</p><pre>./mvnw spring-boot:run -Dspring-boot.run.profiles=local</pre><p>Then remove the migrator. Spring Boot’s migration guide explicitly advises to remove it once migration is complete.</p><h3>Spring Boot 4 is more modular</h3><p>Spring Boot 4 split several areas into smaller, more focused modules and starters. The official migration guide explains that Boot modules now follow a more consistent naming model: spring-boot-&lt;technology&gt;, with starters named spring-boot-starter-&lt;technology&gt;. Test modules follow the same idea with spring-boot-&lt;technology&gt;-test and spring-boot-starter-&lt;technology&gt;-test.</p><p>That means some things that previously worked through broad transitive dependencies now require explicit starters.</p><p>For example:</p><pre>testImplementation(&#39;org.springframework.boot:spring-boot-starter-webflux-test&#39;)<br>testImplementation(&#39;org.springframework.boot:spring-boot-starter-security-test&#39;)<br>testImplementation(&#39;org.springframework.boot:spring-boot-starter-data-jpa-test&#39;)<br>testImplementation(&#39;org.springframework.boot:spring-boot-starter-amqp-test&#39;)</pre><p>Do not blindly keep only:</p><pre>testImplementation(&#39;org.springframework.boot:spring-boot-starter-test&#39;)</pre><p>If your tests depend on security, WebFlux, JPA, AMQP, GraphQL, REST clients, or other specific Boot test infrastructure, use the matching test starter.</p><h3>Jackson 3 is the biggest breaking change</h3><p>Spring Boot 4 uses Jackson 3 by default. Spring’s Jackson 3 support notes explain that Boot 4 and Spring Framework 7 are designed around Jackson 3, while spring-boot-jackson2 exists only as a temporary compatibility bridge.</p><p>The main package change is:</p><pre>com.fasterxml.jackson.* -&gt; tools.jackson.*</pre><p>But there is one important exception. The annotation below stay under com.fasterxml.jackson.annotation</p><pre>import com.fasterxml.jackson.annotation.JsonProperty;<br>import com.fasterxml.jackson.annotation.JsonIgnore;<br>import com.fasterxml.jackson.annotation.JsonInclude;<br>import com.fasterxml.jackson.annotation.JsonFormat;</pre><h3>Common Jackson 3 replacements</h3><pre>| Jackson 2                                                 | Jackson 3                                         |<br>| --------------------------------------------------------- | ------------------------------------------------- |<br>| com.fasterxml.jackson.databind.ObjectMapper               | tools.jackson.databind.ObjectMapper               |<br>| com.fasterxml.jackson.databind.json.JsonMapper            | tools.jackson.databind.json.JsonMapper            |<br>| com.fasterxml.jackson.core.type.TypeReference             | tools.jackson.core.type.TypeReference             |<br>| JsonProcessingException                                   | JacksonException                                  |<br>| JsonMappingException                                      | DatabindException                                 |<br>| JsonDeserializer&lt;T&gt;                                       | ValueDeserializer&lt;T&gt;                              |<br>| JsonSerializer&lt;T&gt;                                         | ValueSerializer&lt;T&gt;                                |<br>| com.fasterxml.jackson.databind.annotation.JsonDeserialize | tools.jackson.databind.annotation.JsonDeserialize |<br>| com.fasterxml.jackson.databind.annotation.JsonSerialize   | tools.jackson.databind.annotation.JsonSerialize   |</pre><h3>ObjectMapper is now builder-first</h3><p>In Jackson 3, configure using JsonMapper.builder():</p><pre>return JsonMapper.builder()<br>        .configure(DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES, false)<br>        .build();</pre><p>Instead of :</p><pre>return new ObjectMapper()<br>        .configure(DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES, false);</pre><h3>JavaTimeModule is gone</h3><p>Remove this:</p><pre>.registerModule(new JavaTimeModule())</pre><p>Jackson 3 includes the former Java 8 date/time modules directly, so JavaTimeModule is no longer required. The migration guide also notes the embedding/removal of former Java 8 modules.</p><h3>Some XML/JSON mappers feature names moved</h3><p>Old:</p><pre>.configure(JsonGenerator.Feature.WRITE_BIGDECIMAL_AS_PLAIN, true)<br>.configure(SerializationFeature.WRITE_DATES_AS_TIMESTAMPS, false)<br>.enable(FromXmlParser.Feature.EMPTY_ELEMENT_AS_NULL)</pre><p>New:</p><pre>.configure(StreamWriteFeature.WRITE_BIGDECIMAL_AS_PLAIN, true)<br>.configure(DateTimeFeature.WRITE_DATES_AS_TIMESTAMPS, false)<br>.enable(XmlReadFeature.EMPTY_ELEMENT_AS_NULL)</pre><h3>XML with Jackson 3</h3><p>For XML-heavy integrations, use the Jackson 3 XML classes:</p><pre>import tools.jackson.core.StreamWriteFeature;<br>import tools.jackson.databind.DeserializationFeature;<br>import tools.jackson.databind.SerializationFeature;<br>import tools.jackson.dataformat.xml.XmlMapper;<br>import tools.jackson.dataformat.xml.XmlReadFeature;<br>import tools.jackson.module.jakarta.xmlbind.JakartaXmlBindAnnotationModule;</pre><p>Example mapper:</p><pre>private final XmlMapper mapper = XmlMapper.xmlBuilder()<br>        .configure(DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES, false)<br>        .configure(StreamWriteFeature.WRITE_BIGDECIMAL_AS_PLAIN, true)<br>        .configure(SerializationFeature.FAIL_ON_EMPTY_BEANS, false)<br>        .enable(XmlReadFeature.EMPTY_ELEMENT_AS_NULL)<br>        .addModule(new JakartaXmlBindAnnotationModule())<br>        .defaultUseWrapper(false)<br>        .build();</pre><p>Use JakartaXmlBindAnnotationModule when your DTOs use jakarta.xml.bind.annotation.*.</p><h3>Custom deserializers changed</h3><p>Old:</p><pre>public class MyDeserializer extends JsonDeserializer&lt;MyDto&gt; {<br>    @Override<br>    public MyDto deserialize(JsonParser p, DeserializationContext ctxt) throws IOException {<br>        JsonNode node = p.getCodec().readTree(p);<br>        ...<br>    }<br>}</pre><p>New:</p><pre>public class MyDeserializer extends ValueDeserializer&lt;MyDto&gt; {<br>    @Override<br>    public MyDto deserialize(JsonParser p, DeserializationContext ctxt) throws JacksonException {<br>        JsonNode node = ctxt.readTree(p);<br>        ...<br>    }<br>}</pre><p>Some important changes:</p><pre>JsonDeserializer -&gt; ValueDeserializer<br>IOException -&gt; JacksonException<br>p.getCodec().readTree(p) -&gt; ctxt.readTree(p)<br>treeToValue(...) -&gt; ctxt.readTreeAsValue(...)</pre><h3>JSpecify replaces Spring nullability annotations</h3><p>Spring Framework 7 uses JSpecify annotations for null-safe APIs. The Spring Framework docs recommend libraries in the Spring ecosystem do the same.</p><p>Old imports:</p><pre>import org.springframework.lang.Nullable;<br>import org.springframework.lang.NonNull;</pre><p>New imports:</p><pre>import org.jspecify.annotations.Nullable;<br>import org.jspecify.annotations.NonNull;</pre><p>For package-level defaults, use:</p><pre>import org.jspecify.annotations.NullMarked;</pre><pre>@NullMarked<br>package com.example.customer;</pre><p>The JSpecify docs describe @NullMarked as the annotation used to mark most API types in a scope as non-null by default.</p><h3>Spring Security 7: make your security configuration explicit</h3><p>If you still have old Spring Security configuration, expect trouble.</p><p>Search for:</p><pre>rg -n &quot;WebSecurityConfigurerAdapter|authorizeRequests|antMatchers|MvcRequestMatcher|AntPathRequestMatcher|\.and\(\)&quot; src/main/java</pre><p>Modern Spring Security configuration should be explicit and lambda-based:</p><pre>@Bean<br>SecurityFilterChain securityFilterChain(HttpSecurity http) throws Exception {<br>    return http<br>            .csrf(csrf -&gt; csrf.disable())<br>            .authorizeHttpRequests(auth -&gt; auth<br>                    .requestMatchers(&quot;/actuator/health/**&quot;).permitAll()<br>                    .anyRequest().authenticated()<br>            )<br>            .oauth2ResourceServer(oauth2 -&gt; oauth2.jwt(Customizer.withDefaults()))<br>            .build();<br>}</pre><p>Spring Security 7 removed several deprecated APIs, and its migration docs call out changes around matchers and the Java DSL.</p><p>For stateless REST APIs using bearer tokens, decide deliberately whether CSRF should be disabled. For browser/session applications, configure CSRF properly instead of disabling it blindly.</p><h3>Undertow support is gone</h3><p>If your application uses:</p><pre>implementation(&#39;org.springframework.boot:spring-boot-starter-undertow&#39;)</pre><p>you need to migrate away from it.</p><p>Spring Boot 4 requires a Servlet 6.1 baseline, and Undertow support was dropped because Undertow was not compatible with that baseline at the time of Boot 4.0. The Undertow starter and embedded Undertow support are removed.</p><p>Move to Tomcat or Jetty:</p><pre>implementation(&#39;org.springframework.boot:spring-boot-starter-web&#39;)</pre><p>Tomcat is the default. If you need Jetty:</p><pre>implementation(&#39;org.springframework.boot:spring-boot-starter-jetty&#39;)</pre><h3>Testcontainers artifact names changed</h3><p>If you were using old Testcontainers , this fails:</p><pre>testImplementation(&#39;org.testcontainers:junit-jupiter&#39;)<br>testImplementation(&#39;org.testcontainers:postgresql&#39;)<br>testImplementation(&#39;org.testcontainers:rabbitmq&#39;)</pre><p>Use the new artifact names:</p><pre>testImplementation(&#39;org.springframework.boot:spring-boot-testcontainers&#39;)<br>testImplementation(&#39;org.testcontainers:testcontainers-junit-jupiter&#39;)<br>testImplementation(&#39;org.testcontainers:testcontainers-postgresql&#39;)<br>testImplementation(&#39;org.testcontainers:testcontainers-rabbitmq&#39;)</pre><p>Use spring-boot-testcontainers when you want Spring Boot integration such as service connections.</p><h3>@MockBean and @SpyBean are removed</h3><p>Spring Boot 4 removed Boot’s @MockBean and @SpyBean support in favor of Spring Framework’s @MockitoBean and @MockitoSpyBean. The Boot migration guide calls out the direct replacement and notes that the new annotations can be used on fields in test classes, but not in @Configuration classes.</p><p>Old:</p><pre>@MockBean<br>private PaymentClient paymentClient;</pre><p>New:</p><pre>@MockitoBean<br>private PaymentClient paymentClient;</pre><p>Search:</p><pre>rg -n &quot;@MockBean|@SpyBean&quot; src/test/java</pre><h3>@SpringBootTest no longer gives you everything automatically</h3><p>Spring Boot 4 also changes some test support assumptions. For example, the migration guide notes that @SpringBootTest no longer automatically provides WebClient or TestRestTemplate beans. If you need TestRestTemplate, add @AutoConfigureTestRestTemplate; for the newer client testing model, use RestTestClient with the relevant dependencies and auto-configuration. This is part of the broader theme: Boot 4 is more explicit and modular.</p><h3>OpenFeign and Jackson 3</h3><p>If you use manual OpenFeign builders, Jackson 3 may break your client setup.</p><p>Old code:</p><pre>import feign.jackson.JacksonEncoder;</pre><pre>Feign.builder()<br>        .encoder(new FormEncoder(new JacksonEncoder()))<br>        .target(TokenClient.class, baseUrl);</pre><p>For Jackson 3:</p><pre>import feign.jackson3.Jackson3Encoder;</pre><pre>Feign.builder()<br>        .encoder(new FormEncoder(new Jackson3Encoder()))<br>        .target(TokenClient.class, baseUrl);</pre><p>As always, test your services thoroughly before going to production. Spring Boot 4 is a major breaking upgrade, so expect a few surprises beyond the compile errors.</p><p>Thanks for reading, and see you in the next upgrade.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26ef4d839a24" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Placeniko helps you smash and leverage Nairobi traffic]]></title>
            <link>https://medium.com/@ibrahimnjeru/smash-nairobi-traffic-report-shame-rogue-motorists-like-a-savage-f0ad92955125?source=rss-3cefd94bf383------2</link>
            <guid isPermaLink="false">https://medium.com/p/f0ad92955125</guid>
            <category><![CDATA[nairobians]]></category>
            <category><![CDATA[nairobi-traffic]]></category>
            <category><![CDATA[placeniko]]></category>
            <category><![CDATA[nairobi]]></category>
            <dc:creator><![CDATA[Ibrahim Fundi]]></dc:creator>
            <pubDate>Wed, 27 Jun 2018 15:32:11 GMT</pubDate>
            <atom:updated>2018-07-01T08:59:37.558Z</atom:updated>
            <content:encoded><![CDATA[<p>Everyone who commutes, walks or drives within the city knows that Nairobi has a rising demand for road usage, a limited infrastructure, semi-public transport and a lack of reliable information on traffic conditions and on top of this, the peculiar Kenyan habit of always being in a hurry even when it doesn’t matter. Cumulate all these factors in the evening rush hour and a commute that would normally take 30 minutes takes almost 3 hours.</p><p>The city is legendary for traffic jams so heavy, Siyanda Mohutsiwa, the famed speaker from Botswana,once said it will ‘humble you’. But not any more. <a href="https://placeniko.com/">Placeniko</a> is here to help you. Its app is available <a href="https://play.google.com/store/apps/details?id=com.placeniko.android"><strong>here</strong></a><strong>.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*Q869HAWQr7pBoEM0Ftsnrw.png" /></figure><p>Placeniko comes in to help you avoid traffic jam, report rogue matatu crew to their sac-cos, report accidents directly to the DMs of police and Red cross , find your lost car and luggage in matatus, shame rogue road users and create awareness on hit and run drivers, find speed guns and leverage traffic if ever stuck.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*SZLRos9N_zqwj7Hn42v4-g.png" /></figure><p>PlaceNiko services the Nairobi county in a way that embodies the Kenyan spirit of always finding a way to make our lives easier. ‘Entreprenuering our way around our lives’ as Ory Okolloh calls it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f0ad92955125" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>