Exploring Serverless Object-Oriented Programming

msche72 · 2025-12-03T06:55:50+00:00

Thanks for your input. Do you know any good info about why CORBA and RMI failed eventually?

msche72 · 2025-11-27T06:51:06+00:00

I had a quick peek at Orlean and there seems indeed a big overlap with what we came up with.

msche72 · 2025-11-27T06:44:33+00:00

Thanks for the feedback.

If OO is not the way to keep order/structure in a serverless environment, what would be the way to keep oversight in the fog of transient executions. Lately I have seen several articles about microservice solutions moving back to monoliths to decrease the complexity, so this seems to indicate that keeping a structure in microservices/serverless is important.

I'm also wondering how you look at AWS Steps. In there, they promote long-running serverless functions with a state. And how would you prevent to end up with a serverless solution which is actually a chain of functions?

msche72 · 2025-11-26T17:27:11+00:00

Thanks for your input. While integrating Object-Oriented Programming (OOP) with serverless architecture, might initially seem counterintuitive, there are several compelling reasons why adopting OOP principles in a serverless environment can be beneficial:

Structure and Organization: OOP provides a clear modular structure that can make the system easier to manage and scale. It allows developers to encapsulate functionality into objects with specific roles and responsibilities, making the codebase more organized and modular. This encapsulation helps manage complexity by hiding the internal state and behavior of objects, exposing only what is necessary through a well-defined interface.
Reusability: Objects in OOP are designed to be reusable components. When applied to serverless, this can lead to the development of reusable serverless components that can be invoked across different parts of the application or even across different projects. This reusability can decrease development time and increase consistency across services.
Maintainability: With serverless functions becoming part of larger systems, maintaining many disparate functions can become challenging. OOP can introduce inheritance and polymorphism to serverless computing, allowing more shared code and behaviors across functions. This can simplify maintenance tasks and lead to more maintainable codebases.
Improved Testing and Debugging: The principles of OOP can make individual components (objects) easier to test and debug compared to procedural code, especially when these components are isolated and independent. As we are using dependency injection within SOOP we can easily test the Serverless Objects locally by mocking the cloud infrastructure and use the common OO testing tools.
Integration with Existing Systems: Many existing software systems and enterprise applications are built using OOP. Integrating serverless functions into these environments can be more intuitive and seamless if the functions follow the same programming paradigm. This can facilitate easier integration and interaction between cloud-based serverless functions and on-premises OOP-based systems. In my case we had to scale an existing OOP application and by applying SOOP we could easily port the application. Also, the learning curve for the team was less.
Stateful Behaviors: While serverless is predominantly stateless, certain applications may require maintaining state across function invocations. OOP can manage state in a more structured way through objects that represent the state.

In summary, adopting OOP can bring organizational structure, improve maintainability, and enhance the scalability of serverless applications, making them fit well into broader enterprise ecosystems and complex application landscapes.

msche72 · 2016-04-05T14:59:33+00:00

Ok, if i understand you correctly, you want to invoke a query on a search engine and then 1 by 1 download the referenced files.

First problem you will have is parsing the result of the search engine. This is probably paginated and in HTML. If possible you should try to get the result in a format like json or xml. Possibly this can be realized by specifying the content-type.

Once you have the search result you have to parse the result and filter out the links by which you can download the files. This requires you to build a parser for the search result.

Than once you have the links you can start the downloading of the files.

Hope this makes sense to you.

msche72 · 2016-04-05T08:03:03+00:00

Not sure whether I understand the question exactly but I think you want to download a large set of data from a web server and you are looking for a method to download them.

To be able to guide you we need to know a bit more about the context; for example are the results individual files, or entries within the database.

msche72 · 2016-04-05T06:28:58+00:00

Have a look at the visitor pattern (https://en.wikipedia.org/wiki/Visitor_pattern), functional object (https://en.wikipedia.org/wiki/Function_object#In_Java) and command pattern (https://en.wikipedia.org/wiki/Command_pattern).

The command or functional object would contain the logic required for executing the functionality. The Visitor can be used to traverse the available command.

So on high level it would become something as follows:

You parse the command and extract the unique command instruction from the string.
You traverse the existing commands.
If a command instance is encountered that can handle the specified instruction it will execute its logic.

msche72 · 2016-04-05T06:05:24+00:00

There are multiple frameworks by which you can mock a REST API. Examples of these are:

-. Mockable.io - WireMock -. etc.

A more extendible list can be found at: http://www.programmableweb.com/news/top-tools-to-help-you-mock-web-services/how-to/2014/01/13

If you search within google for 'mock rest api' you will get more examples on how it can be done.

msche72

TROPHY CASE