Alternatives to Buck logo

Alternatives to Buck

Gradle, Apache Maven, CMake, Sonatype Nexus, and Apache Ant are the most popular alternatives and competitors to Buck.
19
57
+ 1
4

What is Buck and what are its top alternatives?

Buck encourages the creation of small, reusable modules consisting of code and resources, and supports a variety of languages on many platforms.
Buck is a tool in the Java Build Tools category of a tech stack.
Buck is an open source tool with 7.3K GitHub stars and 1.1K GitHub forks. Here鈥檚 a link to Buck's open source repository on GitHub

Buck alternatives & related posts

Gradle logo

Gradle

4.2K
3.2K
247
4.2K
3.2K
+ 1
247
A powerful build system for the JVM
Gradle logo
Gradle
VS
Buck logo
Buck

related Gradle posts

Apache Maven
Apache Maven
Gradle
Gradle

We use Apache Maven because it is a standard. Gradle is very good alternative, but Gradle doesn't provide any advantage for our project. Gradle is slower (without running daemon), need more resources and a learning curve is quite big. Our project can not use a great flexibility of Gradle. On the other hand, Maven is well-know tool integrated in many IDEs, Dockers and so on.

See more
Java
Java
JavaScript
JavaScript
Node.js
Node.js
nginx
nginx
Ubuntu
Ubuntu
MongoDB
MongoDB
Amazon EC2
Amazon EC2
Redis
Redis
Amazon S3
Amazon S3
AWS Lambda
AWS Lambda
RabbitMQ
RabbitMQ
Kafka
Kafka
MySQL
MySQL
Spring Boot
Spring Boot
Dropwizard
Dropwizard
Google Analytics
Google Analytics
Elasticsearch
Elasticsearch
Amazon Route 53
Amazon Route 53
GitHub
GitHub
Docker
Docker
Webpack
Webpack
CircleCI
CircleCI
Jenkins
Jenkins
Travis CI
Travis CI
Gradle
Gradle
Apache Maven
Apache Maven
Jira
Jira
notion.so
notion.so
Trello
Trello
Vue.js
Vue.js
Flutter
Flutter
Application & Data

Java JavaScript Node.js nginx Ubuntu MongoDB Amazon EC2 Redis Amazon S3 AWS Lambda RabbitMQ Kafka MySQL Spring Boot Dropwizard Vue.js Flutter

Utilities

Google Analytics Elasticsearch Amazon Route 53

DevOps

GitHub Docker Webpack CircleCI Jenkins Travis CI Gradle Apache Maven

Cooperation Tools

Jira notion.so Trello

See more

related Apache Maven posts

Tymoteusz Paul
Tymoteusz Paul
Devops guy at X20X Development LTD | 21 upvotes 1.7M views
Vagrant
Vagrant
VirtualBox
VirtualBox
Ansible
Ansible
Elasticsearch
Elasticsearch
Kibana
Kibana
Logstash
Logstash
TeamCity
TeamCity
Jenkins
Jenkins
Slack
Slack
Apache Maven
Apache Maven
Vault
Vault
Git
Git
Docker
Docker
CircleCI
CircleCI
LXC
LXC
Amazon EC2
Amazon EC2

Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

See more
Ganesa Vijayakumar
Ganesa Vijayakumar
Full Stack Coder | Module Lead | 15 upvotes 975K views
Codacy
Codacy
SonarQube
SonarQube
React
React
React Router
React Router
React Native
React Native
JavaScript
JavaScript
jQuery
jQuery
jQuery UI
jQuery UI
jQuery Mobile
jQuery Mobile
Bootstrap
Bootstrap
Java
Java
Node.js
Node.js
MySQL
MySQL
Hibernate
Hibernate
Heroku
Heroku
Amazon S3
Amazon S3
Amazon RDS
Amazon RDS
Solr
Solr
Elasticsearch
Elasticsearch
Amazon Route 53
Amazon Route 53
Microsoft Azure
Microsoft Azure
Amazon EC2 Container Service
Amazon EC2 Container Service
Apache Maven
Apache Maven
Git
Git
Docker
Docker

I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

As per my work experience and knowledge, I have chosen the followings stacks to this mission.

UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

Happy Coding! Suggestions are welcome! :)

Thanks, Ganesa

See more
CMake logo

CMake

332
71
1
332
71
+ 1
1
An open-source system that manages the build process
CMake logo
CMake
VS
Buck logo
Buck
Sonatype Nexus logo

Sonatype Nexus

280
144
0
280
144
+ 1
0
organize, store, and distribute software components
    Be the first to leave a pro
    Sonatype Nexus logo
    Sonatype Nexus
    VS
    Buck logo
    Buck

    related Sonatype Nexus posts

    Joshua Dean K眉pper
    Joshua Dean K眉pper
    CEO at Scrayos UG (haftungsbeschr盲nkt) | 5 upvotes 52.8K views
    atScrayos UG (haftungsbeschr盲nkt)Scrayos UG (haftungsbeschr盲nkt)
    Sonatype Nexus
    Sonatype Nexus
    GitLab
    GitLab
    JFrog Artifactory
    JFrog Artifactory

    We use Sonatype Nexus to store our closed-source java libraries to simplify our deployment and dependency-management. While there are many alternatives, most of them are expensive ( GitLab Enterprise ), monilithic ( JFrog Artifactory ) or only offer SaaS-licences. We preferred the on-premise approach of Nexus and therefore decided to use it.

    We exclusively use the Maven-capabilities and are glad that the modular design of Nexus allows us to run it very lightweight.

    See more
    Docker
    Docker
    Red Hat OpenShift
    Red Hat OpenShift
    SonarQube
    SonarQube
    Sonatype Nexus
    Sonatype Nexus
    GitLab
    GitLab
    Vault
    Vault
    Apache Maven
    Apache Maven
    AngularJS
    AngularJS
    Spring Boot
    Spring Boot
    #DeploymentWorkflow

    We use Docker for our #DeploymentWorkflow along with OpenShift SonarQube Sonatype Nexus GitLab Vault Apache Maven AngularJS Spring-Boot

    See more
    Apache Ant logo

    Apache Ant

    132
    97
    7
    132
    97
    + 1
    7
    Java based build tool
    Apache Ant logo
    Apache Ant
    VS
    Buck logo
    Buck

    related Apache Ant posts

    Joshua Dean K眉pper
    Joshua Dean K眉pper
    CEO at Scrayos UG (haftungsbeschr盲nkt) | 1 upvotes 147.5K views
    atScrayos UG (haftungsbeschr盲nkt)Scrayos UG (haftungsbeschr盲nkt)
    Apache Maven
    Apache Maven
    Apache Ant
    Apache Ant
    Gradle
    Gradle
    Bazel
    Bazel

    All Java-Projects are compiled using Apache Maven. We prefer it over Apache Ant and Gradle as it combines lightweightness with feature-richness and offers basically all we can imagine from a software project-management tool and more. We're open however to re-evaluate this decision in favor of Gradle or Bazel in the future if we feel like we're missing out on anything.

    See more
    JFrog Artifactory logo

    JFrog Artifactory

    131
    90
    0
    131
    90
    + 1
    0
    Enterprise Universal Repository Manager
      Be the first to leave a pro
      JFrog Artifactory logo
      JFrog Artifactory
      VS
      Buck logo
      Buck

      related JFrog Artifactory posts

      Joshua Dean K眉pper
      Joshua Dean K眉pper
      CEO at Scrayos UG (haftungsbeschr盲nkt) | 5 upvotes 52.8K views
      atScrayos UG (haftungsbeschr盲nkt)Scrayos UG (haftungsbeschr盲nkt)
      Sonatype Nexus
      Sonatype Nexus
      GitLab
      GitLab
      JFrog Artifactory
      JFrog Artifactory

      We use Sonatype Nexus to store our closed-source java libraries to simplify our deployment and dependency-management. While there are many alternatives, most of them are expensive ( GitLab Enterprise ), monilithic ( JFrog Artifactory ) or only offer SaaS-licences. We preferred the on-premise approach of Nexus and therefore decided to use it.

      We exclusively use the Maven-capabilities and are glad that the modular design of Nexus allows us to run it very lightweight.

      See more

      related Bazel posts

      Joshua Dean K眉pper
      Joshua Dean K眉pper
      CEO at Scrayos UG (haftungsbeschr盲nkt) | 1 upvotes 147.5K views
      atScrayos UG (haftungsbeschr盲nkt)Scrayos UG (haftungsbeschr盲nkt)
      Apache Maven
      Apache Maven
      Apache Ant
      Apache Ant
      Gradle
      Gradle
      Bazel
      Bazel

      All Java-Projects are compiled using Apache Maven. We prefer it over Apache Ant and Gradle as it combines lightweightness with feature-richness and offers basically all we can imagine from a software project-management tool and more. We're open however to re-evaluate this decision in favor of Gradle or Bazel in the future if we feel like we're missing out on anything.

      See more
      SBT logo

      SBT

      92
      48
      0
      92
      48
      + 1
      0
      An open source build tool for Scala and Java projects
        Be the first to leave a pro
        SBT logo
        SBT
        VS
        Buck logo
        Buck