With Akka now considered critical infrastructure for many large organizations, the Apache 2.0 model becomes increasingly risky when a small company solely carries the maintenance effort. Over the years, Lightbend has steadily borne more of the support for Akka. It essentially gives users the right to do whatever they want without any restrictions or obligations to contribute back to the community and the project from which they benefit. PIXAVE 2.1.1 LICENSE LICENSEApache 2.0 is a very liberal license well suited for early, small open source projects establishing community. For better or worse, Apache was and still is seen as the de facto standard license of choice in the open source community. When I initially chose the Apache 2.0 license for Akka, I was unaware of the impact that choice would have if Akka became a large, global project. PIXAVE 2.1.1 LICENSE SOFTWAREIn the infrastructure space, much of the open source software is now created by companies, from small startups innovating and challenging the status quo, to large enterprises seeing open source as a great way to attract talent and build communities around their brands.Īt the same time, companies using open source software commercially have become more confident operating it themselves and less reliant on help from the companies developing the software. But in the last 10-15 years, this has drastically changed. In the early days of open source, as in the early days of Akka, most of the work was done by passionate developers during late nights and weekends, all for the love of programming and the joy of working on it together. I am so grateful for what it has enabled me to do, learn, and experience and the long-lasting friendships it has helped me build. When it works, like with Akka, it’s magic. Open source is the perfect environment to try out crazy ideas, to try to reach higher, and to be able to do it with peers that share the same passion and joy for programming, curiosity, creativity, and urge for change, regardless of background, gender, citizenship, ethnicity, political values, or whatever. Building software in the open and putting your work out there for everyone to see and judge can be scary, at least initially, but it can also be very rewarding. I owe so much to our amazing Akka community, who have been generous, helpful, and offering creative collaboration beyond boundaries. With the rise of edge computing, Akka’s model natively allows for building systems of services with millions of efficient, autonomous, mobile, self-organizing, self-healing, and location transparent services (actors) is an even better fit. It’s great that the industry has caught up with Akka and its reactive principles of system design. But it provided an ideal programming model for cloud computing years before it was even on most companies' radar. Its actor-based programming model-channeling the essence of distributed systems honestly, leveraging concepts like asynchronous messaging and computation, eventual consistency, event logging, and much more, a design we nowadays call reactive-could have been considered alien at the time. It is the runtime core for 1000s of products, many built by the Global 2000, including household names such as Apple, Disney, GM, HPE, Norwegian Cruise Lines, Starbucks, and Tesla.įor many years, Akka was ahead of its time. Today, Akka is exceptionally reliable, scalable, and performant. It’s been a fantastic journey so far (read about Akka’s inception and early days here). I created Akka 13 years ago out of love for programming, distributed systems, learning new things, and open source. Today, we are announcing a change to Akka’s license model so that Akka can be a thriving project for many decades.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |