Erwan Michel on LinkedIn: The end of 0% interest rates: what it means for software engineering… (2024)

As I read Gergely Orosz's latest article on post-ZIRP (zero percent interest rate policies) engineering practices, I began to reflect on my journey in leading the CREX 's engineering team:1. We started off with a monolith, and still remain largely a monolith. We only started 2 microservices which are stateless and serve a very specific purpose. (e.g. a PDF service that receives HTML and returns a PDF).2. We adopted full-stack Phoenix with Liveview for our monolith. We find that while liveview has its shortcomings, it is, in Gergely's words, "harder to notice" as compared to the "smaller team size, faster iteration and lower overall cost".3. We default to a "let's get this thing working first" mentality instead of imagining scenarios that might never happen. When we start to feel the pain, we have to update our implementation. This is a trade-off we knowingly take.4. Our team has more responsibilities - backend, frontend, design, devops, security - and even on the science and accounting standards. We have collective ownership on the overall product and do not shy away from stepping out from our engineering responsibility.That's being said, there are certain things I never compromise. I still believe in having good test coverage (although not necessarily 100%), good code readability and security.I am fortunate to work with a wonderful team, and I look forward to the next phase! Kong Lum Hon See Bei Low Korachal Phadvibulya Haruthai C. Chatchawas Wuttisirisart Daria Kushnir Anut Chatikavanijhttps://lnkd.in/g2_uuJbh

18

𝐌𝐨𝐧𝐨𝐥𝐢𝐭𝐡𝐢𝐜 𝐕𝐒 𝐌𝐢𝐜𝐫𝐨𝐬𝐞𝐫𝐯𝐢𝐜𝐞𝐬 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞: 𝐀 𝐒𝐭𝐫𝐚𝐭𝐞𝐠𝐢𝐜 𝐂𝐡𝐨𝐢𝐜𝐞In today's ever-evolving landscape of software development, the debate between Monolithic and Microservices architectures is more relevant than ever. It's crucial to understand the strengths and challenges of each approach. 🔍 𝐌𝐨𝐧𝐨𝐥𝐢𝐭𝐡𝐢𝐜 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 - Often seen as the traditional model, monolithic architecture is like a tightly interwoven fabric where all components of the application are interconnected and interdependent. This approach offers simplicity in development, deployment, and scaling for smaller applications or teams. However, as the application grows, scaling can become a challenge, leading to longer development cycles and complex debugging processes.🔍 𝐌𝐢𝐜𝐫𝐨𝐬𝐞𝐫𝐯𝐢𝐜𝐞𝐬 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 - Imagine a constellation, where each star is a service. Microservices architecture breaks down the application into a collection of smaller, independent services. This approach provides excellent scalability, flexibility, and the ability to use different technologies for different services. It's ideal for large, complex applications and teams that require agility and speed in development. However, it comes with its own set of challenges like increased complexity in managing multiple services and inter-service communication.➡As tech leaders, our choice between these architectures should align with our project requirements, team expertise, and long-term strategic goals.👥 I'm curious to hear from you! Are you team Monolithic or team Microservices? What has been your experience in implementing the architecture you chose? Share your insights and let's learn from each other.#softwaredevelopment #monolithicarchitecture #microservices #systemdesign

2

1 Comment

Choosing the Right Architecture: Monolithic vs. MicroservicesBuilding software? Choosing the right architecture is crucial. Let's compare two popular options:Monolithic:✅ Benefits:⚡️ Simple to develop and deploy.⚡️ Easy to debug and maintain.⚡️ Good performance for small-scale applications.❌ Disadvantages:⚡️ Difficult to scale and adapt to changing requirements.⚡️ Single point of failure: one bug can bring down the entire application.⚡️ Not suitable for complex applications with large teams.Microservices:✅ Benefits:⚡️ Highly scalable and adaptable.⚡️ Resilient to failures: one service failing doesn't affect others.⚡️ Enables independent development and deployment of services.⚡️ Suitable for large, complex applications with multiple teams.❌ Disadvantages:⚡️ Increased complexity in development and deployment.⚡️ Debugging and monitoring can be more challenging.⚡️ Requires additional infrastructure management.Choosing the right architecture depends on your specific needs. Consider factors like:⚡️ Application size and complexity.⚡️ Scalability requirements.⚡️ Team size and expertise.⚡️ Expected growth and change.No single architecture is perfect. Weigh the benefits and disadvantages carefully to choose the best fit for your project. I have used both architectures in my career, Comment on what you have used 🤔 . #softwarearchitecture #microservices #monolithic #development #webdev #appdev

22

🚀 Understanding the Difference Between Monolithic and Microservice Architecture 🌐🔹 Monolithic Architecture:Traditionally, monolithic architecture has been the go-to approach for developing software. In this model, an application is built as a single, tightly coupled unit, where all components are interconnected and interdependent. 🧩 This means that any changes or updates require the entire application to be rebuilt and redeployed. While it offers simplicity in development and testing, it can become a bottleneck when scaling, maintaining, and introducing new features.🔹 Microservice Architecture:Enter microservice architecture! 🌟 This innovative approach advocates breaking down an application into a collection of loosely coupled, independently deployable services. 🎯 Each service handles a specific business capability and communicates through well-defined APIs, enabling flexibility, scalability, and resilience. 🛠️ This modular nature allows teams to work independently on different services, deploy updates without affecting the entire system, and even adopt different technologies or programming languages for each service.🔸 Key Differences:1️⃣ Scalability: Monolithic architecture scales as a single unit, while microservices can scale individual services independently based on demand, improving performance and resource utilization.2️⃣ Maintenance: In monolithic architecture, any changes require redeployment of the entire application, making maintenance complex. Microservices allow independent development, testing, and deployment, making updates and bug fixes more manageable.3️⃣ Technology Diversity: Monolithic applications usually rely on a single technology stack, while microservices offer the flexibility to use different technologies for each service, selecting the best tools for the job.4️⃣ Resilience and Fault Isolation: Microservices are more resilient as failure in one service doesn't bring down the entire system. Additionally, it's easier to isolate and handle failures in specific services without impacting the entire application.Both architectures have their own merits and are suited for different scenarios. The choice between monolithic and microservice architecture depends on factors like project size, team structure, scalability requirements, and development velocity.Remember, embracing the right architectural approach can significantly impact the success of your software development projects. Stay curious, stay innovative! 💡Feel free to share your thoughts and experiences with these architectures in the comments. Let's keep the conversation going! 🗣️#technology #softwaredevelopment #systemdesign

8

The Power of Cloud-Native Architecture in Full Stack EngineeringIn today's rapidly evolving digital landscape, the role of full-stack engineering has become more crucial than ever. One of the foundational elements of this domain is the concept of "Cloud-Native Architecture." Let's dive deep into this topic.Understanding Cloud-NativeCloud-native is a design approach in software development that utilizes cloud computing to "build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds." It's about how applications are created and deployed, not where.Benefits of Cloud-Native ArchitectureScalability: One of the most significant advantages of cloud-native applications is their ability to scale out by adding more instances as opposed to scaling up (adding more power to existing hardware).Resilience: These applications are designed to handle failures gracefully. If one component fails, another can seamlessly take over.Flexibility: With cloud-native, developers can use the best languages, tools, and databases for the job without being tied to a specific technology stack.Speed: Continuous delivery is facilitated, allowing for faster iterations and quicker deployments.Challenges and ConsiderationsWhile the benefits are numerous, it's essential to understand the challenges. Transitioning to a cloud-native approach requires a shift in culture, processes, and technology. It's not just about using new tools but about changing how teams think about software development.ConclusionEmbracing cloud-native architecture in full-stack engineering offers a competitive edge, enabling businesses to adapt quickly to market changes, scale efficiently, and deliver unparalleled user experiences. As the digital world continues to evolve, understanding and implementing these principles will be key to staying ahead.

1

𝐌𝐨𝐧𝐨𝐥𝐢𝐭𝐡𝐢𝐜 𝐕𝐒 𝐌𝐢𝐜𝐫𝐨𝐬𝐞𝐫𝐯𝐢𝐜𝐞𝐬 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞: 𝐀 𝐒𝐭𝐫𝐚𝐭𝐞𝐠𝐢𝐜 𝐂𝐡𝐨𝐢𝐜𝐞In today's ever-evolving landscape of software development, the debate between Monolithic and Microservices architectures is more relevant than ever. It's crucial to understand the strengths and challenges of each approach.🔍 𝐌𝐨𝐧𝐨𝐥𝐢𝐭𝐡𝐢𝐜 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 - Often seen as the traditional model, monolithic architecture is like a tightly interwoven fabric where all components of the application are interconnected and interdependent. This approach offers simplicity in development, deployment, and scaling for smaller applications or teams. However, as the application grows, scaling can become a challenge, leading to longer development cycles and complex debugging processes.🔍 𝐌𝐢𝐜𝐫𝐨𝐬𝐞𝐫𝐯𝐢𝐜𝐞𝐬 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 - Imagine a constellation, where each star is a service. Microservices architecture breaks down the application into a collection of smaller, independent services. This approach provides excellent scalability, flexibility, and the ability to use different technologies for different services. It's ideal for large, complex applications and teams that require agility and speed in development. However, it comes with its own set of challenges like increased complexity in managing multiple services and inter-service communication.➡ As tech leaders, our choice between these architectures should align with our project requirements, team expertise, and long-term strategic goals.👥 I'm curious to hear from you! Are you team Monolithic or team Microservices? What has been your experience in implementing the architecture you chose? Share your insights and let's learn from each other.✅ Read more about Microservices: Grokking Microservice Design Patterns - https://lnkd.in/gDMtPQxiGif credit: Nelson Djalo#softwaredevelopment #monolithicarchitecture #microservices#systemdesign #monolithic #microservicesarchitecture #linkedinconnection #linkedinpost

416

21 Comments

💡In another post related to the end of the 0% interest era, Gergely argues(among other things) that one potential consequence of tighter budgets and the need to do more with less is the return to monolith architectures because companies struggle to handle the increased complexity of microservices (with reduced number of people). 🔻Also, looks like from the experience of several bigger companies, the microservice approach didn't quite bring the intended benefits. 💰Microservice architecture could be more suited for companies in aggressive growth and not for companies with more conservative growth. 📰An interesting read, same as with the other articles in the series, gives some food for thought about the impact of the economy status on how companies structure teams and even architectural decisions.https://lnkd.in/dndUXk67

3

𝐌𝐨𝐧𝐨𝐥𝐢𝐭𝐡𝐢𝐜 𝐕𝐒 𝐌𝐢𝐜𝐫𝐨𝐬𝐞𝐫𝐯𝐢𝐜𝐞𝐬 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞: 𝐀 𝐒𝐭𝐫𝐚𝐭𝐞𝐠𝐢𝐜 𝐂𝐡𝐨𝐢𝐜𝐞In today's ever-evolving landscape of software development, the debate between Monolithic and Microservices architectures is more relevant than ever. It's crucial to understand the strengths and challenges of each approach. 🔍 𝐌𝐨𝐧𝐨𝐥𝐢𝐭𝐡𝐢𝐜 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞- Often seen as the traditional model, monolithic architecture is like a tightly interwoven fabric where all components of the application are interconnected and interdependent. This approach offers simplicity in development, deployment, and scaling for smaller applications or teams. However, as the application grows, scaling can become a challenge, leading to longer development cycles and complex debugging processes.🔍 𝐌𝐢𝐜𝐫𝐨𝐬𝐞𝐫𝐯𝐢𝐜𝐞𝐬 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 - Imagine a constellation, where each star is a service. Microservices architecture breaks down the application into a collection of smaller, independent services. This approach provides excellent scalability, flexibility, and the ability to use different technologies for different services. It's ideal for large, complex applications and teams that require agility and speed in development. However, it comes with its own set of challenges like increased complexity in managing multiple services and inter-service communication.➡As tech leaders, our choice between these architectures should align with our project requirements, team expertise, and long-term strategic goals.👥 I'm curious to hear from you! Are you team Monolithic or team Microservices? What has been your experience in implementing the architecture you chose? Share your insights and let's learn from each other.✅ Read more about Microservices: Grokking Microservice Design Patterns - https://lnkd.in/gDMtPQxiGif credit: Nelson Djalo#softwaredevelopment #monolithicarchitecture #microservices #systemdesign

811

12 Comments

Monolithic Architecture ➡ Microservice EnvironmentsAt one point the norm, longer-standing businesses are moving away from the coding monoliths they architected originally, in favour of a modern microservices environment. Whilst not for everyone, the scalability and independence of microservice architecture is undeniable, here's some top tips I've learned from Lead Architects we've deployed on projects:- Don’t rush the discovery, you may not feel you're making any progress, but it’s vital you consider all variables before the implementation phase.- Once implementation has started, don’t bypass or tamper with the process, making minor manual changes is the start of a revert to the monolith.- Identify a most paramount business component and stick with it, all other components will become dependencies of that.- Upon completion, either the monolith will be fully dissolved, or what remains becomes a microservice in itself.- Typically, coding monoliths are written in older languages/frameworks, so if you also plan to modernise your tech stack, this should be done concurrently.If you've worked on a modernisation project like this and have any other tips on best practices, I'd love to hear them!Credit:Ronny Nielsen

14

6 Comments

As digital transformation continues to disrupt industries across the board, #platformengineering has emerged as a crucial set of practices and patterns for IT teams to enable self-service capabilities for software engineering teams. At its core, platform engineering aims to provide low-friction access to infrastructure for developers through an Internal Developer Platform (#IDP) that includes documentation and self-service tools. Why are we, providers of an application management platform, loving the growing adoption of platform engineering?In this blog post, we explore how platform engineering applies to edge computing, particularly as the platformization of the edge gains momentum. ▶️ Here is the full article: https://lnkd.in/dx2Kg4KPPsst. If Platform Engineering in Edge Computing is on your mind, you can also request your free copy of our white paper 💡 Confessions of a Platform Engineer: Edge Computing Rollout Edition 💡 ▶️ Access the paper here: https://lnkd.in/dMnsNURJ

34