The ZODB is a mature graph database written in Python and optimized in C. Just subclass off of class Persistent Object, and Persistent Container, and your objects, graphs and applications become persistent. The market for Graph Databases has recently exploded, as evidenced by over $200Million invested in graph database companies. Most of the graph databases are written in Java. If you are a Python developer, you will find much greater productivity using a graph database written in Python, than one written in statically bound Java. The major Java databases constrain you to one of several persistent data types. Persistent Python, supported by the ZODB allows you to make any Python Data Structure persistent. The new ZODB Demo makes it very easy to start building your own applications on top of the ZODB. You can start by customizing the TreeLeaf, TreeBranch and TreeRoot classes and their templates. You get CRUD for free. The demo includes traditional relational CRUD, Create, Read, Update, and Delete. But it also includes the extended graph CRUD. Rename a Leaf Or Branch. Cut and paste leaves or branches, copy and paste leaves or branches. The talk also demonstrates the soon-to-be released view historic versions and restore a previous version.
Większość zespołów, z którymi pracowałem kroczyła nigdy niekończącą się ścieżką w poszukiwaniu złotego środka w pisaniu dokumentacji. Miejscu, w którym czerpie się korzyści z posiadania pomocnej dokumentacji, jednak nie spędza się zbyt wiele czasu i energii na jej tworzeniu. Dla niektórych punktem wyjściowym jest popularny błąd, w którym mówi się, że kodu nie należy dokumentować, gdyż kod powinien być sam w sobie wystarczająco czytelny. Inni z kolei tworzą bardzo dokładną dokumentację i szybko wpadają w pułapkę ogromnego kosztu jej utrzymywania. Jest lepsza droga, aby inni programiści mieli dobre wrażenia. Podzielę się kilkoma sposobami, jak na przykład: • Częściowo lub całkowicie wykonywalna dokumentacja • Dokumentacja API zrozumiała dla maszyn i ludzi • Testy automatyczne jako dokumentacja
While searching the Internet for yet another module that's AsyncIO compatible I've stumbled upon this github comment: "Ya, IMHO the whole async stuff is yet-another-rift that the upstream python developers caused (without even calling it python 4.0) and I'm not even sure how many people/developers see that yet. (...)" ...and I completely agree with it. I've been running AsyncIO in production for over a year now and my initial enthusiasm has waned. Don't get me wrong, AsyncIO is great and I will continue using it. However, being at the technological edge comes with a price, which a lot of people is not aware of. In this presentation I'm going to talk about what I wished I had known before adding AsyncIO to our stack and share my experience with running and maintaining AsyncIO applications at Akamai.
Christopher Lozinski is an MIT graduate, serial entrepreneur, dual US-EU citizen, and polyglot. Instead of seeking Venture Capital, he moved from Silicon Valley to Poland. He started using the ZODB in 1999, built a number of products with it, most recently PythonLinks.info, and has now released the open source ZodbDemo.
I am a Software Engineer, mostly recognized for my numerous contributions to the tech community as an organizer, speaker and activist. Currently I am coding at Codility and training developers with Bottega. I had a lot of fun building communities like Warsaw Java User Group, Mobile Warsaw and organizing some great events (Mobile Central Europe, Warsjawa) and leading IT departaments in Polidea and Growbots. I am also a mathematician, amateur runner, notorious speaker.
Michal Wysokinski is a software engineer at Frameworks and Tools team making sure that Akamai is using only best tools for the job. He’s most recent work involves developing a framework for monitoring and testing Akamai’s vast CDN network of nearly 240 000 servers and creating a tool for alerting and live analysis based on microservices logs produced by Akamai’s internal cloud platform.
Deployed is a team of passionate software developers. Since 2011, we've been helping our clients to run and scale their businesses. With continuous growth, we now employ 24 people. What do we do? We work with international companies in multicultural and diverse environments. We are experts in Python and Django. We also specialize in ReactJS and React Native. What differentiates us from our competitors is that we scrutinously test our code, focus on quality in the development process, while writing and deploying clean code. Each year, we host Pykonik's website and provide sponsorship of related events. Come along and say hi to our team members! We are always looking for experienced Python/Django developers as well as fullstack developers, React/React Native developers, QA engineers and Systems administrators.