Apache Shiro
Persistent Collection
| Apache Shiro | Persistent Collection | |
|---|---|---|
| 4 | 4 | |
| 4,263 | 746 | |
| 0.3% | - | |
| 9.5 | 6.6 | |
| 6 days ago | about 2 months ago | |
| Java | Java | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Apache Shiro
-
Serverless Apache Zeppelin on AWS
The only missing feature in this architecture is the login and logout capability. In this case, Apache Zeppelin provides Shiro for notebook authentication. Apache Shiro is a powerful and easy-to-use Java security framework that performs authentication, authorization, cryptography, and session management. Here, you can find a step-by-step guide about how Shiro works. This example uses the default configuration.
-
Reaper 3.0 for Apache Cassandra is available
Shiro 1.8.0
- Apache Shiro
-
Libraries, Frameworks and Technologies you would NOT recommend
Apache Shiro is another security framework. I haven't tried it out myself, but I was sorely tempted to when trying to set up Spring Security.
Persistent Collection
-
I had a great experience with Scala and hopefully it will get more popular
So does Java! Also, kotlinx.collections is still not stable and I don't think they are intending to make it so any time soon.
-
What’s so great about functional programming anyway?
> If you are using containers, always, always, always use immutable containers from Google Guava unless you have an exceptionally good reason.
I actually prefer pcollections: https://github.com/hrldcpr/pcollections
AtomicReference + immutable data types is a really nice way to program in Java, and is basically the way most Clojure programs are written.
- Why Java's Records Are Better* Than Lombok's Data and Kotlin's Data Classes
-
Libraries, Frameworks and Technologies you would NOT recommend
You might consider persistent collections instead of immutable collections, I believe it is more optimized https://github.com/hrldcpr/pcollections
What are some alternatives?
Keycloak - Open Source Identity and Access Management For Modern Applications and Services
Big Queue - A big, fast and persistent queue based on memory mapped file.
Spring Security - Spring Security
tape - A lightning fast, transactional, file-based FIFO for Android and Java.
pac4j - Security engine for Java (authentication, authorization, multi frameworks): OAuth, CAS, SAML, OpenID Connect, LDAP, JWT...
Apache Parquet - Apache Parquet
jCasbin - An authorization library that supports access control models like ACL, RBAC, ABAC in Java
SBE - Simple Binary Encoding (SBE) - High Performance Message Codec
Bouncy Castle - Bouncy Castle Java Distribution (Mirror)
Protobuf - Protocol Buffers - Google's data interchange format
OACC Framework - OACC (Object ACcess Control) is an advanced Java Application Security Framework
dexx - Persistent (immutable) collections for Java and Kotlin