Mambu VS git-sizer

• Scalability
  Mambu is designed to scale easily, accommodating the growth of financial institutions without significant architectural changes.
• Flexibility
  Mambu provides a modular and API-driven architecture, allowing for customized features and integrations with other systems.
• Speed of Deployment
  Being a cloud-based solution, Mambu can be deployed faster compared to traditional core banking systems, reducing time to market.
• Regulatory Compliance
  Mambu includes built-in features for regulatory compliance across different regions, easing the burden on financial institutions.
• Cost-Effective
  The SaaS (Software as a Service) model of Mambu can be more cost-effective as it reduces the need for extensive on-premises infrastructure and maintenance.
• Continuous Updates
  Mambu provides regular updates and improvements, ensuring the platform remains up-to-date with the latest features and security protocols.
• User-Friendly
  Mambu offers a user-friendly interface that simplifies the management of financial products and services.

Possible disadvantages

• Internet Dependency
  As a cloud-based solution, Mambu relies heavily on internet connectivity, which could be a constraint in regions with unstable internet access.
• Customization Limitations
  Despite its modularity, there may still be limitations to how much you can customize Mambu to fit specific business needs.
• Data Security Concerns
  Storing sensitive financial data in the cloud may raise security concerns, especially for institutions that prefer on-premises solutions.
• Integration Complexity
  While Mambu offers APIs for integration, connecting it seamlessly with legacy systems or other third-party applications can be complex and time-consuming.
• Cost for High Usage
  While Mambu's SaaS model can be cost-effective initially, high usage and scaling can lead to increased subscription costs over time.
• Limited Offline Capabilities
  Mambu's functionality may be significantly limited without an internet connection, which can impact business continuity in areas with poor connectivity.

• Comprehensive Repository Analysis
  git-sizer analyzes many different dimensions of a Git repository including commit count, tree size, blob size, history depth, and reference counts, providing a holistic view of repository health and potential scaling issues.
• Easy to Use
  The tool is simple to run with minimal setup—just execute it within a git repository—and it produces clear, human-readable output that highlights potential problem areas without requiring complex configuration.
• Identifies Performance Bottlenecks
  It helps identify specific issues that could degrade Git performance, such as excessively large blobs, deep history, large trees, or too many references, which is valuable before migrating or scaling repositories.
• Open Source and Maintained by GitHub
  Being an official GitHub project, it benefits from credibility, community trust, and ongoing maintenance, and it is well documented with clear explanations of what each metric means.
• Useful for Pre-Migration Checks
  It's particularly helpful for teams migrating repositories to new platforms or consolidating repos, as it flags potential issues that could cause problems during migration or with hosting providers' limits.

Possible disadvantages

• No Automatic Remediation
  git-sizer only identifies and reports issues but does not offer any built-in tools or automated processes to fix problems like large blobs or excessive history depth—users must use separate tools like BFG Repo-Cleaner or git-filter-repo.
• Output Can Be Overwhelming for Beginners
  While detailed, the output includes many metrics and threshold levels that may be confusing for users unfamiliar with Git internals, requiring some learning curve to fully interpret results.
• Limited to Local Analysis
  The tool analyzes a local clone of the repository, so it requires users to have a full local copy of the repo (or at least enough history) to get accurate results, which can be time-consuming for very large repositories.
• No Real-Time Monitoring
  It functions as a one-time analysis tool rather than providing continuous or real-time monitoring of repository health, requiring manual reruns to track changes over time.
• Command-Line Only Interface
  The tool lacks a graphical user interface, which may be less accessible for users who prefer visual dashboards or are less comfortable with command-line tools.

No analysis of Mambu yet.

P.F.C. makes banking experience personal with Mambu's cloud-native banking platform.

More videos

No git-sizer videos yet. You could help us improve this page by suggesting one.

• Ask HN: Who is hiring? (October 2024)

  Mambu (https://mambu.com) | Engineering Managers, Software Engineers (Java) | Full-time | Remote (Netherlands, Romania, Lithuania) We're Mambu, a SaaS company providing the core banking engine for modern financial institutions. Our... - Source: Hacker News / almost 2 years ago

• The future of Kubernetes? 5 trends from Kubecon!

  There's already banks running white labelled in the cloud, take for example the services mambu (https://mambu.com) offers. Why wouldn't they be able to run in the cloud? Source: over 3 years ago

• how to keep github repos small?

  Also there’s a cool project from GitHub you can use to help understand the size of git’s objects in your git repo https://github.com/github/git-sizer. This might help you determine what the best cloning strategy could be. Source: almost 5 years ago