Clojure vs Spring: What are the differences?
What is Clojure? A dynamic programming language that targets the Java Virtual Machine. Clojure is designed to be a general-purpose language, combining the approachability and interactive development of a scripting language with an efficient and robust infrastructure for multithreaded programming. Clojure is a compiled language - it compiles directly to JVM bytecode, yet remains completely dynamic. Clojure is a dialect of Lisp, and shares with Lisp the code-as-data philosophy and a powerful macro system.
What is Spring? Provides a comprehensive programming and configuration model for modern Java-based enterprise applications. A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments.
Clojure belongs to "Languages" category of the tech stack, while Spring can be primarily classified under "Frameworks (Full Stack)".
"It is a lisp", "Concise syntax" and "Persistent data structures" are the key factors why developers consider Clojure; whereas "Java", "Open source" and "Great community" are the primary reasons why Spring is favored.
Clojure and Spring are both open source tools. It seems that Spring with 30.6K GitHub stars and 19.6K forks on GitHub has more adoption than Clojure with 7.85K GitHub stars and 1.25K GitHub forks.
MIT, Zillow, and Intuit are some of the popular companies that use Spring, whereas Clojure is used by Nubank, CircleCI, and Groupon. Spring has a broader approval, being mentioned in 319 company stacks & 184 developers stacks; compared to Clojure, which is listed in 95 company stacks and 80 developer stacks.
What is Clojure?
What is Spring?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Stitch is run entirely on AWS. All of our transactional databases are run with Amazon RDS, and we rely on Amazon S3 for data persistence in various stages of our pipeline. Our product integrates with Amazon Redshift as a data destination, and we also use Redshift as an internal data warehouse (powered by Stitch, of course).
The majority of our services run on stateless Amazon EC2 instances that are managed by AWS OpsWorks. We recently introduced Kubernetes into our infrastructure to run the scheduled jobs that execute Singer code to extract data from various sources. Although we tend to be wary of shiny new toys, Kubernetes has proven to be a good fit for this problem, and its stability, strong community and helpful tooling have made it easy for us to incorporate into our operations.
I adopted Clojure and ClojureScript because:
- it's 1 language, multiple platforms.
- Simple syntax.
- Designed to avoid unwanted side effects and bugs.
- Immutable data-structures.
- Compact code, very expressive.
- Source code is data.
- It has super-flexible macro.
- Has metadata.
To complement Java. The REPL lets me interactively exercise Java code. I can write performant and safe libraries in Java, and then use them in Clojure. I also find the data-centric aspect of Clojure (excellent build-in structures, literal syntax for easily creating those structures, functions that act well on abstractions of those structures) good for data processing.
This fits a sweet spot between Ruby and Java.
Spring is another gift rained down by the gods of Open Source Software (a.k.a. Pivotal Labs in this particular case) that just makes sense on all levels.
From Spring Boot, to SpringMVC, the configuration architecture & profile paradigm, Spring Cloud expandability, to the ease with which one can deploy Spring applets as microservices within Docker is an absolute joy.
We use Clojure mostly for its "Minority Report"-like interactive development in situations that require 'semi-automatic programming' (data inspection, admin tasks, API exploration, scrapers, etc.). We have also used Clojure successfully to build some components of our stack very quickly and reliably, in the backend and the frontend.
just started learning clojure, maybe around two weeks or so. i'm addicted. this is what i want to be working with and learning for the foreseeable future. the elegance of the language is refreshing. the community is really amazing. i've finally found a language that fits my passion for programming.
Clojure simplifies and reduces the coding efforts involved in creating CloudRepo. The fact that it runs in the JVM gives us access to all the libraries that we could ever need. Our code base is much smaller and easier to reason about than it would have been had we gone with pure Java.
The core of the application use Spring Stack, to provide services and structure like:
- Self contained application with spring boot
- And many others.
그냥 간단한 MVC 웹 프레임 워크 인줄 알았는데 정말 모듈화가 잘 되있고, 사용하다보면 개발자에게 정말 편리하게 만들어 놓았다. vaildation 부분은 따로 처리 할 수 있고, 파라미터 담는 변수와 디폴트 값을 인자로 설정해 주는 부분도 참 좋은 것 같다. 또 spring-data 는 jpa 활용해 빠르게 개발하는데 유용하다.
- SpringFramework 중 MVC , AOP 등의 라이브러리를 활용하여 웹 어플리케이션 프로젝트 구성
공통 로직 구현 및 보안 처리 가능
Spring5에서 지원하는 함수형 프로그래밍 경험 있음