Giulia Serra
Bologna, Emilia Romagna, Italia
777 follower
Oltre 500 collegamenti
Esperienza
-
-
-
-
-
-
-
Formazione
Corsi
-
Agile Project Management
-
-
IdentityIQ Implementation: Essentials v7.2
Sailpoint University
-
Java Spring Framework & Hibernate
-
-
Oracle Identity Governance 11gR2 - Develop Identity Provisioning
Oracle University
-
Oracle Identity Governance 11gR2 - Essentials
Oracle University
Lingue
-
Inglese
Conoscenza professionale
-
Italiano
Conoscenza madrelingua o bilingue
Altri profili simili
Esplora altri post
-
Alejandro Duarte
😊 Happy to be one of the speakers at WMF - We Make Future 2024 in #Bologna, #Italy. I'll be talking about the history of relational databases, the origins of #MySQL and #MariaDB, how to handle different workloads in a single database using pluggable storage engines, how to use database proxies to achieve high availability, how to use #NoSQL with MariaDB, horizontal scaling with read/write splitting, change data capture, data ingestion, #ColumnStore, and much more! 👉 https://lnkd.in/gGA6-fdK #WMF2024 #WeMakeFuture
2 commenti -
HPC Knowledge Portal
"Kubernetes for HPC Services" by Davide Pastorino and Diego Bacchin (Do IT Systems S.r.l. – Do IT Now Alliance) Abstract: This presentation explores the use of #Kubernetes, a powerful container orchestration platform, to deliver high-performance computing (HPC) management and monitoring services. It discusses how Kubernetes can enhance the provisioning, management, and scalability of such HPC services. Key topics include the design decisions regarding the Kubernetes infrastructure and related services, as well as the deployment of HPC management and monitoring services. Attendees will gain insights into leveraging Kubernetes to modernize and optimize HPC management services. #HPC #HPCKP #HPCKP24
-
Luigi Perrone
Lo sapevi che... do you remember the "Secure Boot" feature present on the z16 systems used to verify the initial system code so that, if not validated, the bootstrap fails ? This is valid for the Linux on Z world. But for z/OS environment ? Despite having the same objective, in z/OS systems we talk about "Validated Boot", in order to control the bootstrap code (IPL) via digital signatures. It is a different implementation from the Secure Boot, but it too is aimed at validating that the IPL data is intact, not tampered with and originating from a reliable source, or in any case to detect unauthorized changes to the IPL executable code. In this way is it possible to demonstrate the compliant with NIAP (National Information Assurance Partnership) certification, which is required for certain secure software distribution scenarios. To know more : https://lnkd.in/dPyURcpf #secure #zsecure #ibm #security #z16 #mainframe #cybersecurity
1 commento -
Luigi Perrone
Lo sapevi che ... with zMFA 2.3 you can configure Single Sign-On (SSO) using the OpenID Connect (OIDC) protocol. The OIDC protocol works in conjunction with the Node.js application that must be configured to perform SSO. Here is the authentication flow with zMFA during SSO: • JSON Web Token (JWT) validation. • SSO ID extraction. • Verify that the SSO-ID matches the SSO-ID configured for the zMFA user. • With positive verification then zMFA generates a CTC (CacheTokenCredential) that can be spent. To learn more: https://lnkd.in/dAuNXHpn #mainframesecurity #zsecurity #security #zmfa #mfa #authentication #ibm #mainframe
-
CodeAir
Introduction These days I feel like we’re lucky to have the chance to choose the tools we want to work with. I really like GraphQL and in my opinion it is an important piece, even in cases where the backend programming language is different from that of the frontend. And regardless of the context/language, there is always tooling for schema-based codegen. In cases where you have a monorepo that uses TypeScript, tRPC is undoubtedly a great tool to be used in this context and one of the great advantages is that it is simple and intuitive and I feel that we can be much more productive. However, we are not always that lucky, because the backend may use a different language and prefer to use REST. In these cases, many people either create an API client with the definition of data types, or use validation schemas to guarantee type-safety at runtime and infer types from them. Today I’m going to share a solution that in my opinion is very interesting, it’s called feTS, it’s also an end-to-end solution but today I’m going to teach you how to use it just as an http api client. Getting Started We start by running the following command: npm install fets Enter fullscreen mode Exit fullscreen mode In the next step we will need a definition of an OpenAPI. In today’s article I will use the {JSON} Placeholder found in this Gist. After copying the contents of the yaml file, let’s open SwaggerEditor and convert the yaml definition to json and in our project we can create the file openapi.ts and assign the json of the OpenAPI specification to a variable called openapi as follows: export const openapi = { // OpenAPI specification... } as const; Enter fullscreen mode Exit fullscreen mode In the main.ts (or other) file we can start by importing the necessary feTS primitives to create our type-safe client together with the openapi we just created. After instantiating the client we can define the API endpoint that we will consume and we will have the client ready and completely type-safe. import { createClient, type NormalizeOAS } from "fets"; import { openapi } from "./openapi"; const client = createClient<NormalizeOAS>({ endpoint: "https://lnkd.in/dc6jMAC", }); const response = await client["/posts/{id}"].get({ params: { id: 3 } }); const data = await response.json(); console.log(data); Enter fullscreen mode Exit fullscreen mode Obviously I wouldn’t leave the article here because another topic I want to cover is the creation of plugins. Let’s assume that our API needs to send the token in the headers so that we can be authorized to consume resources protected by the REST API. To do this, we will create a plugin called useAuthPlugin which will have the following interfaces: export type Tokens = { accessToken: string; refreshToken: string; }; export type AuthPluginOpts = { refreshToken: () => Promise; actions: {
-
Fabrizio Rametta
Italians will say "Il bello della diretta" which - in this case - can be translated into "The fun of live coding". This is a beautiful video about the power of GitHub Copilot and how it can help you not only when you are already able to coding on a specific language, but also in case you really don't have any expertise on that. The author shows how to deal with a Python application without knowing anything, not only from live coding point of view (you write what you want and he produces the code) but also from a live prompt where you can ask less concise questions and wait for a nice reply. There is two sentences the author affirms that we need to focus on when approach on Github Copilot: 1. You are always responsible for the code you will push. Copilot is just an assistant, a co-worker for pair programming. But you are the owner of the code and you need to take always care about correctness and quality 2. Every time you use it, you can receive different suggestions, so do not trust on predictability for produced code At the end of the speech, there is also a nice overview about the Enterprise Version, which means that - not only but for me it is the most relevant thing - you can train your Copilot with your own codebase and he can learn from that (especially for internal API, catalogs and so on). The last fragment of the video shows also a study on impact of Github Copilot: it seems to reduce the develop time of 55% and increase of 90% the joy of coding for programmers. I personally don't think 55% is a percentage that can be reached because - for me - reducing the time of producing code means that I can focus more on code quality and tests. So even if you reduce of 55%, you will spend 30% more time to improve what I said, so give you the math (and remember that more quality means also less bugs and less rework) Take a look https://lnkd.in/dbRVUGTR
-
Vincenzo Lombardo
RIlasciato nifi 2.0 M4 n.d.r : speravamo nella versione production ready ma ci sono alcune cose interessanti comunque in questa quarta milestone. Sotto alcune delle nuove funzionalità e improvements (dalle Release Notes) : Nuove funzionalità - Completely rebuilt user interface featuring system or user selectable dark mode! - Support for Kafka 3 in for both consumption and publishing with Kafka. - Now able to split binary Packet Capture (PCAP) with SplitPCAP - Microsoft Excel XLSX files can be split to individual sheets with SplitExcel. - DeleteFile allows for removal of local files - New interface for Python extensions supporting components which source new data called FlowFileSource Improvements - Added Python Processor support to MiNiFi framework - Added App Installation Token support to GitHub FlowRegistryClient - Improved framework keystore and truststore handling to support dynamic reloading for cluster communication - Changed from RSA to Ed25519 for signing and verification of Application Bearer Tokens
-
Nicola De Filippo
REST is not just about CRUD; it is defined in the paper "Architectural Styles and the Design of Network-based Software Architectures" by Roy Thomas Fielding. One of the properties described in the paper is ‘Code on Demand,’ where the client can request a script or binary from the server (similar to what happens when a browser requests JavaScript files to extend the behavior of a web page). This concept is powerful, but it’s not exclusive to the web world. In this post, you can see the same concept applied using #Qt. #systemdesign
-
JAPO Dev Solutions
JAPO v1.2 released, along with JAPO Plugin for JetBrains IntelliJ IDEA Enhancements: - Multi-Annotations Search: enhanced the search endpoint to allow searching for multiple annotations within a single query - Submit and Schedule Annotations Updates: you can now submit annotations updates ahead of the release date of the maven artifact containing those updates, and then indicate the desired date at which the updates should be published to JAPO users - Introducing JAPO Plugin for JetBrains IntelliJ IDEA Bug Fixes: - Fixed minor issues with search queries validation logic https://lnkd.in/eTkFszAd #japo #java #annotations #search #engine
-
Fabrizio Rametta
API versioning is one of the features that is most underrated and developers (but also architects, product manager and so on) don't take care about it. Focus on version means that your APIs are really well maintained and documented and you are able to offer backward compatibility across the time by using a valid notation (minor, major, patch). To assure that everything is working it's really important to have a solid tests for your code because every little change should be under your control. In my experience I see that versioning is not used for internal API, like people don't carein a microservices landscape: just send an email to other silos with "Why bro, we are changing this and that, please verify everything works" which means pushing responsibility to other people. For companies that expose APIs to internet or in general as a service, versioning is a must and developers should adhere to his principles, because clients pay for that and should be always safe in what they use. As per the article there are very ways to version, and I see that people tend to use the uri version (which has higher boundaries). Take a look https://lnkd.in/d5cw3Hvh
-
Davide Bellone
🚀 Unlock the Power of Arc42 for Your Software Projects! 🚀 Hey #Developers, #Architects, and #TechEnthusiasts! 🌟 Struggling with project documentation? 🤔 Arc42 is a template you may want to use! What you'll find in this article: 1️⃣ Comprehensive Guide: Learn how Arc42 structures your documentation, making it future-proof and easy to maintain. 🛠️ 2️⃣ Practical Tips: Get actionable insights on how to implement Arc42 using tools like Confluence, Word, and Markdown. 📝 3️⃣ Detailed Sections: Understand the 12 key sections of Arc42, from Introduction & Goals to Risks & Technical Debt. 📊 4️⃣ Real-World Examples: See how Arc42 can be applied to real projects, ensuring you capture all essential details. 🌐 5️⃣ Free Templates: Access handy templates to kickstart your documentation process without hassle. 🎁 Don’t miss out on this opportunity to elevate your project documentation game! 💪 #SoftwareArchitecture #Documentation #Arc42 #TechTips https://lnkd.in/dWFp9EkQ
-
CodeAir
Due to changing times, companies, thankfully, no longer create a monolithic application that does everything. Instead, that same application is divided into different modules or small projects, each performing a specific function. We call the use of small projects to build a larger application the microservices architecture. The reason I mention this architecture here is that microservices rely on or are based on APIs. What is an API? There are various ways to define what an API is. Personally, I define an API as the entry point from the outside into your project. Of course, the same applies when we are the ones consuming different APIs. We have our front end, which consumes the back end through an API, and in turn, the back end consumes two other services through APIs. An API can return either a single character or a list with thousands of elements. Types of API in C# In C#, we have two options for creating APIs: SOAP and REST. Both options have different characteristics, but the ultimate goal is the same: sending information between a client and a server. 2.1 Differences between SOAP and REST Protocol: A significant difference is that SOAP is a protocol, while REST is an architecture that operates on the HTTP protocol. Development: Developing a SOAP service takes more time, both for the client and the server. In REST, we operate over the HTTP protocol, which means that to receive/send information, we do it through web requests, through the URL, or using the message body. Developing a REST API is much faster than a SOAP web service. SOAP has advantages in other aspects, for example, it can maintain state between several requests, while in REST, each request is individual. Due to the mentioned file (.wsdl) with XML and DTD, SOAP services are much more secure. Creating an API in C# When creating APIs, we should design the endpoints with CRUD in mind. 3.1 What is CRUD? CRUD is an acronym referring to its initials: Create (create): Using the HTTP POST method. Read (read): Using the HTTP GET method. Update (update): Using HTTP PUT. Delete (delete): Using HTTP DELETE. There are more HTTP methods, but 99.9% of actions are performed with these. In C#, our entry point will be the controllers. To do this, we must ensure that within the Startup.cs class, we have the service that adds the controllers. public void ConfigureServices(IServiceCollection services) { services.AddControllers(); } Enter fullscreen mode Exit fullscreen mode And in this same class, in the Configure method, within UseEndpoints, we must indicate to look for these endpoints in the controllers with the condition endpoints.MapControllers(). app.UseEndpoints(endpoints => { endpoints.MapGet("https://dev.to/", async context => { await context.Response.WriteAsync("Hello World!"); }); endpoints.MapControllers(); }); Enter fullscreen mode Exit
Altre persone che si chiamano Giulia Serra in Italia
-
Giulia Serra
-
Giulia Serra
-
Giulia Serra
Specialista legale societario @ ALLIANZ
-
Giulia Serra
Banker Consultant Banca Mediolanum
Su LinkedIn ci sono altre 91 persone che si chiamano Giulia Serra in Italia
Vedi altre persone che si chiamano Giulia Serra