<?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 Adeleye Adedolapo on Medium]]></title>
        <description><![CDATA[Stories by Adeleye Adedolapo on Medium]]></description>
        <link>https://medium.com/@adeleyeadedolapomayowa?source=rss-aceeef33b408------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*TSLT7fXcV9LDAZRN.</url>
            <title>Stories by Adeleye Adedolapo on Medium</title>
            <link>https://medium.com/@adeleyeadedolapomayowa?source=rss-aceeef33b408------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 00:40:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adeleyeadedolapomayowa/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[CAP Theorem and the Real Tradeoffs Behind Picking a Database]]></title>
            <link>https://medium.com/@adeleyeadedolapomayowa/cap-theorem-and-the-real-tradeoffs-behind-picking-a-database-ab19f009e528?source=rss-aceeef33b408------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab19f009e528</guid>
            <category><![CDATA[distributed-systems]]></category>
            <category><![CDATA[system-design-concepts]]></category>
            <dc:creator><![CDATA[Adeleye Adedolapo]]></dc:creator>
            <pubDate>Wed, 08 Jul 2026 23:49:25 GMT</pubDate>
            <atom:updated>2026-07-08T23:49:25.048Z</atom:updated>
            <content:encoded><![CDATA[<p>Every distributed systems engineer eventually runs into the same wall: a database that behaved perfectly in staging starts misbehaving the moment it is spread across multiple nodes, datacenters, or regions. Usually, the root cause traces back to a tradeoff nobody explicitly made, because nobody sat down and asked what the system should do when the network itself becomes unreliable.</p><p>That’s what the CAP theorem is really about. Not database marketing buzzwords, not a checklist, but a hard limit on what’s simultaneously achievable in a distributed system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eM49j_3M7G0VO0znNnZ79w.png" /></figure><h4>What CAP Actually Says</h4><p>Formulated by Eric Brewer in 2000 and later formally proven by Seth Gilbert and Nancy Lynch, the CAP theorem states that a distributed data system can only guarantee two of the following three properties at any given moment:</p><ul><li><strong>Consistency: </strong>every read receives the most recent write or an error. All nodes see the same data at the same time.</li><li><strong>Availability: </strong>every request receives a (non-error) response, without the guarantee that it contains the most recent write.</li><li><strong>Partition Tolerance: </strong>the system continues to operate despite an arbitrary number of messages being dropped or delayed between nodes.</li></ul><p>The nuance that gets lost in most summaries: <strong>partition tolerance isn’t really a choice</strong>. Networks fail. Packets get dropped. Nodes in different availability zones lose contact with each other. In any real distributed system, partitions <em>will</em> happen; it’s a matter of when, not if. So the actual decision you’re making isn’t “which two of three do I want,” it’s:</p><blockquote><strong>When a network partition occurs, do I sacrifice consistency or availability?</strong></blockquote><p>This reframes CAP from three options down to two real-world choices: <strong>CP</strong> or <strong>AP</strong>.</p><p><strong>CP Systems: Consistency Over Availability</strong></p><p>A CP system, when it detects a partition, will refuse to respond (or will return an error) rather than risk serving stale or conflicting data. It prioritises correctness over uptime.</p><p><strong>Characteristics:</strong></p><ul><li>Reads and writes may be rejected during a partition to avoid a divergent state.</li><li>Strong consistency guarantees, often linearizability or at least strict serializability within a quorum.</li><li>Typically built around consensus protocols like Raft or Paxos.</li></ul><p><strong>Examples:</strong> HBase, MongoDB (with majority write/read concerns), etcd, ZooKeeper, and traditional single-leader relational databases when configured for synchronous replication.</p><p><strong>Where this fits:</strong> Any place where an incorrect answer is worse than no answer. Financial ledgers, inventory counts, distributed locks, configuration stores, and anything relevant to payment infrastructure that touches money movement. If a NIP (NIBSS Instant Payment) debit-credit pair can’t guarantee consistency across a partition, you risk double-debits or phantom credits, which are far more expensive to reconcile than a temporarily unavailable endpoint.</p><h3>AP Systems: Availability Over Consistency</h3><p>An AP system keeps responding even during a partition, accepting that different nodes might temporarily disagree. It guarantees the system stays “up” and resolves conflicts later through different reconciliation strategies (last-write-wins, vector clocks, CRDTs, application-level merge logic).</p><p><strong>Characteristics:</strong></p><ul><li>Writes succeed even if a node can’t currently reach its peers.</li><li>Reads may return stale data.</li><li>Requires an explicit strategy for eventual consistency and conflict resolution.</li></ul><p><strong>Examples:</strong> Cassandra, DynamoDB (in its default configuration), Couchbase, Riak.</p><p><strong>Where this fits:</strong> Systems where availability under load matters more than perfect real-time accuracy, and where staleness is tolerable or resolvable. Shopping cart contents, social media feeds, product catalogues, session stores, and analytics pipelines are classic cases. A user seeing their cart from 200ms ago is a non-event; a bank seeing a stale balance during a transfer is not.</p><h3>The Piece CAP Doesn’t Cover: PACELC</h3><p>CAP only describes system behaviour <em>during a partition</em>. But partitions are rare relative to normal operation — most of the time, your system is running fine, and you still have a tradeoff to make: <strong>latency vs. consistency</strong>, even with no partition in sight.</p><p>This is where <strong>PACELC</strong> (proposed by Daniel Abadi) extends the conversation:</p><blockquote><strong>If Partitioned: choose Availability or Consistency; Else (normal operation): choose Latency or Consistency.</strong></blockquote><p>This matters more in practice than CAP alone, because it forces you to confront a tradeoff you face with every single request, not just during rare outage windows. A system replicating synchronously across regions for strong consistency pays a latency tax on every write — even when nothing is broken. A system that replicates asynchronously gets low latency, but has a consistency window where replicas can diverge.</p><h3>A Practical Decision Framework</h3><p>When picking a database, the CAP/PACELC lens is useful, but it needs to be translated into engineering questions you can actually answer:</p><ol><li><strong>What does a “wrong” read cost, versus a “no” response?</strong> If serving stale data leads to a financial or safety-critical error, <strong>lean CP</strong>. If it leads to a minor UX inconsistency that self-corrects, <strong>lean AP</strong>.</li><li><strong>What’s your actual partition frequency and blast radius?</strong> Multi-region, cross-cloud, or WAN-linked deployments face partitions far more often than a single-AZ cluster. If you’re single-region with redundant networking, the CAP tradeoff is less urgent than your PACELC latency tradeoff.</li><li><strong>Can conflicts be resolved after the fact, and by whom?</strong> AP systems push conflict resolution downstream; either to the database or to your application layer. If your domain doesn’t have a natural merge strategy (money doesn’t “merge” cleanly), CP is usually safer.</li></ol><p><strong>4. What are your read/write ratios and access patterns?</strong> Consistency guarantees get expensive under write-heavy, multi-region workloads. If most of your load is reads that can tolerate slight staleness, AP with read-repair or bounded staleness may outperform CP without necessarily hurting correctness</p><p><strong>5. Do you need this decision to be uniform across the whole system, or can it vary by data type?</strong> Most real systems aren’t monolithically CP or AP; they’re heterogeneous. Ledger and transaction state might sit in a CP store (or a strongly consistent RDBMS with synchronous replication), while session data, caching layers (Redis), and audit/event logs live in AP-leaning stores optimized for throughput.</p><p>The point isn’t that one database “wins.” It’s that the tradeoff should be made <em>deliberately, per data type</em>, rather than inherited by default from whatever database the team already knew how to operate.</p><h3>Closing Thought</h3><p>CAP theorem isn’t a limitation to work around; it’s a forcing function for an honest conversation your team should be having anyway: <em>what happens when things go wrong, and which failure mode can we actually tolerate?</em> Framed that way, database selection stops being a technology preference and becomes a direct expression of your system’s risk tolerance.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab19f009e528" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Encoding, Encryption, and Hashing: What’s the Difference and When to Use Each]]></title>
            <link>https://medium.com/@adeleyeadedolapomayowa/encoding-encryption-and-hashing-whats-the-difference-and-when-to-use-each-cf6b6a079481?source=rss-aceeef33b408------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf6b6a079481</guid>
            <category><![CDATA[hashing]]></category>
            <category><![CDATA[pci-dss]]></category>
            <category><![CDATA[encoding]]></category>
            <category><![CDATA[encryption]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Adeleye Adedolapo]]></dc:creator>
            <pubDate>Wed, 08 Jul 2026 06:50:59 GMT</pubDate>
            <atom:updated>2026-07-08T10:39:07.004Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’ve spent any time in backend engineering, you’ve probably seen these three terms used loosely, sometimes even interchangeably, in code reviews, documentation, or Slack threads. “Just encrypt the password” (please don’t). “Encode the token before sending it” (fine, but that’s not security). “Hash the payload for the signature” (now we’re talking).</p><p>They solve fundamentally different problems. Mixing them up isn’t just a semantic slip; it can lead to real security vulnerabilities, broken integrations, or systems that quietly do the wrong thing. This article breaks down what each one actually does, how they differ, and where each belongs in a real system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dMPb9Q9LXUJWwyvQLkUOjw.jpeg" /></figure><h3>The One-Sentence Version</h3><ul><li><strong>Encoding</strong> transforms data into a different format for compatibility; it’s reversible by design and requires no secret.</li><li><strong>Encryption</strong> transforms data to keep it confidential; it’s reversible, but only with the correct key.</li><li><strong>Hashing</strong> transforms data into a fixed-size fingerprint; it’s a one-way function and is not meant to be reversed at all.</li></ul><p>If you remember nothing else, remember this: encoding is about <strong>format</strong>, encryption is about <strong>secrecy</strong>, and hashing is about <strong>integrity/verification</strong>.</p><h3>Encoding</h3><h4>What it does</h4><p>Encoding converts data from one representation to another so it can be safely transmitted, stored, or processed by systems that expect a particular format. It doesn’t hide anything and doesn’t require a key; anyone with the encoding scheme (which is always public) can reverse it instantly.</p><h4>Common schemes</h4><ul><li><strong>Base64</strong> turns binary data into ASCII text, commonly used to embed binary content (images, files, tokens) inside JSON, XML, or URLs.</li><li><strong>URL encoding (percent-encoding) </strong>escapes characters that aren’t safe in URLs (spaces, &amp;, =, etc.).</li><li><strong>UTF-8 / UTF-16</strong> — character encodings that map text into bytes.</li><li><strong>Hex encoding</strong> represents bytes as readable hexadecimal characters, often used for hashes or binary keys in logs.</li></ul><h4>Where it’s applicable</h4><ul><li>Embedding binary data (images, files, protobuf payloads) in text-based formats like JSON.</li><li>Encoding a JWT header and payload (note: the <em>signature</em> on a JWT is what protects it; the header/payload are just Base64URL-encoded and fully readable by anyone).</li><li>Making data safe to include in URLs, headers, or email bodies.</li><li>Serializing data between systems with different native character sets.</li></ul><h4>What it’s <em>not</em> for:</h4><p>Encoding is not a security control. If you Base64-encode a password or an API key and store that in a database, you have not protected anything — decoding it is trivial and requires no secret at all. This is a surprisingly common mistake in systems that need to satisfy an “at rest” compliance checkbox without doing the actual work.</p><h3>Encryption</h3><h4>What it does</h4><p>Encryption transforms plaintext into ciphertext using an algorithm and a key, such that the original data can only be recovered by someone holding the correct key. It exists specifically to protect confidentiality by keeping data unreadable to anyone who doesn’t have authorization.</p><p><strong>Two main families</strong></p><ul><li><strong>Symmetric encryption</strong> (e.g., AES-256) uses the same key to encrypt and decrypt. Fast, suited for large volumes of data, but requires securely distributing and rotating the shared key.</li><li><strong>Asymmetric encryption</strong> (e.g., RSA, ECC) — a public key encrypts; a private key decrypts. It is slower but solves the key-distribution problem; it is useful for things like TLS handshakes, signing, and key exchange.</li></ul><p>In practice, most real-world systems use both together: asymmetric encryption to securely exchange a symmetric session key, then symmetric encryption for the actual data (this is exactly how TLS works).</p><h4>Where it’s applicable</h4><ul><li>Data in transit: TLS/SSL for API calls, gRPC channels, database connections.</li><li>Data at rest: encrypting sensitive fields in a database (PANs, BVNs, NIN details, account numbers) or encrypting entire disks/volumes (EBS encryption on AWS, for example).</li><li>Application-level encryption of sensitive payloads before they reach a message queue such as Kafka, especially in multi-tenant or cross-border data flows.</li><li>Secrets management: encrypting credentials, private keys, and config secrets (AWS KMS, HashiCorp Vault).</li><li>End-to-end encrypted messaging, where even the service provider can’t read the content.</li></ul><h4>Key considerations</h4><ul><li>Encryption is only as strong as key management. A well-encrypted database with a hardcoded key sitting in the same repo is barely better than plaintext.</li><li>Encryption always implies <strong>someone, somewhere, can decrypt it; </strong>if you don’t want <em>anyone</em> ever to recover the original value, encryption is the wrong tool. That’s what hashing is for.</li></ul><h3>Hashing</h3><h4>What it does</h4><p>Hashing takes an input of any size and produces a fixed-length output (a “digest”) using a one-way function. A good cryptographic hash function has three critical properties:</p><ol><li><strong>Deterministic: </strong>the same input always produces the same output.</li><li><strong>Pre-image resistant: </strong>you can’t feasibly reverse a hash back to the original input.</li><li><strong>Collision resistant: </strong>it’s computationally impossible to find inputs that produce the same hash.</li></ol><p>Unlike encryption, there’s no key and no way back. If you need the original value back, hashing is the wrong tool by definition.</p><h4>Common algorithms</h4><ul><li><strong>SHA-256 / SHA-3:</strong> A general-purpose cryptographic hash function, widely used for integrity checks, digital signatures, and blockchain.</li><li><strong>bcrypt / scrypt / Argon2</strong> — purpose-built for password hashing. These are intentionally slow and include built-in salting, which resists brute-force and rainbow-table attacks. This is the category that password storage should always use, never plain SHA-256, which is fast enough to brute-force at scale.</li><li><strong>MD5 / SHA-1</strong> — largely deprecated for security reasons due to known collision vulnerabilities, though it is still seen in some legacy checksums.</li></ul><h3>Where it’s applicable</h3><ul><li><strong>Password storage: </strong>never store plaintext or even encrypted passwords; store a salted hash (bcrypt/Argon2) so that even a database breach doesn’t expose usable credentials.</li><li><strong>Data integrity verification: </strong>checksums for file downloads; verifying that a message wasn’t tampered with in transit (this is exactly what HMAC signatures on webhooks do).</li><li><strong>Digital signatures: </strong>you hash the data, then encrypt the hash with a private key; the recipient re-hashes and compares.</li><li><strong>Deduplication and indexing: </strong>hashing large objects to quickly compare or index them without storing the full content.</li></ul><h4>Common Mistakes Worth Calling Out</h4><ul><li><strong>“Encoding as security.”</strong> Base64 is not encryption. If someone asks you to “encode the password before saving it,” push back; that’s providing an illusion of protection with none of the substance.</li><li><strong>Hashing passwords with fast, general-purpose hashes.</strong> SHA-256 is great for file integrity but terrible for passwords because GPUs can compute billions of SHA-256 hashes per second. Password hashing algorithms are deliberately slow and memory-hard.</li><li><strong>Encrypt when you should hash;</strong> If you never need the original value back (passwords, API key verification), hashing is both simpler and more secure than encryption, since there’s no key to protect or leak.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf6b6a079481" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enhancing Spring Boot Applications: Application and Database Optimisation Strategies]]></title>
            <link>https://medium.com/@adeleyeadedolapomayowa/enhancing-spring-boot-applications-application-and-database-optimisation-strategies-0819c4eadec4?source=rss-aceeef33b408------2</link>
            <guid isPermaLink="false">https://medium.com/p/0819c4eadec4</guid>
            <category><![CDATA[application-performance]]></category>
            <category><![CDATA[redis]]></category>
            <category><![CDATA[spring-boot]]></category>
            <category><![CDATA[java]]></category>
            <dc:creator><![CDATA[Adeleye Adedolapo]]></dc:creator>
            <pubDate>Thu, 02 Jul 2026 03:09:15 GMT</pubDate>
            <atom:updated>2026-07-02T03:20:48.269Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/959/1*FhpnyHS2oSfqijAz0jR4Lg.jpeg" /></figure><h3><strong>Introduction</strong></h3><p>Spring Boot has become the default choice for building production-grade Java applications, thanks to its convention-over-configuration philosophy and rich ecosystem. But shipping a working application is only the first milestone, as traffic grows and data volumes increase, teams quickly discover that “it works” and “it works well under load” are very different things.</p><p>This article walks through practical strategies for enhancing a Spring Boot application on two fronts: the <strong>application layer</strong> (how the app processes requests, manages resources, and scales) and the <strong>database layer</strong> (how data is stored, queried, and accessed efficiently). Together, these form the backbone of a system that stays fast and reliable as it grows.</p><h3>Part 1: Application-Layer Enhancements</h3><h3>1. Externalise and Profile Your Configuration</h3><p>Use Spring profiles (<em>application-dev.yml, application-prod.yml</em>) to separate environment-specific settings. This avoids hardcoding values and makes it easy to tune thread pools, timeouts, and logging levels per environment without touching code.</p><pre>spring:<br>  profiles:<br>    active: prod<br>server:<br>  tomcat:<br>    threads:<br>      max: 200<br>      min-spare: 20</pre><h3><strong>2. Enable Caching</strong></h3><p>Repeated calls to expensive services or database queries are a common source of latency. Spring’s caching abstraction (<em>@Cacheable, @CacheEvict, @CachePut</em>) lets you add caching with minimal code changes.</p><pre>@Cacheable(value = &quot;products&quot;, key = &quot;#id&quot;)<br>public Product getProductById(Long id) {<br>    return productRepository.findById(id)<br>        .orElseThrow(() -&gt; new ProductNotFoundException(id));<br>}</pre><p>For production, back this with a distributed cache like <strong>Redis</strong> rather than the default in-memory <strong>ConcurrentHashMap</strong>, so cached data survives restarts and is shared across instances.</p><h3>3. Use Asynchronous Processing</h3><p>Not every operation needs to block the request thread. Use @Async for fire-and-forget tasks (sending emails, writing audit logs, triggering notifications) and configure a dedicated thread pool so async work doesn&#39;t starve your main request-handling threads.</p><pre>@Async(&quot;taskExecutor&quot;)<br>public void sendWelcomeEmail(User user) {<br>    emailService.send(user.getEmail(), &quot;Welcome!&quot;);<br>}</pre><p>For heavier workloads, consider message queues (Kafka, RabbitMQ) to decouple producers from consumers entirely.</p><h3>4. Tune the Embedded Server and Thread Pools</h3><p>Default Tomcat settings are conservative. Adjust thread pool size, connection timeouts, and max connections based on load testing rather than guesswork. Pair this with proper <strong>JVM tuning</strong> (heap size, garbage collector choice <em>G1GC</em> is a solid default for most Spring Boot workloads).</p><h3>5. Add Observability</h3><p>You can’t optimise what you can’t measure. Spring Boot Actuator, combined with Micrometer and a metrics backend (Prometheus/Grafana), gives visibility into request latency, error rates, thread pool saturation, and JVM memory.</p><pre>management:<br>  endpoints:<br>    web:<br>      exposure:<br>        include: health, metrics, prometheus</pre><p>Add distributed tracing (Micrometer Tracing with Zipkin or OpenTelemetry) once you move to microservices, so you can follow a request across service boundaries.</p><h3>6. Validate Input Early and Fail Fast</h3><p>Use Bean Validation (<em>@Valid, @NotNull, @Size</em>) in the controller layer to reject invalid requests before they reach the business logic or the database. This reduces unnecessary load and improves error clarity for API consumers.</p><h3>7. Secure the Application</h3><p>Enhancements aren’t just about speed. Apply Spring Security best practices: enforce HTTPS, use short-lived JWTs or OAuth2 tokens, rate-limit sensitive endpoints, and keep dependencies patched.</p><h3>Part 2: Database-Layer Enhancements</h3><h3>1. Tune the Connection Pool</h3><p>Spring Boot uses <strong>HikariCP</strong> by default; it’s fast, but the default pool size (10) is rarely optimal. Size it based on your database’s capacity and expected concurrency, not guesswork.</p><pre>spring:<br>  datasource:<br>    hikari:<br>      maximum-pool-size: 20<br>      minimum-idle: 5<br>      connection-timeout: 30000<br>      idle-timeout: 600000</pre><p>A common mistake is oversizing the pool; adding more connections than your database can efficiently handle often <em>reduces</em> throughput rather than improves it.</p><h3>2. Optimise Queries and Indexing</h3><ul><li>Add indexes on columns used in <em>WHERE</em>, <em>JOIN</em>, and <em>ORDER BY</em> clauses, but avoid over-indexing, since every index adds write overhead.</li><li>Use EXPLAIN ANALYZE(PostgreSQL) or equivalent to identify slow queries and full table scans.</li><li>Watch out for the <strong>N+1 query problem</strong> in JPA/Hibernate, a classic performance killer where fetching a list of entities triggers a separate query per related entity.</li></ul><pre>@OneToMany(mappedBy = &quot;author&quot;)<br>private List&lt;Book&gt; books;<br><br>// Fix: fetch eagerly with a join when you know you need the data<br>@Query(&quot;SELECT a FROM Author a JOIN FETCH a.books WHERE a.id = :id&quot;)<br>Author findByIdWithBooks(@Param(&quot;id&quot;) Long id);</pre><h3>3. Use Pagination for Large Result Sets</h3><p>Never return unbounded result sets to clients. Spring Data’s Pageable makes this straightforward and prevents both memory bloat and slow responses.</p><pre>Page&lt;Order&gt; findByCustomerId(Long customerId, Pageable pageable);</pre><h3>4. Manage Schema Changes with Migration Tools</h3><p>Use <strong>Flyway</strong> or <strong>Liquibase</strong> instead of <em>spring.jpa.hibernate.ddl-auto=update</em> in production. Versioned migrations give you a reliable, auditable history of schema changes and make rollbacks possible.</p><h3>5. Batch Writes</h3><p>For bulk inserts/updates, enable Hibernate batching rather than issuing one statement per row:</p><pre>spring:<br>  jpa:<br>    properties:<br>      hibernate:<br>        jdbc:<br>          batch_size: 50<br>        order_inserts: true<br>        order_updates: true</pre><h3>6. Consider Read Replicas and Caching for Read-Heavy Workloads</h3><p>If reads dominate writes, route read queries to a replica database and keep writes on the primary. Combine this with a second-level cache (Hibernate’s second-level cache with Redis/Ehcache) for frequently accessed, rarely changed data like reference tables.</p><h3>7. Use Projections for Lean Queries</h3><p>When you only need a few fields, avoid fetching entire entities. Spring Data projections (interface-based or DTO-based) reduce the amount of data pulled from the database and mapped into objects.</p><pre>public interface OrderSummary {<br>    Long getId();<br>    BigDecimal getTotal();<br>}<br><br>List&lt;OrderSummary&gt; findByStatus(String status);</pre><h3>Conclusion</h3><p>Enhancing a Spring Boot application isn’t a single fix; it’s an ongoing discipline of measuring, tuning, and validating changes under realistic load. The application layer and database layer are deeply connected: a beautifully optimised query won’t help if your connection pool is starved, and a well-tuned thread pool won’t save you from an N+1 query problem. Treat performance work iteratively; profile first, change one thing at a time, and measure the impact before moving to the next bottleneck.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0819c4eadec4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bootcamp challenges and how I have adapted in the last few weeks]]></title>
            <link>https://medium.com/@adeleyeadedolapomayowa/bootcamp-challenges-and-how-i-have-adapted-in-the-last-few-weeks-d3041cfbd55?source=rss-aceeef33b408------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3041cfbd55</guid>
            <category><![CDATA[adaptation]]></category>
            <category><![CDATA[andela]]></category>
            <dc:creator><![CDATA[Adeleye Adedolapo]]></dc:creator>
            <pubDate>Tue, 19 Mar 2019 15:13:47 GMT</pubDate>
            <atom:updated>2019-03-19T15:13:47.079Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/225/1*oEE-lVAqjEILtnKYKNoWYA.jpeg" /></figure><p>It&#39;s towards the end of boot camp and it has been a really long journey, I have faced a lot of challenges I have never encountered before, I had to either dig deep or look for someone who has encountered similar.</p><p>These challenges made boot camp fun to me, though I can count the number of times I smiled at during these few days. I have had to adapt in various ways I could never have thought.</p><p>Firstly, learning the right way to look for answers, Google up problems with the right questions, looking for peers who understand the problem than I do and when all fails I escalate to my learning-facilitator-assistant who is really experienced.</p><p>Secondly, I can proudly say what I learned these past few weeks feels like a semester worth of knowledge and I am really happy with that. It showed me that I could adapt to a lot of changes in a short space of time. I achieved all these knowledge by keeping studying till very late at night, ensuring I don&#39;t get discouraged when faced with challenges, sometimes I try to rest for a few hours when I am blocked as this gives me a different perspective towards the problem I am trying to solve</p><p>Thirdly, My time management and attention to detail have improved tremendously. This is one of the perks of being exposed to the boot camp process. At Andela, they hold these traits key, because as a software developer, meeting deadlines and building effective products are key to keeping the business alive. These past few days we have been giving challenges to submit and keeping to time while still giving out very good products rates you high.</p><p>All in all, Andela boot camp is a beautiful experience as it consistently tests your borders and pushes you to greater heights.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3041cfbd55" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Experience in Bootcamp so far]]></title>
            <link>https://medium.com/@adeleyeadedolapomayowa/my-experience-in-bootcamp-so-far-500b664adfd?source=rss-aceeef33b408------2</link>
            <guid isPermaLink="false">https://medium.com/p/500b664adfd</guid>
            <category><![CDATA[experience]]></category>
            <category><![CDATA[andela]]></category>
            <dc:creator><![CDATA[Adeleye Adedolapo]]></dc:creator>
            <pubDate>Thu, 14 Mar 2019 16:17:15 GMT</pubDate>
            <atom:updated>2019-03-14T16:17:15.312Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/259/1*nlLPK5RPcgOlNV3F-TedLA.jpeg" /></figure><p>It&#39;s the fourth day at boot camp, a lot has happened in the few days I have spent. I have learned a lot of new things, met a lot of new people and also built newer habits.</p><p>Asking questions has become a new habit I have formed, prior to Andela I would prefer keeping off and getting a way to solve the problem myself instead of getting someone who is more knowledgeable at the topic at hand. At Andela boot camp, life moves on really fast, it is very difficult keeping track of time.</p><p>My daily routine during the time I have spent here is very different from how it would have been during a regular day. Early mornings are spent preparing a meal to last the whole day as I cannot guarantee I will get another before night. Once that is handled, work for the day starts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/294/1*yFYoreRW2IUlRxpY-ZeevA.png" /></figure><p>Keeping time has been one of my challenges at the boot camp, gradually that has changed and will still get better as we have a lot of challenges to meet up with. Firstly, we post a stand-up on what we achieved the previous day, what we want to achieve the present day and any blockers we might or are facing trying to solve that.</p><p>A lot has changed since the first day, as I learned it is very beneficial to ask questions and be available to help your peers to when they are stuck. This has helped avert certain time wasters, as some challenges can be easily understood if you’re put through and once your peers understand they can also benefit from you too when they are stuck, it helps you understand things faster.</p><p>The most important things I have learned so far are persistence, relentlessness, unlearning to learn better. There are so many times these few days I have thought, why am I even trying out for this company, their processes are just unnecessary then again I think to myself as there are so many other ways I have improved myself which I would not have on a normal day. I am so happy to be part of this experience</p><p>All in all the experience has been really good, as I have learned a new way of life which has changed my habits in a good way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=500b664adfd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An interesting tool/technology I encountered in preparation for Bootcamp]]></title>
            <link>https://medium.com/@adeleyeadedolapomayowa/an-interesting-tool-technology-i-encountered-in-preparation-for-bootcamp-58baff1feb59?source=rss-aceeef33b408------2</link>
            <guid isPermaLink="false">https://medium.com/p/58baff1feb59</guid>
            <category><![CDATA[eslint]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Adeleye Adedolapo]]></dc:creator>
            <pubDate>Wed, 13 Mar 2019 14:39:47 GMT</pubDate>
            <atom:updated>2019-03-13T14:39:47.126Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*lmBh1aZebiCPmvWdZ5E1UQ.jpeg" /></figure><p>The tool I found most interesting is ESlint. Its a tool used in removing lint from your codes, like you remove lint from your dress. It is a really amazing tool because it gives you confidence in the way you write and structure your codes.</p><p>Before opting to use this tool, its cool to know that you will be frustrated at first because of all the errors it points out that you thought were cool. ESlint forces you to structure your codes according to industry standards. There are two popular styling guides namely: Google and Airbnb. Either of the two is fine to use, but Andela a software development company I aspire to work for encourages Airbnb.</p><p>According to my pre-boot-camp facilitator, ESlint is angry, and I cannot agree more, but when you think of the benefits, it totally outweighs the stress you&#39;ll face trying to restructure your code.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=58baff1feb59" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Reflections on the Andela Epic Values]]></title>
            <link>https://medium.com/@adeleyeadedolapomayowa/my-reflections-on-the-andela-epic-values-e82cdaadc139?source=rss-aceeef33b408------2</link>
            <guid isPermaLink="false">https://medium.com/p/e82cdaadc139</guid>
            <category><![CDATA[andela]]></category>
            <dc:creator><![CDATA[Adeleye Adedolapo]]></dc:creator>
            <pubDate>Tue, 12 Mar 2019 16:11:46 GMT</pubDate>
            <atom:updated>2019-03-12T16:11:46.263Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/304/1*nToxC5Ok3xFHpn4U1k1_vg.jpeg" /></figure><p>This is my second day of Andela boot-camp cycle 42 and it has been very interesting and challenging too, despite the challenges that you face, everyone here is expected to show certain traits which will determine if they will suit into Andela properly as a node.</p><p>Andela is a software development company that wants to bridge the skill gap between Africa and the western world, in doing so they require some traits in every staff they employ called the EPIC values. The EPIC values are really upheld at Andela and if you display something contrary, you would be disqualified. In the next paragraph, I will discuss my reflections on the EPIC Values letter by letter.</p><p>E — stands for excellence. Striving for excellence motivates you, it is about doing the right thing with the materials you have at your disposal. Excellence may be closely related to perfectionism, but the two are very different, the latter lets you set unrealistic goals which may, in turn, drain you mentally and defeat the purpose of whatever project you are on.</p><p>At Andela, they encourage you to strive for excellence as this will always bring out the best in you in any situation you find yourself.</p><p>P — stands for passion. Passion is a strong desire to achieve something, it is what fuels you to keep on striving even when the odds are against you. At Andela, they hold this trait dear to heart. As a company involved in solving various challenges in the world, using innovative ideas and tools to achieve all of these, it is very easy to lose focus, but when you have passion and believe in what you want to achieve you will find out you just keep going regardless of the blockers you may face.</p><p>I — stands for integriy. This is the value of being honest and having strong moral and ethical principles. Andela holds this trait dearest as it is believed every other value can be worked on and corrected, but when one purposely gives incorrect information about a subject, things can get messy. It is better to admit you made a mistake than deliver a project that is not optimal, thereby giving users wrong believes about the product you are selling.</p><p>C — stands for collaboration. Collaboration is very key, as the most tedious task can be accomplished in a short space of time. Andela cherishes collaboration and they make use of a lot of tools to achieve this. tools such as Github, Pivotal Tracker and also their in-house system called VOF tracker. All of the above-mentioned tools make collaborating with your peers and superiors seamless.</p><p>I hope I’ve been able to explain what I understand by the EPIC values and how they are making me a better person.</p><p>Thank you for reading</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e82cdaadc139" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Demonstrated Growth Mindset Recently]]></title>
            <link>https://medium.com/@adeleyeadedolapomayowa/how-i-demonstrated-growth-mindset-recently-26161b352e9c?source=rss-aceeef33b408------2</link>
            <guid isPermaLink="false">https://medium.com/p/26161b352e9c</guid>
            <category><![CDATA[growth-mindset]]></category>
            <dc:creator><![CDATA[Adeleye Adedolapo]]></dc:creator>
            <pubDate>Mon, 11 Mar 2019 14:44:46 GMT</pubDate>
            <atom:updated>2019-03-11T14:44:46.513Z</atom:updated>
            <content:encoded><![CDATA[<p>A mindset according to Carol Dweck “is a self-perception or ‘self-theory’ that people hold about themselves”, believing in what you can achieve and what you cannot is a simple example of mindset, and either of the two will determine what a person achieves in their endeavors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/259/1*jAyjkNmFMmRW3NO3jp71Tg.jpeg" /><figcaption>GROWTH!!!!!!…..</figcaption></figure><p>People with a growth mindset believe their basic talents or what they are not good at can be improved through persistence and hard work. This view creates a love for learning and the resilience to follow through with whatever they are trying to accomplish. People with a growth believe things will always change and try to adjust to these changes rather than feel accomplished with the conventional way of doing things.</p><p>Recently I have been faced with the task of getting employed by Andela, a software consulting firm with a branch in Nigeria. This process has been really tedious as they strive to adhere to global standards and expect all their employees to buy into this global mentality. I have been exposed to a whole lot of tools and approaches in doing things. Learning all of these has been really difficult due to some constraints such as electricity, internet connectivity and getting the right resources to unblock you when faced with a challenge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/275/1*Xpz1p8VQq28bxVMX-UrheA.jpeg" /></figure><p>A few months back I made it to the boot-camp phase of their recruitment process, I was very elated as it signified all the effort I put into improving myself was not in vain. On getting to the boot-camp I got exposed to newer concepts I didn’t know about before and this got me slightly depressed because with all the progress I thought I had made I still had a lot to learn, I didn&#39;t let this deter me from trying to learn these new tools. Although I didn’t make it past the boot-camp in that cycle, the failure pushed me to level up and now I feel way more confident and better than I was a few months back.</p><p><strong>Things to take from this write-up</strong></p><ol><li>I didn&#39;t let failure scare me.</li><li>I learnt through perseverance and persistence.</li><li>I found better ways to accomplish seemingly difficult tasks.</li><li>I could apply these new ways I learnt to solve other tasks</li><li>Most importantly, I got better and confident.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26161b352e9c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An interesting tool/technology I encountered in preparation for Bootcamp]]></title>
            <link>https://medium.com/@adeleyeadedolapomayowa/an-interesting-tool-technology-i-encountered-in-preparation-for-bootcamp-23384f7deade?source=rss-aceeef33b408------2</link>
            <guid isPermaLink="false">https://medium.com/p/23384f7deade</guid>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[Adeleye Adedolapo]]></dc:creator>
            <pubDate>Wed, 24 Oct 2018 16:52:38 GMT</pubDate>
            <atom:updated>2018-10-24T16:52:38.943Z</atom:updated>
            <content:encoded><![CDATA[<p>An interesting tool/technology I encountered in preparation for Bootcamp</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/348/1*BnUHSPO7hMkRMPifj4la8A.png" /></figure><p>The tool I find the most interesting is GIT and GITHUB. This tool enables very good collaboration between team members, it also encourages the agile methodology of development since it makes use of effective collaboration flexibility and adaptive measures in ensuring products are developed swiftly. Git is a version control system for tracking changes in computer files and coordinating work on those files among multiple people. It is primarily used for source-code management in software development but it can be used to keep track of changes in any set of files.</p><p>Git has a lot of important features like viewing the status of files you have worked on adding those files to the staging area that helps you know what has been tracked or not and also committing/saving those files. You can also create branches for your work which simply means the state of your work at a particular point in time. All of these can be done simply by typing commands into the command line interface. When you are done working with those files locally, you can PUSH them into the GITHUB website which stores you base code for you and your team member to view and make adjustments when necessary.</p><p>I have learned a few tricks using this technology and looking forward to learning a few more.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23384f7deade" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Reflections on Andela’s EPIC Values]]></title>
            <link>https://medium.com/@adeleyeadedolapomayowa/my-reflections-on-andelas-epic-values-2eb5ab2cb2cc?source=rss-aceeef33b408------2</link>
            <guid isPermaLink="false">https://medium.com/p/2eb5ab2cb2cc</guid>
            <category><![CDATA[andela]]></category>
            <dc:creator><![CDATA[Adeleye Adedolapo]]></dc:creator>
            <pubDate>Wed, 24 Oct 2018 15:55:39 GMT</pubDate>
            <atom:updated>2018-10-24T15:55:39.474Z</atom:updated>
            <content:encoded><![CDATA[<p>My Reflections on Andela’s EPIC Values</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*TfTIy7HrEyWrvSeFcb6EqA.jpeg" /></figure><p>Every organization has it’s culture and values staff must adhere to. The ANDELA EPIC values stand out as it pushes you constantly to be better than what you were in the past what seems normal and good 5 minutes ago may not be the right way to go about it now.</p><p>The EPIC stands for EXCELLENCE, PASSION, INTEGRITY, and COLLABORATION. I anyone that lives by these standards will achieve a great many things.</p><p>Excellence: The word is a description of itself, you strive to be the best you can be at all times, not just managing what you have but also looking for better ways to improve on the opportunities you have.</p><p>Passion: This is what drives you spurs your imagination to succeed, what picks you up when faced with challenges what powers you to exceed expectations, without this attribute you tend to quit at every roadblock you are faced with.</p><p>Integrity: This is a quality of being honest and having strong moral principles. The staff that embodies this quality tend to stand upright no matter the situation he or she is faced with, makes decisions based on what is right. This makes ANDELA staff stand out as you can take their words without thinking twice.</p><p>Collaboration: This is one value I like the most it brings people together no matter the culture or background as long as they are all willing to achieve the same goal. It Brings the best out of each member as no one will like to be a drag to the accomplishment of a product and it is also an avenue to learn more as no one is an island of knowledge</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2eb5ab2cb2cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>